Authority management method and device, electronic equipment and medium

Abstract

The invention provides an authority management method and device, electronic equipment and a medium. The authority management method comprises the following steps: creating at least one resource group; for each resource group, determining at least one target user under the resource from users of the cloud management platform; associating the resource group with at least one user account of each target user; user permissions of target users in the resource group are configured; allocating resources created by the user based on the user account to a resource group associated with the user account; and for each user, if the user has at least one user account associated with the resource group, accessing resources under the resource group based on the user permission of the resource group. According to the scheme, the flexibility of resource authority management can be improved.

Description

Technical Field

[0001] The present application relates to the field of cloud platform management technology, and in particular to a permission management method, device, electronic device and medium. Background Art

[0002] With the trend of digital transformation, cloud computing technology has been widely used and popularized. Cloud management platform is a product that provides management of private cloud, public cloud and hybrid cloud, mainly managing the resources in the cloud platform, including hosts, hard disks, network resources, etc.

[0003] In related technologies, resources are usually divided according to their regions, such as resources in region A and region B. Resources under each region are isolated on a region-by-region basis, and corresponding permissions are set for resources in the same region. Users in each region can access the resources in that region based on the set permissions.

[0004] However, with the development of cloud technology, the resources under the cloud platform have gradually become more complex and diverse. The flexibility of resource permission management methods in related technologies is poor and cannot adapt to complex and diverse resource management needs. Therefore, it is important to improve the flexibility of resource permission management. Summary of the invention

[0005] The embodiments of the present application provide a permission management method, device, electronic device and medium, aiming to improve the flexibility of resource permission management.

[0006] In a first aspect, the present application provides a permission management method, the method comprising: creating at least one resource group; for each resource group, determining at least one target user under the resource from the users of the cloud management platform; associating the resource group with at least one user account of each target user; and configuring user permissions of the target users under the resource group; allocating the resources created by the user based on the user account to the resource group associated with the user account; for each user, if the user has at least one user account associated with the resource group, accessing the resources under the resource group based on the user permissions of the resource group.

[0007] In some embodiments, each resource group has a unique first identifier; associating the resource group with at least one user account of each target user includes: for each target user, determining the first user account to be associated in the user account of the target user; establishing a corresponding relationship between the first identifier and the first user account of each target account, and using the user account having a corresponding relationship with the first identifier of the resource group as the user account associated with the resource group.

[0008] In some embodiments, after allocating the resources created by the user based on the user account to the resource group associated with the user account, the method further includes: disassociating the first resource group from the first user account of the first user;

[0009] The resources created by the first user based on the first user account are removed from the first resource group.

[0010] In some embodiments, after disassociating the first resource group from the first user account of the first user, the process further includes associating the second resource group with the first user account of the first user, and allocating resources created by the first user based on the first user account to the second resource group.

[0011] In some embodiments, allocating the resources created by the user based on the user account to the resource group associated with the user account includes: detecting whether the user account used by the user to create resources has an associated resource group; if so, allocating the resources created by the user based on the user account to the resource group associated with the user account; if not, allocating the resources created by the user based on the user account to the default resource group.

[0012] In some embodiments, configuring the user rights of the target users under the resource group includes: for each resource group, setting the same user rights for the target users under the resource group.

[0013] In some embodiments, configuring the user rights of the target users under the resource group includes: for each target user under each resource group, setting the user rights corresponding to the target user.

[0014] In a second aspect, the present application provides a permission management device, comprising: a resource group management module, used to create at least one resource group; a user management module, used to determine, for each resource group, at least one target user under the resource from the users of the cloud management platform; to associate the resource group with at least one user account of each target user; and to configure user permissions of the target users under the resource group; the resource group management module, also used to allocate the resources created by the user based on the user account to the resource group associated with the user account; the user management module, also used to, for each user, access the resources under the resource group based on the user permissions of the resource group if the user has at least one user account associated with the resource group.

[0015] In some embodiments, each resource group has a unique first identifier; the user management module is specifically used to determine, for each target user, the first user account to be associated in the user account of the target user; the user management module is also specifically used to establish a correspondence between the first identifier and the first user account of each target account, and use the user account that has a corresponding relationship with the first identifier of the resource group as the user account associated with the resource group.

[0016] In some embodiments, the resource group management module is also used to disassociate the first resource group from the first user account of the first user after allocating the resources created by the user based on the user account to the resource group associated with the user account; and remove the resources created by the first user based on the first user account from the first resource group.

[0017] In some embodiments, the resource group management module is also used to, after disassociating the first resource group from the first user account of the first user, also include: associating the second resource group with the first user account of the first user, and allocating the resources created by the first user based on the first user account to the second resource group.

[0018] In some embodiments, the resource group management module is specifically used to detect whether the user account used by the user to create resources has an associated resource group; if so, the resources created by the user based on the user account are allocated to the resource group associated with the user account; if not, the resources created by the user based on the user account are allocated to the default resource group.

[0019] In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the method described above.

[0020] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to implement the method as described above when executed by a processor.

[0021] In the permission management method, device, electronic device and medium provided in the embodiments of the present application, at least one resource group is created; for each resource group, at least one target user under the resource group is determined, and at least one user account of the target user is associated with the resource group, and the user permissions of the target user under the resource group are configured, and the resources created by the target user based on the user account are allocated to the resource group associated with the user account. For each user, if the user has at least one user account associated with the resource group, the resources under the resource group are accessed based on the user permissions of the resource group. In this solution, the user account that creates the resources is associated with the resource group. Based on the association relationship, the resources created by the user account can be allocated to the associated resource group, and the resources under the resource group are isolated in units of resource groups. The isolation granularity is smaller, and the division of resources in each resource group can be customized, so this solution can improve the flexibility of resource permission management. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the embodiments of the present application, and together with the description are used to explain the principles of the embodiments of the present application.

[0023] The above drawings show the embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the embodiments of the present application in any way, but to illustrate the concepts of the embodiments of the present application to those skilled in the art by referring to specific embodiments.

[0024] Figure 1 A flowchart of a permission management method provided in Example 1 of the present application;

[0025] Figure 2 A flowchart of another permission management method provided in Example 1 of the present application;

[0026] Figure 3 A schematic diagram of the structure of another permission management method provided in an embodiment of the present application;

[0027] Figure 4 A schematic diagram of the structure of the rights management device provided in Example 1 of the present application;

[0028] Figure 5 This is a schematic diagram of the structure of an electronic device provided in Example 3 of the present application.

[0029] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0030] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0031] It should be noted that the brief description of terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their common and usual meanings.

[0032] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0033] The terms "first", "second", etc. in the specification and claims of this application and the above drawings are used to distinguish similar or similar objects or entities, and do not necessarily mean to limit a specific order or sequence, unless otherwise indicated. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, for example, they can be implemented in an order other than those given in the diagrams or descriptions of the embodiments of this application.

[0034] In addition, the terms "including" and "having" and any variations thereof are intended to cover but not exclude inclusion, for example, a product or device comprising a list of components is not necessarily limited to those components explicitly listed, but may include other components not explicitly listed or inherent to such products or devices. The term "circuitry" as used in this application refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with the element.

[0035] With the trend of digital transformation, cloud computing technology has been widely used and popularized. Cloud management platform is a product that provides management of private cloud, public cloud and hybrid cloud, mainly managing the resources in the cloud platform, including hosts, hard disks, network resources, etc.

[0036] In related technologies, resources are usually divided according to their regions, such as resources in region A and region B. Resources under each region are isolated on a region-by-region basis, and corresponding permissions are set for resources in the same region. Users in each region can access the resources in that region based on the set permissions.

[0037] However, with the development of cloud technology, the resources under the cloud platform have gradually become more complex and diverse. The flexibility of resource permission management methods in related technologies is poor and cannot adapt to complex and diverse resource management needs. Therefore, it is important to improve the flexibility of resource permission management.

[0038] In view of this, in the permission management method provided in the embodiment of the present application, a resource group is created, and the resource group can be associated with the user account of the target user. Based on the association relationship, the resources created by the user account can be allocated to the associated resource group, and the resources under the resource group can be isolated in units of resource groups. The isolation granularity is smaller, and the division of resources in each resource group can be customized. Therefore, this solution can improve the flexibility of resource permission management.

[0039] It should be noted that the permission management method, device, equipment and storage medium improved in this application can be used in the management field of the cloud platform, and can also be used in any field other than the management field of the cloud platform. This application does not limit the application field of the permission management method and device.

[0040] The technical solutions of the present application and the technical solutions of the present application are described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. In the description of the present application, unless otherwise clearly specified and limited, each term should be understood in a broad sense in the art. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0041] Embodiment 1

[0042] Figure 1 This is a flowchart of a rights management method provided in the first embodiment of the present application. The execution subject of the method may be a rights management system in a cloud management platform, which may be implemented in the form of hardware or hardware plus software. Figure 1 As shown, the method includes:

[0043] S101, creating at least one resource group;

[0044] S102: for each resource group, determine at least one target user under the resource from users of the cloud management platform; associate the resource group with at least one user account of each target user; and configure user permissions of the target user under the resource group;

[0045] S103, allocating the resources created by the user based on the user account to the resource group associated with the user account;

[0046] S104: For each user, if at least one user account of the user is associated with a resource group, the user accesses resources under the resource group based on the user authority of the resource group.

[0047] The resources in this embodiment may include but are not limited to: a host, a hard disk, a server, etc. At least one resource group is created in S101, that is, different resource groups can be established based on the attributes or categories of resources in the cloud management platform, and each resource group has its own category, name, etc. The number of resource groups can be set based on actual needs. As an example, the resource group may include: a hardware resource group, a computing resource group, etc.

[0048] In S102, in actual application, the cloud management platform includes multiple users, wherein the multiple users may include different companies, or different departments under different companies, etc. Each user may include one or more accounts, and the user may create different resources based on different accounts. For example, Company A may include a first account and a second account, wherein the first account is used to create hardware resources, and the second account is used to create computing resources. For each resource group, the target user under the resource group is determined from the users under the cloud management platform, wherein the number of target users may be one or more. The resource group is associated with an account of the target user, that is, all target users under the resource group can be obtained based on the association relationship. It should be noted that the same account of the target user can be associated with multiple accounts, such as the first account of user A can be associated with the first resource group, and can also be associated with the second resource group. This embodiment does not limit this.

[0049] There may be multiple methods for establishing association. As an implementation method, S102 includes:

[0050] For each target user, determining a first user account to be associated among the user accounts of the target user;

[0051] A correspondence between the first identifier and the first user account of each target account is established, and the user account having a correspondence with the first identifier of the resource group is used as the user account associated with the resource group.

[0052] For example, the target user includes 10 user accounts, and accounts 1 to 5 are used as the first user accounts to be associated. The first identifier can be a unique resource group ID of the resource group, and the resource group ID is set in the account information of accounts 1 to 5. For the target user, the resource group associated with the account can be determined based on the resource group ID in the account information.

[0053] Configure permissions for the target user. That is, only the target user under the resource group has access rights to the resources in the resource group. User permissions may include adding, deleting, modifying, and checking resources. It should be noted that when setting permissions for the target user, in some examples, the same user permissions are set for the target users under the resource group for each resource group. This example sets the same user permissions for all target users under the resource group, that is, the target users under the same resource group are treated the same, which facilitates the management of the target users. In other examples, for each target user under each resource group, the user permissions corresponding to the target user are set. In this example, different users under the same resource group can be set to the same permissions or different permissions. For example, the permissions set for target user A under resource group 1 are the access rights to the resources under resource group 1, and the permissions set for target user B under resource group 1 are the permissions to delete and modify the resources under resource group 1. This can further improve the flexibility of permission management.

[0054] After completing the permission configuration for the target user, S103 can be executed to assign the resources created by the user based on the user account to the resource group associated with the user account, wherein the resources created based on the user account can be created before the resource group is created, or can be created based on actual needs after the resource group is created. In the example where the resource is created before the resource group is created, the resource information of each resource includes the user account that creates the resource group. After the resource group is created, the resource will be based on the created user account and the resource group associated with the user account according to the association relationship. After the resource group is created, resources are established according to demand, and then the created resources are assigned to the corresponding resource group. It should be noted that a user can include multiple user accounts, each account can be associated with a resource group, and for each user, the resource groups associated with all the user accounts of the user can be displayed in the form of a list, and the user can select the corresponding resource group from the list to access the resources under the resource group.

[0055] It should also be noted that in actual applications, not all users are associated with resource groups. Figure 2 A flowchart of a permission management method provided in another embodiment of the present application is shown in FIG. Figure 2 As shown, S103 may include:

[0056] S1031, detecting whether the user account used by the user to create resources has an associated resource group;

[0057] S1032: If so, allocate the resources created by the user based on the user account to the resource group associated with the user account;

[0058] S1033: If not, assign the resources created by the user based on the user account to a default resource group.

[0059] In this example, for the scenario where the user account that creates the resource is associated with a resource group, the resource is directly allocated to the resource group associated with the user account. For the scenario where the user account that creates the resource is not associated with a resource group, the resource can be directly allocated to the default resource group. This makes it easier to maintain the resources under the cloud platform.

[0060] After the allocation of resources is completed, S104 is executed. For each user, if at least one user account of the user is associated with a resource group, the user can access the resources under the resource group based on the user permissions of the resource group. In other words, as long as a user has a user account associated with a resource group, the user can access all resources under the resource group according to the permissions set by the resource group.

[0061] For example, user A includes user account 1 and user account 2, where user account 1 is associated with the first resource group, and user account 2 is associated with the second resource group; user B includes user account 3, and user account 3 is associated with the first resource group and the third resource group. Then user A can access the resources under the first resource group and the second resource group, and user B can access the resources under the first resource group and the third resource group.

[0062] In this solution, the user account of the user who creates the resources is associated with the resource group. Based on the association relationship, the resources created by the user account can be assigned to the associated resource group, and the resources under the resource group can be isolated on a resource group basis. The isolation granularity is smaller, and the division of resources in each resource group can be customized. Therefore, this solution can improve the flexibility of resource permission management.

[0063] Based on the above embodiment, in some embodiments, after S103, the method of this embodiment may further include:

[0064] Disassociating the first resource group from the first user account of the first user;

[0065] The resources created by the first user based on the first user account are removed from the first resource group.

[0066] In this embodiment, by releasing the association between the first user account and the resource group, all resources established by the first user account are removed from the first resource group. It should be noted that for the first user, if there are other user accounts associated with the first resource group, the first user can still access the resources under the first resource group; if the first user does not have other user accounts associated with the first resource group, the first user cannot access the resources under the first resource group. Based on this solution, the flexibility of permission management can be further improved.

[0067] Based on the above embodiment, in some other embodiments, after the first resource group is disassociated from the first user account of the first user, the method further includes:

[0068] The second resource group is associated with the first user account of the first user, and the resources created by the first user based on the first user account are allocated to the second resource group.

[0069] In this embodiment, in combination with the above embodiments, it can be seen that this embodiment provides a method for implementing transfer between resource groups. In this solution, the transfer of resource groups is implemented by establishing or releasing the association between user accounts and resource groups, thereby further improving the flexibility of authority management.

[0070] The following is an exemplary introduction to this embodiment in combination with actual scenarios: Figure 3 A structural diagram of another permission management method provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, first create a resource group, including creating a name for the resource group, a resource group ID, etc. For each resource group, determine at least one target user under the resource from the users of the cloud management platform, associate the resource group with at least one user account of each target user, and configure the user permissions of the target user under the resource group. Then, detect whether the user account used by the user to create the resource has an associated resource group. If so, assign the resources created by the user based on the user account to the resource group associated with the user account. If not, assign the resources created by the user based on the user account to the default resource group. In later maintenance, the association between the first resource group and the first user account of the first user can also be disassociated, and the resources created by the first user based on the first user account can be removed from the first resource group to achieve resource removal. Associate the second resource group with the first user account of the first user, and assign the resources created by the first user based on the first user account to the second resource group to achieve resource transfer, thereby achieving maintenance of the resource group.

[0071] The permission management method provided in the embodiment of the present application creates at least one resource group; for each resource group, at least one target user under the resource group is determined, and at least one user account of the target user is associated with the resource group, and the user permissions of the target user under the resource group are configured, and the resources created by the target user based on the user account are allocated to the resource group associated with the user account. For each user, if the user has at least one user account associated with the resource group, the resources under the resource group are accessed based on the user permissions of the resource group. In this solution, the user account of the user who creates the resource is associated with the resource group. Based on the association relationship, the resources created by the user account can be allocated to the associated resource group, and the resources under the resource group are isolated in units of resource groups. The isolation granularity is smaller, and the division of resources in each resource group can be customized, so this solution can improve the flexibility of resource permission management.

[0072] Embodiment 2

[0073] Figure 4 This is a schematic diagram of the structure of the rights management device provided in Example 1 of the present application, such as Figure 4 As shown, the authority device includes:

[0074] The resource group management module 41 is used to create at least one resource group;

[0075] The user management module 42 is used to determine, for each resource group, at least one target user under the resource from the users of the cloud management platform; associate the resource group with at least one user account of each target user; and configure user permissions of the target user under the resource group;

[0076] The resource group management module 43 is further used to allocate the resources created by the user based on the user account to the resource group associated with the user account;

[0077] The user management module 42 is further configured to, for each user, access resources under the resource group based on the user rights of the resource group if at least one user account of the user is associated with the resource group.

[0078] As a way to achieve this,

[0079] The user management module 42 is specifically configured to determine, for each target user, a first user account to be associated among the user accounts of the target user;

[0080] The user management module 42 is further specifically configured to establish a correspondence between the first identifier and a first user account of each target account, and use a user account having a correspondence with the first identifier of the resource group as a user account associated with the resource group.

[0081] In some examples, the user management module 42 is specifically used to set the same user permissions for the target users under each resource group. In this example, all target users under the resource group are set with the same user permissions, that is, the target users under the same resource group are treated the same, which can facilitate the management of the target users.

[0082] In other examples, the user management module is specifically used to set the user rights corresponding to each target user under each resource group, so as to further improve the flexibility of rights management.

[0083] It should also be noted that in actual applications, not all users are associated with resource groups.

[0084] The resource group management module 43 is specifically used to detect whether the user account used by the user to create resources has an associated resource group;

[0085] The resource group management module 43 is specifically configured to allocate the resources created by the user based on the user account to the resource group associated with the user account, if any;

[0086] The resource group management module 43 is specifically configured to allocate the resources created by the user based on the user account to a default resource group if the default resource group does not exist.

[0087] In this example, for the scenario where the user account that creates the resource is associated with a resource group, the resource is directly allocated to the resource group associated with the user account. For the scenario where the user account that creates the resource is not associated with a resource group, the resource can be directly allocated to the default resource group. This makes it easier to maintain the resources under the cloud platform.

[0088] Based on the above embodiments, in some embodiments, the resource group management module 43 is further used to allocate the resources created by the user based on the user account to the resource group associated with the user account.

[0089] Disassociating the first resource group from the first user account of the first user;

[0090] The resources created by the first user based on the first user account are removed from the first resource group.

[0091] Based on the above embodiment, in some other embodiments, the resource group management module 43 is further used for, after the association between the first resource group and the first user account of the first user is released,

[0092] The second resource group is associated with the first user account of the first user, and the resources created by the first user based on the first user account are allocated to the second resource group.

[0093] In this embodiment, in combination with the above embodiments, it can be seen that this embodiment provides a method for implementing transfer between resource groups. In this solution, the transfer of resource groups is implemented by establishing or releasing the association between user accounts and resource groups, thereby further improving the flexibility of authority management.

[0094] The permission management device provided in the embodiment of the present application creates at least one resource group; for each resource group, at least one target user under the resource group is determined, and at least one user account of the target user is associated with the resource group, and the user permissions of the target user under the resource group are configured, and the resources created by the target user based on the user account are allocated to the resource group associated with the user account. For each user, if the user has at least one user account associated with the resource group, the resources under the resource group are accessed based on the user permissions of the resource group. In this solution, the user account of the user who creates the resource is associated with the resource group. Based on the association relationship, the resources created by the user account can be allocated to the associated resource group, and the resources under the resource group are isolated in units of resource groups. The isolation granularity is smaller, and the division of resources in each resource group can be customized, so this solution can improve the flexibility of resource permission management.

[0095] Embodiment 3

[0096] Figure 5 This is a schematic diagram of the structure of an electronic device provided in Example 3 of the present application, such as Figure 5 As shown, the electronic device includes:

[0097] The electronic device includes a processor 291 and a memory 292; it may also include a communication interface 293 and a bus 294. The processor 291, the memory 292, and the communication interface 293 may communicate with each other through the bus 294. The communication interface 293 may be used for information transmission. The processor 291 may call the logic instructions in the memory 292 to execute the method of the above embodiment.

[0098] In addition, the logic instructions in the above-mentioned memory 292 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

[0099] The memory 292 is a computer-readable storage medium that can be used to store software programs and computer executable programs, such as program instructions / modules corresponding to the methods in the embodiments of the present application. The processor 291 executes functional applications and data processing by running the software programs, instructions, and modules stored in the memory 292, that is, implementing the methods in the above method embodiments.

[0100] The memory 292 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory 292 may include a high-speed random access memory and may also include a non-volatile memory.

[0101] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in any one of the embodiments.

[0102] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims.

[0103] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A rights management method, characterized in that: The method comprises: Create at least one resource group; For each resource group, determine at least one target user under the resource from the users of the cloud management platform; associate the resource group with at least one user account of each target user; and configure user permissions of the target users under the resource group; Allocating resources created by the user based on the user account to a resource group associated with the user account; For each user, if at least one user account of the user is associated with a resource group, the user can access resources under the resource group based on the user permissions of the resource group.

2. The method according to claim 1, characterized in that Each resource group has a unique first identifier; The associating the resource group with at least one user account of each target user includes: For each target user, determining a first user account to be associated among the user accounts of the target user; A correspondence between the first identifier and the first user account of each target account is established, and the user account having a correspondence with the first identifier of the resource group is used as the user account associated with the resource group.

3. The method according to claim 1, characterized in that After allocating the resources created by the user based on the user account to the resource group associated with the user account, the method further comprises: Disassociating the first resource group from the first user account of the first user; The resources created by the first user based on the first user account are removed from the first resource group.

4. The method according to claim 3, characterized in that After the first resource group is disassociated from the first user account of the first user, the method further includes: The second resource group is associated with the first user account of the first user, and the resources created by the first user based on the first user account are allocated to the second resource group.

5. The method according to any one of claims 1 to 4, characterized in that: The allocating the resources created by the user based on the user account to the resource group associated with the user account includes: Detect whether the user account used by the user to create resources has an associated resource group; If so, allocating the resources created by the user based on the user account to the resource group associated with the user account; If not, the resources created by the user based on the user account are allocated to the default resource group.

6. The method according to any one of claims 1 to 4, characterized in that: The configuring the user rights of the target user under the resource group includes: For each resource group, the same user permissions are set for target users under the resource group.

7. The method according to any one of claims 1 to 4, characterized in that: The configuring the user rights of the target user under the resource group includes: For each target user under each resource group, set the user permissions corresponding to the target user.

8. A rights management device, characterized in that: include: A resource group management module, used to create at least one resource group; A user management module, configured to determine, for each resource group, at least one target user under the resource from users of the cloud management platform; Associating the resource group with at least one user account of each target user; And configure the user permissions of the target user under the resource group; The resource group management module is further used to allocate the resources created by the user based on the user account to the resource group associated with the user account; The user management module is further configured to, for each user, access resources under the resource group based on the user rights of the resource group if at least one user account of the user is associated with the resource group.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images