A method, device and authentication server for access control of multi-cloud system

By receiving object access requests from clients in the authentication server and obtaining target permission policies, the problem of insufficient flexibility in permission management in multi-cloud systems is solved, and fine-grained control of user access rights is achieved, which improves the flexibility and accuracy of permission management. sex.

CN112580006BActive Publication Date: 2024-11-26CHINA CONSTRUCTION BANK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011554144.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-24
Publication Date
2024-11-26
Estimated Expiration
2040-12-24

AI Technical Summary

Technical Problem

In the prior art, the access permission management of multi-cloud systems lacks flexibility and cannot subdivide the permission granularity, resulting in the inflexible user access permission management.

Method used

Provides a multi-cloud system access control method, which receives object access requests from clients through authentication servers, obtains target permission policies that match the user ID and object ID, determines whether the user has permission to access target objects in the target cloud system, and then identifies the The authentication results are transmitted to the target cloud system.

Benefits of technology

It realizes fine-grained control of user access rights in multi-cloud systems, improves the flexibility of permission management, and ensures that users can accurately access accessed objects in the cloud system according to permission policies.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112580006B_ABST
    Figure CN112580006B_ABST
Patent Text Reader

Abstract

The present application discloses an access permission control method, device and authentication server for a multi-cloud system. The method is applied to an authentication server, and the authentication server corresponds to multiple cloud systems. The cloud systems include multiple accessed objects. The method comprises: receiving an object access request sent by a client, wherein the object access request at least includes a user identifier of a target user and an object identifier of a target object, and the target object is an accessed object in a target cloud system among the multiple cloud systems; obtaining a target permission policy that matches the user identifier and the object identifier in a permission policy set, wherein the permission policy set includes multiple permission policy information, and each permission policy information corresponds to a user and an accessed object; obtaining an authentication result according to the target permission policy, wherein the authentication result indicates whether the target user has permission to access the target object in the target cloud system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of permission management, and in particular to an access permission control method, device and authentication server for a multi-cloud system. Background Art

[0002] With the development of technology, more and more cloud service providers are providing users with cloud services with different functions. For different cloud service providers, the unified authentication center can manage the user's access to the resources or functions of each cloud system.

[0003] Currently, the management of access rights to multi-cloud systems is usually performed according to the cloud system. For example, a user has access rights to one or more cloud systems, while another user does not have access rights to a certain cloud system. Based on this, when authenticating the access request submitted by the user, it can only be determined whether the user has access rights to the resources or functions of a certain cloud system, but it cannot be determined whether the user has access rights to different resources or functions in the cloud system.

[0004] Therefore, when managing user access rights, it is impossible to subdivide the granularity of the rights, resulting in poor flexibility in managing user access rights. Summary of the invention

[0005] In view of this, the present application provides an access rights control method, device and authentication server for a multi-cloud system, which are used to solve the technical problem of poor flexibility in the management of user access rights in the prior art.

[0006] The present application provides an access rights control method for a multi-cloud system, which is applied to an authentication server, wherein the authentication server corresponds to multiple cloud systems, and the cloud systems include multiple access objects. The method includes:

[0007] receiving an object access request sent by a client, wherein the object access request includes at least a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems;

[0008] In the authority policy set, a target authority policy matching the user identifier and the object identifier is obtained, wherein the authority policy set includes a plurality of authority policy information, each of which corresponds to a user and an accessed object;

[0009] According to the target permission policy, an authentication result is obtained, where the authentication result indicates whether the target user has permission to access the target object in the target cloud system.

[0010] The above method preferably obtains a target permission policy that matches the user identifier and the object identifier in the permission policy set, including:

[0011] In the permission policy set, initial policy information matching the user identifier and / or the user group identifier corresponding to the user identifier is screened; the user group identifier is the identifier of the target user group to which the target user belongs; the target user group also includes one or more other users;

[0012] In the initial policy information, a target permission policy matching the object identifier is screened out.

[0013] The above method preferably includes screening, in the permission policy set, initial policy information that matches the user identifier and / or the user group identifier corresponding to the user identifier, including:

[0014] In the permission policy set, first policy information matching the user identifier is selected;

[0015] In the authority policy set, second policy information matching the user group identifier is screened, and the first policy information and / or the second policy information constitute initial policy information.

[0016] The above method preferably further comprises:

[0017] The authentication result is transmitted to the target cloud system.

[0018] In the above method, preferably, the object access request also includes the identity authentication identifier of the target user;

[0019] The identity verification mark is generated when the target user logs into the target cloud system, and the identity verification mark indicates that the target user has successfully logged into the target.

[0020] The above method, preferably, further comprises:

[0021] receiving a user login request sent by the client, wherein the user login request at least includes verification information of the target user and a system identifier of the target cloud system;

[0022] Verifying the verification information according to the system identifier to obtain a verification result, wherein the verification result indicates whether the target user has passed the identity authentication of the target cloud system;

[0023] In a case where the verification result indicates that the target user has passed the identity authentication of the target cloud system, an identity authentication identifier of the target user is obtained.

[0024] The above method preferably verifies the verification information according to the system identifier to obtain a verification result, including:

[0025] Obtaining verification signature information corresponding to the verification information;

[0026] The standard signature information corresponding to the system identifier is compared with the verification signature information to obtain a verification result.

[0027] In the above method, preferably, obtaining the verification signature information corresponding to the verification information includes:

[0028] Using a signature algorithm, the user name and password in the verification information are signed to obtain verification signature information;

[0029] or,

[0030] The access key in the verification information is signed using a signature algorithm to obtain verification signature information.

[0031] The present application also provides an access rights control device for a multi-cloud system, which is applied to an authentication server, wherein the authentication server corresponds to multiple cloud systems, and the cloud systems include multiple access objects, and the device includes:

[0032] a request receiving unit, configured to receive an object access request sent by a client, wherein the object access request at least includes a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems;

[0033] A policy obtaining unit, configured to obtain a target permission policy that matches the user identifier and the object identifier from a permission policy set, wherein the permission policy set includes a plurality of permission policy information, each of which corresponds to a user and an accessed object;

[0034] The result obtaining unit is used to obtain an authentication result according to the target permission policy, wherein the authentication result indicates whether the target user has the permission to access the target object in the target cloud system.

[0035] The present application also provides an authentication server, the authentication server corresponding to a plurality of cloud systems, the cloud systems including a plurality of accessed objects, the authentication server comprising:

[0036] A transmission module, configured to receive an object access request sent by a client, wherein the object access request at least includes a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems;

[0037] The processor is used to obtain a target permission policy that matches the user identifier and the object identifier in a permission policy set, wherein the permission policy set includes multiple permission policy information, each of which corresponds to a user and an accessed object; and obtain an authentication result according to the target permission policy, wherein the authentication result indicates whether the target user has the permission to access the target object in the target cloud system.

[0038] The present application also provides a storage medium on which a program is stored. When the program is executed by a processor, the access permission control method for a multi-cloud system described in any one of the above items is implemented.

[0039] The present application also provides a processor, which is used to run a program, wherein the program executes any of the above-mentioned access permission control methods for a multi-cloud system when running.

[0040] It can be seen from the above technical solutions that in the access rights control method, device and authentication server of a multi-cloud system disclosed in the present application, after receiving the object access request sent by the client, the target permission policy that matches the object access request can be obtained in the permission policy set, and then the authentication result that characterizes whether the target user in the object access request can access the target object in the target cloud system can be obtained. It can be seen that in the present application, by subdividing the access rights granularity of multiple cloud systems into the accessed objects in each cloud system, the permission control of the user's access to the accessed objects in the cloud system can be realized when the user accesses the cloud system through the client, thereby improving the flexibility of permission management. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0042] Figure 1 A flowchart of a method for managing access rights of a multi-cloud system provided in Embodiment 1 of the present application;

[0043] Figure 2-Figure 5 They are respectively application example diagrams of the embodiments of the present application;

[0044] Figure 6 A partial flow chart of a method for managing access rights of a multi-cloud system provided in Embodiment 1 of the present application;

[0045] Figure 7-Figure 8Another flowchart of a method for managing access rights of a multi-cloud system provided in Embodiment 1 of the present application;

[0046] Fig. 9 Another application example diagram of the embodiment of the present application;

[0047] Fig.10 Another partial flow chart of a method for managing access rights of a multi-cloud system provided in Embodiment 1 of the present application;

[0048] Fig.11 A schematic diagram of the structure of an access rights management device for a multi-cloud system provided in Embodiment 2 of the present application;

[0049] Fig.12 Another structural diagram of an access rights management device for a multi-cloud system provided in Embodiment 2 of the present application;

[0050] Fig.13 A schematic diagram of the structure of an authentication server provided in Example 3 of the present application;

[0051] Figure 14-16 They are respectively example diagrams of the embodiments of the present application being applicable to user identity authentication and authority management in the financial industry. DETAILED DESCRIPTION

[0052] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0053] refer to Figure 1 , is a flowchart of a method for managing access rights of a multi-cloud system provided in the first embodiment of the present application. The method is applicable to an authentication server capable of processing data, such as a computer or a server. It should be noted that the authentication server corresponds to multiple cloud systems, such as Figure 2 As shown in , each cloud system is implemented by an electronic device deployed in the cloud, and each cloud system includes multiple accessed objects, such as accessible data resources or functional components. The technical solution in this embodiment is mainly used to implement the permission control of users to access the accessed objects in the cloud system, thereby improving the flexibility of permission management.

[0054] Specifically, the method in this embodiment may include the following steps:

[0055] Step 101: Receive an object access request sent by a client.

[0056] Among them, the object access request at least includes the user identifier of the target user and the object identifier of the target object. The target user is the user who needs to access the target object, and the target object is the accessed object in one or more target cloud systems in multiple cloud systems, such as a picture resource or a computing function.

[0057] It should be noted that the object access request may be a request generated by clicking or selecting a control corresponding to a target object such as a resource or function on the target cloud system operation interface presented on the target user's client after the target user logs in to the target cloud system, so as to indicate that the target user needs to access the target object. At this time, the user identifier of the target user may be information such as a user name, code or number that can uniquely identify the target user, and the object identifier of the target object may be information such as an object name, code or storage path that can uniquely identify the target object.

[0058] In addition, it should be particularly noted that, in order to achieve unified management of access rights of multi-cloud systems in this embodiment, the management and control of access rights are centralized in the authentication server in this embodiment. Therefore, after the object access request is generated on the client and sent to the target cloud system, the client sends the object access request to the authentication server in this embodiment through redirection according to the reply information returned by the target cloud system that requires authentication of the object access request. As a result, the authentication server in this embodiment can receive the object access request sent by the client through the communication connection with the client, such as Figure 3 as shown in .

[0059] The client corresponding to the target user can be a terminal or device such as a mobile phone, pad or computer.

[0060] Step 102: Obtain a target permission policy that matches the user identifier and the object identifier in the permission policy set.

[0061] The permission policy set is a pre-configured set, which may contain multiple permission policy information, each permission policy information corresponds to a user and an accessed object, and each permission policy information contains information about whether the user has access rights to the accessed object. For example, the permission policy set is implemented as a table containing multiple fields, such as Figure 4As shown in , the table contains multiple rows of fields, each row of fields contains a user column, an object column and a permission column. The user column records the user's ID, the object column records the object's ID, and the permission column records the information on whether the user has access rights. Based on this, the information in the permission column in each row of fields represents whether the user in the user column has the permission to access the object in the object column. For example, allow indicates that user A has access rights to the accessed object B, and deny indicates that user A does not have access rights to the accessed object C. It should be noted that the table may contain multiple rows of fields corresponding to the same user, and the multiple rows of fields corresponding to the same user are used to record whether the user has access rights to different accessed objects. It should be noted that the table may contain multiple rows of fields corresponding to the same accessed object, and the multiple rows of fields corresponding to the same accessed object are used to record whether different users have access rights to the accessed object.

[0062] Furthermore, in a multi-cloud system, two or even more users can be bound to the same user group, e.g. Figure 5 As shown in , users in the same user group have the same access rights, such as the same access rights to the same or multiple accessed objects. In addition, a user can exist alone and not be bound to any user group, or can be bound to a user group, or can exist alone and be bound to one or multiple user groups at the same time.

[0063] Based on this, the permission policy information in the permission policy set may also be permission policy information corresponding to the user group and the accessed object, and the permission policy information corresponding to the user group includes information on whether the users in the user group have access rights to the accessed object. Figure 4 As shown in , the user column of the row field in the table can also correspond to the user group. In this case, the identifier of the user group is recorded in the user column, the identifier of the object is recorded in the object column, and the information on whether the user has access rights is recorded in the permission column. Based on this, the information in the permission column in each row field represents whether the user in the user group in the user column has the permission to access the object in the object column. For example, allow indicates that users A and D in user group X have access rights to the accessed object B, and deny indicates that users A and D in user group Y do not have access rights to the accessed object C. It should be noted that the table may contain multiple rows of fields corresponding to the same user group, and the multiple rows of fields corresponding to the same user group are respectively used to record whether the user group has access rights to different accessed objects. It should be noted that the table may contain multiple rows of fields corresponding to the same accessed object, and the multiple rows of fields corresponding to the same accessed object are respectively used to record whether different user groups have access rights to the accessed object.

[0064] It should be noted that, unlike the access permission management that one user can only correspond to one cloud system, in this embodiment, the access permission is subdivided into the granularity of the accessed object, so that each permission policy information can correspond to the accessed object rather than the cloud systems to which multiple accessed objects belong.

[0065] Based on this, in this embodiment, after obtaining the user identifier and object identifier, the permission policy information is screened in the permission policy set to obtain a target permission policy that matches both the user identifier and the object identifier in the object access request, and the target permission policy contains information on whether the target user has access rights to the target object.

[0066] Step 103: Obtain the authentication result according to the target authority policy.

[0067] The authentication result indicates whether the target user has the authority to access the target object in the target cloud system.

[0068] Specifically, in this embodiment, the information on whether the target user in the target permission policy has access rights to the target object can be analyzed and judged, thereby parsing out whether the target user has access rights to the target object in the target cloud system, thereby generating an authentication result.

[0069] Among them, the identification in the authentication result can be used to indicate whether the target user has the permission to access the target object in the target cloud system. For example, allow is used to indicate that the target user has the permission to access the target object in the target cloud system, and deny is used to indicate that the target user does not have the permission to access the target object in the target cloud system.

[0070] It can be seen from the above scheme that in a multi-cloud system access rights management method provided in the first embodiment of the present application, after receiving an object access request sent by a client, a target permission policy that matches the object access request can be obtained in the permission policy set, and then an authentication result that characterizes whether the target user in the object access request can access the target object in the target cloud system can be obtained. It can be seen that in this embodiment, by subdividing the access rights granularity of multiple cloud systems into the accessed objects in each cloud system, it is possible to implement permission control for users to access the accessed objects in the cloud system when the user accesses the cloud system through the client, thereby improving the flexibility of permission management.

[0071] In one implementation, in step 102, when obtaining the target permission policy that matches the user identifier and the object identifier in the permission policy set, it can be implemented by the following steps: Figure 6 As shown in:

[0072] Step 601: In the permission policy set, initial policy information matching the user identifier and / or the user group identifier corresponding to the user identifier is screened.

[0073] The user group identifier is an identifier of a target user group to which the target user belongs. In addition to the target user, the target user group may also include one or more other users. All users in the target user group have the same access rights to the accessed object.

[0074] Specifically, in this embodiment, only the initial policy information matching the user identifier may be screened in the authority policy set;

[0075] Alternatively, only the initial policy information matching the user group identifier corresponding to the user identifier is filtered in the permission policy set;

[0076] Alternatively, the first policy information matching the user identifier and the second policy information matching the user group identifier corresponding to the user identifier are simultaneously screened in the permission policy set, and the screened first policy information and / or second policy information constitute the initial policy information;

[0077] Alternatively, in this embodiment, first policy information matching the user identifier is first screened in the permission policy set. If the first policy information matching the user identifier is not screened out in the permission policy set, second policy information matching the user group identifier corresponding to the user identifier is then screened in the permission policy set as the initial policy information.

[0078] Specifically, taking the screening of permission policy information that matches the user identifier as an example, in this embodiment, the user identifier can be compared with the user in each permission policy information in the permission policy set, and then the initial policy information that matches the user identifier can be screened out. For example, in the table of the permission policy set in this embodiment, the user identifier is compared with the user in the user column in the table, and then one or more rows of fields that match the user identifier are screened out, and each row of fields screened out corresponds to a piece of permission policy information, that is, the initial policy information that matches the user identifier. The implementation method of screening the permission policy information that matches the user group identifier can refer to the above method, which will not be described in detail here.

[0079] It should be noted that there may be one or more pieces of initial policy information matching the user identifier.

[0080] Step 602: Filter out the target permission policy that matches the object identifier in the initial policy information.

[0081] Among them, in this embodiment, the object identifier can be compared with the initial policy information, and then the target permission policy that matches the object identifier can be screened out. For example, in this embodiment, in one or more rows of fields that match the user identifier, the object identifier is compared with the accessed object in the object column in these fields, and then one or more rows of fields that match both the user identifier and the object identifier are screened out, and each row of fields that are screened out is a permission policy information, that is, the target permission policy.

[0082] In one implementation, after step 103, the method in this embodiment may further include the following steps: Figure 7 As shown in:

[0083] Step 104: Transmit the authentication result to the target cloud system.

[0084] Among them, after the authentication server in this embodiment transmits the authentication result to the target cloud system, the target cloud system can allow or prohibit the target user from accessing the target object based on the information in the authentication result whether the target user has the access right to the accessed object. For example, if the authentication result indicates that the target user has the access right to the target object such as a picture, the target cloud system allows the target user to view the picture or allows the target user to download the picture; for another example, if the authentication result indicates that the target user does not have the access right to the picture, the target cloud system prohibits the target user from viewing the target object such as a picture.

[0085] Further, in this embodiment, after obtaining the authentication result, the authentication result can also be transmitted to the client to prompt the target user. In addition, when the target user does not have access rights to the target object, the target user can be further prompted to obtain access rights before accessing the object.

[0086] In one implementation, the object access request may also include an identity authentication identifier of the target user, which is generated when the target user logs in to the target cloud system, and is used to indicate that the target user has successfully logged in to the target cloud system, that is, the target user is authenticated and verified by the authentication server when logging in to the target cloud system.

[0087] The identity verification identifier may be represented by a string.

[0088] Specifically, when the target user needs to log in to the target cloud system, the target user's identity is authenticated on the authentication server. Based on this, before step 101, the method in this embodiment may also include the following steps of authenticating the target user, such as Figure 8 As shown in:

[0089] Step 105: Receive a user login request sent by the client.

[0090] The user login request at least includes the verification information of the target user and the system identifier of the target cloud system.

[0091] Specifically, the verification information of the target user can be implemented differently according to the way the target user logs in to the target cloud system: when the target user logs in to the target cloud system through a page, the verification information of the target user includes information such as the user name and password entered by the target user on the page; when the target user logs in to the target cloud system through an interface such as an execution program, the verification information of the target user includes information such as the access key of the target user contained in the execution program.

[0092] It should be noted that when the target user performs a login operation on the target cloud system on the client, such as entering a user name and password or triggering an execution program to start running, the client sends the initial user login request generated by the login operation to the target cloud system. At this time, the initial user login request may only include the verification information of the target user. In order to achieve unified management of access rights of multi-cloud systems in this embodiment, the management and control of access rights are centralized in the authentication server in this embodiment. Therefore, after the user login request is generated on the client and sent to the target cloud system, the client redirects the user login request to the authentication server in this embodiment based on the reply information returned by the target cloud system that requires identity authentication of the target user. At this time, the user login request received by the authentication server also includes the system identifier of the target cloud system to indicate that identity authentication is required for the target user to log in to the target cloud system. As a result, the authentication server in this embodiment can receive the user login request sent by the client through the communication connection with the client, such as Fig. 9 as shown in .

[0093] Step 106: Verify the verification information according to the system identifier to obtain a verification result.

[0094] The verification result indicates whether the target user has passed the identity authentication of the target cloud system.

[0095] Specifically, in this embodiment, when verifying the verification information, it can be implemented in the following ways: Fig.10 As shown in:

[0096] Step 1001: Obtain verification signature information corresponding to the verification information.

[0097] Specifically, in this embodiment, the verification information may be encrypted or encoded using a signature algorithm to obtain the verification signature information.

[0098] In one implementation, in this embodiment, a signature algorithm such as an encryption algorithm may be used to sign the user name and password in the verification information to obtain verification signature information;

[0099] In another implementation, in this embodiment, a signature algorithm may be used to sign the access key in the verification information to obtain verification signature information.

[0100] The above two implementation methods correspond to the two access methods here: one is that the target user logs in on the page with a user name and password. At this time, the user name and password are signed using a signature algorithm to obtain verification signature information to verify the user's identity; the other is that the product service is called using a program. At this time, the key pair such as AccessKeyID and AccessKeySecret is used as the input parameter of the program, and the key pair is signed using a signature algorithm to obtain verification signature information to verify the user's identity.

[0101] Step 1002: Compare the standard signature information corresponding to the system identifier with the verification signature information to obtain a verification result.

[0102] For example, in this embodiment, the standard signature information of the target cloud system can be obtained from a signature library in which the standard signature information of each cloud system is pre-stored in the authentication server, and then the standard signature information of the target cloud system can be compared with the verification signature information obtained by signing the verification information using the signature algorithm to obtain a verification result.

[0103] Among them, when the standard signature information corresponding to the system identifier is consistent with the verification signature information, the verification result indicates that the target user has passed the identity authentication of the target cloud system; when the standard signature information corresponding to the system identifier is inconsistent with the verification signature information, the verification result indicates that the target user has not passed the identity authentication of the target cloud system.

[0104] Step 107 : Determine whether the verification result indicates that the target user has passed the identity authentication of the target cloud system. If the verification result indicates that the target user has passed the identity authentication of the target cloud system, execute step 108 .

[0105] Specifically, in this embodiment, the content in the verification result can be judged. For example, when the verification result is 1, the verification result indicates that the target user has passed the identity authentication of the target cloud system. When the verification result is 0, the verification result indicates that the target user has not passed the identity authentication of the target cloud system.

[0106] Step 108: Obtain the identity authentication identifier of the target user.

[0107] In this embodiment, according to the generation rule of the verification mark, an identity verification mark, which may also be called an access ticket, may be generated for the target user to indicate that the target user has passed the identity verification of the target cloud system.

[0108] In addition, in this embodiment, when the authentication server authenticates the target user, it can provide identification information such as global tickets, service tickets, and global sessions for the target user to log in to the target cloud system, so as to represent the login status of the target user through the client to log in to the target cloud system, so as to control the target user to exit the login status of the target cloud system on the client when the target user logs in to the target cloud system again through other terminals such as mobile phones.

[0109] refer to Fig.11 , is a schematic diagram of the structure of a multi-cloud system access rights management device provided in the second embodiment of the present application. The device can be configured in an authentication server capable of data processing, such as a computer or server. It should be noted that the authentication server corresponds to multiple cloud systems, such as Figure 2 As shown in , each cloud system is implemented by an electronic device deployed in the cloud, and each cloud system includes multiple accessed objects, such as accessible data resources or functional components. The technical solution in this embodiment is mainly used to implement the permission control of users to access the accessed objects in the cloud system, thereby improving the flexibility of permission management.

[0110] Specifically, the device in this embodiment may include the following units:

[0111] The request receiving unit 1101 is used to receive an object access request sent by a client, wherein the object access request at least includes a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems;

[0112] The policy obtaining unit 1102 is used to obtain a target permission policy that matches the user identifier and the object identifier in a permission policy set, wherein the permission policy set includes a plurality of permission policy information, each of which corresponds to a user and an accessed object;

[0113] The result obtaining unit 1103 is used to obtain an authentication result according to the target permission policy, where the authentication result indicates whether the target user has the permission to access the target object in the target cloud system.

[0114] It can be seen from the above scheme that in the access permission control device for a multi-cloud system provided in the second embodiment of the present application, after receiving the object access request sent by the client, the target permission policy that matches the object access request can be obtained in the permission policy set, and then the authentication result that characterizes whether the target user in the object access request can access the target object in the target cloud system can be obtained. It can be seen that in this embodiment, by subdividing the access permission granularity of multiple cloud systems into the accessed objects in each cloud system, the permission control of the user's access to the accessed objects in the cloud system can be implemented when the user accesses the cloud system through the client, thereby improving the flexibility of permission management.

[0115] In one implementation, the policy acquisition unit 1102 is specifically used to: in the permission policy set, filter the initial policy information that matches the user identifier and / or the user group identifier corresponding to the user identifier; the user group identifier is the identifier of the target user group to which the target user belongs; the target user group also includes one or more other users; in the initial policy information, filter out the target permission policy that matches the object identifier.

[0116] Optionally, when the policy obtaining unit 1102 filters the initial policy information that matches the user identifier and / or the user group identifier corresponding to the user identifier in the permission policy set, it is specifically used to: filter the first policy information that matches the user identifier in the permission policy set; filter the second policy information that matches the user group identifier in the permission policy set, and the first policy information and / or the second policy information constitute the initial policy information.

[0117] In one implementation, the result obtaining unit 1103 is further used to: transmit the authentication result to the target cloud system.

[0118] In one implementation, the object access request also includes an identity verification identifier of the target user; wherein the identity verification identifier is generated when the target user logs into the target cloud system, and the identity verification identifier indicates that the target user has successfully logged into the target.

[0119] In one implementation, the device in this embodiment may further include the following units: Fig.12 As shown in:

[0120] The identity authentication unit 1104 is used to verify the verification information according to the system identifier to obtain a verification result after the request receiving unit 1101 receives the user login request sent by the client, and the user login request at least includes the verification information of the target user and the system identifier of the target cloud system; the verification result indicates whether the target user has passed the identity authentication of the target cloud system; when the verification result indicates that the target user has passed the identity authentication of the target cloud system, obtain the identity authentication identifier of the target user.

[0121] In one implementation, when the identity authentication unit 1104 verifies the verification information according to the system identifier to obtain a verification result, it is specifically used to: obtain the verification signature information corresponding to the verification information; for example, use a signature algorithm to sign the user name and password in the verification information to obtain the verification signature information; or, use a signature algorithm to sign the access key in the verification information to obtain the verification signature information; then, compare the standard signature information corresponding to the system identifier with the verification signature information to obtain the verification result.

[0122] It should be noted that the specific implementation of each unit in this embodiment can refer to the corresponding content in the previous text and will not be described in detail here.

[0123] refer to Fig.13 , is a schematic diagram of the structure of an authentication server provided in Embodiment 3 of the present application. The authentication server may correspond to multiple cloud systems, such as Figure 2 As shown in , each cloud system is implemented by an electronic device deployed in the cloud, and each cloud system includes multiple accessed objects, such as accessible data resources or functional components. The technical solution in this embodiment is mainly used to implement the permission control of users to access the accessed objects in the cloud system, thereby improving the flexibility of permission management.

[0124] Specifically, the authentication server in this embodiment may include the following structure:

[0125] The transmission module 1301 is used to receive an object access request sent by a client, wherein the object access request at least includes a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems;

[0126] Processor 1302 is used to obtain a target permission policy that matches the user identifier and the object identifier in a permission policy set, where the permission policy set includes multiple permission policy information, each of which corresponds to a user and an accessed object; and obtain an authentication result based on the target permission policy, where the authentication result indicates whether the target user has the permission to access the target object in the target cloud system.

[0127] Of course, the authentication server in this embodiment may also include a memory for storing applications and data generated by the operation of the applications. When the processor 1302 executes the applications stored in the memory, the above functions of the processor 1302 may be implemented.

[0128] It can be seen from the above scheme that in an authentication server provided in Example 3 of the present application, after receiving an object access request sent by a client, a target permission policy that matches the object access request can be obtained in the permission policy set, and then an authentication result that characterizes whether the target user in the object access request can access the target object in the target cloud system can be obtained. It can be seen that in this embodiment, by subdividing the access rights granularity of multiple cloud systems into the accessed objects in each cloud system, it is possible to implement permission control for users to access the accessed objects in the cloud system when the user accesses the cloud system through the client, thereby improving the flexibility of permission management.

[0129] An embodiment of the present application further provides a storage medium on which a program is stored. When the program is executed by a processor, the access permission control method for a multi-cloud system described in any of the above embodiments is implemented.

[0130] An embodiment of the present application further provides a processor, which is used to run a program, wherein the program executes the access permission control method for a multi-cloud system described in any of the above embodiments when running.

[0131] Taking the user and permission management of multiple cloud systems configured in the cloud by the financial industry as an example, the technical solution in this application is illustrated as follows:

[0132] The inventors of this application found that there are currently many different implementation solutions for user identity authentication and permission management in a multi-cloud ecosystem, but all of them have certain defects, as follows:

[0133] In one implementation, different application systems maintain a user identity authentication system. For administrators who manage different systems, they need to enter their own user names and passwords for login, authorization, operation, etc., which is inconvenient to use and manage. Later, a single sign-on solution was formed, and the authentication process was automatically completed by the system. Taking cookie-based single sign-on as an example, its main principle is to encrypt the user name and password and store them in the cookie. Later, when the user visits the website, the user's current login status is verified. If the verification fails, the user name and password are taken out from the cookie for login. From the user's perspective, it is believed that only one login operation of entering the user name and password has been performed, but in fact, the user name and password have been transmitted multiple times, increasing the risk of theft. In addition, this unified login solution cannot be accessed across domains. Each system has a login authentication system, which increases the complexity of the code and has great limitations.

[0134] For the unified authentication center login method based on CAS, an independent authentication center is deployed separately to provide authentication services. However, due to the complexity of its own authority control, CAS authentication alone cannot meet the subdivision of authority granularity.

[0135] Based on the above defects, the inventor of this application provides an identity access and control system for unified user life cycle management in a multi-cloud ecosystem (multi-cloud system scenario) in order to solve the problem of unified management of user identity authentication and authority management in a multi-cloud ecosystem, effectively reducing the cost of authority management and providing a more flexible and convenient console access method for the multi-cloud ecosystem. For example, based on the unified authentication system of the unified authentication center CAS (Central Authentication Server), the management of the user's full life cycle and user authority management can be used as a separate authentication system to achieve the use of the same user and the same authority to log in to the operating cloud platform in a multi-cloud ecosystem.

[0136] The specific design plan is as follows:

[0137] In this application, a separate unified authentication center is built, which is the authentication server mentioned above. In a multi-cloud ecosystem, each cloud management system no longer manages separate user identity access and permission control modules. Through a separate unified authentication center, the account management of the entire life cycle, such as user creation, authorization, login, authentication, and deletion, is managed separately, and a secure access method can be provided for resources and operations. Access management is mainly implemented by binding authorization policies to users and user groups. The access key consists of a user name and password, or AccessKeyID and AccessKeySecret, and is used for identity authentication of cloud service API requests. When a user accesses a function or resource, the user first authenticates the identity, and then the access permission is verified. Only after the above two steps are passed can the resource be accessed, otherwise the access will be denied.

[0138] First, the single sign-on design for unified user lifecycle management in a multi-cloud form:

[0139] 1. Database design of unified identity access and authority control system:

[0140] like Fig.14 As shown in , in the unified identity authentication scheme proposed in this application, a dedicated user information database is used to store user information, including user name, password, mobile phone number, email address, user group, user corresponding access key and other information. Based on the principle of CAS, CAS Server is a unified identity authentication center (i.e., authentication server), and user information is stored in a database DB (database), which is authenticated by querying the DB during user authentication. CAS Client is deployed in the client's application system (i.e., client), and a URL is set to redirect the user authentication request to CAS Server, thereby realizing login, verification and logout operations.

[0141] 2. Design of unified identity access and authority control system:

[0142] When a user logs in to the system for the first time through a domain name, the web page is redirected to the unified identity authentication server for the first login. Identity authentication is performed based on the user information credentials such as the user name and password entered by the user. If the verification is successful, an access authentication evidence is generated, that is, the identity authentication identifier mentioned above. When the user accesses other resources or functions under the cloud system, the access ticket will be submitted to the CAS unified identity authentication server for verification. At this time, the administrator no longer needs to submit the login information again when opening the system.

[0143] In order to implement the single sign-on function, CAS provides global tickets TGT (ticket granting ticket), service tickets ST (service ticket) and global sessions (ticket granting cookies). The workflow of the unified identity authentication solution based on CAS single sign-on is as follows Fig.14 As shown in:

[0144] Specific description:

[0145] 1. The user accesses the cloud system 001 via the Web;

[0146] 2. System 001 finds that the user has not yet been authenticated and redirects the page request to the CAS Server;

[0147] 3. The user enters relevant authentication information and passes the verification;

[0148] 4. After the authentication is passed, the authentication center will jump to the corresponding cloud system 001 for the user to log in with the relevant authentication;

[0149] 5. After the authentication is passed, the authentication center will jump to the corresponding cloud system 002 for the user to log in (or);

[0150] 6. After the authentication is passed, the authentication center jumps to the corresponding cloud system 004 for the user to log in (or); to a different cloud system, such as cloud system 001;

[0151] 7. The cloud system returns the client user's login information to the cloud system.

[0152] Secondly, unified user lifecycle management and permission management control in multi-cloud form:

[0153] After the user performs unified single sign-on, the functions and resources that can be operated after logging into the platform need further authentication because the permission control granularity is not detailed enough. Fig.15 As shown in, when a user clicks on a resource or an interface-level function on the cloud platform through a browser, the browser will verify the user information with the permission control module of the unified authentication center. If the identity verification passes, the user can operate the corresponding functions and resources of the platform. If the authentication fails, a prompt message is returned indicating that the operation is not authorized and the administrator should be contacted for authorization.

[0154] 1. Database design of unified identity access and authority control system:

[0155] As mentioned above, in the unified identity authentication scheme proposed in this application, a dedicated user information database is used to store user information. In addition, in order to further manage user permissions, a separate database is designed to store platform policy data. The permission control scheme is implemented based on IAM, and the strategy is the key element of the scheme: based on the user and user group binding strategy, authentication is implemented to confirm whether the user has the permission to operate a certain function or resource of the platform. The authentication process is as follows Fig.15 shown.

[0156] 2. Design of unified identity access and authority control system

[0157] The IAM permission management system is a more sophisticated access control system that enables multiple users with different roles to manage the entire cloud platform. When a user has logged into the system and operates a resource on the platform, the browser will authenticate the operation to the unified authentication center. When a user initiates an access request, the system performs authentication based on the action in the user's authorized access policy, checking the rules such as Fig.15 As shown:

[0158] 1. The user initiates an access request;

[0159] 2. The system redirects the request to the CAS Server;

[0160] 3. The system will first search for permissions based on IAM project authorization among the granted access permissions, that is, it will filter the matching permission policy information actions in the permission policy set, and then search for the action corresponding to the request in the permissions;

[0161] 4. If a matching Allow or Deny action is found, cloud system 001 performs access control and returns the requested authentication decision, Allow or Deny, and the authentication ends;

[0162] 5. If a matching Allow or Deny action is found, the cloud system 002 performs access control and returns the requested authentication decision, Allow or Deny, and the authentication ends;

[0163] 6. If a matching Allow or Deny action is found, the cloud system 004 performs access control and returns the requested authentication decision, Allow or Deny, and the authentication ends;

[0164] 7. The cloud system returns the content corresponding to the request to the user, such as resources or functions.

[0165] The following references Fig.16 , the process of obtaining the authentication result is explained:

[0166] First, after receiving the access request, check whether there is IAM permission policy information corresponding to the access request. If there is, the authentication result can be directly obtained, Allow or Deny, and the authentication is completed;

[0167] If there is no IAM permission policy information corresponding to the access request, then determine whether the user is added to the user group. If so, check whether there is IAM permission policy information corresponding to the user group. If so, you can directly get the authentication result, Allow or Deny, and the authentication ends;

[0168] If the user is not added to the user group or there is no IAM permission policy information corresponding to the user group to which the user has joined, the authentication result is also obtained, that is, Deny, and the authentication ends.

[0169] In summary, under the multi-cloud model, enterprises often use a set of user and permission control systems in different clouds, which has great defects. In view of this, this application solves the current situation of multiple identity authentications and separate permission controls in the multi-cloud ecosystem by setting up a separate identity access and permission control system for user full life cycle management, thereby reducing the management costs of user registration, login, and permission control. Moreover, the unified identity access and permission control system can also reduce system redundancy and facilitate system administrators to manage their own products. For example, CVM administrators have the same management permissions in different clouds. Compared with the traditional user model, this model is more suitable for the actual pain points faced by current enterprises and can improve management efficiency for enterprises.

[0170] It can be seen that the technical solution in this application can effectively solve the management of platform users under multi-cloud deployment. From the user's perspective, the same user (product administrator role on the cloud platform) only needs to use a set of authentication systems to conveniently manage the products he operates and maintains; for the platform management side, the independent user authentication system gets rid of the complex architecture and redundancy of platform management, and each platform no longer needs to maintain a set of modules for managing users separately, and can focus more on the development of its own products; in addition, it can have better operability in maintaining user information data fields, user life cycle management, user unified authorization, and authority control, and will not cause the difficulty of managing multiple user management modules on multiple platforms, or the lack of a certain platform user, resulting in the lack of product administrator roles, affecting product management and operation and maintenance.

[0171] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0172] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0173] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0174] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for controlling access rights of a multi-cloud system. It is characterized in that Applied to an authentication server, the authentication server corresponds to a plurality of cloud systems, the cloud systems contain a plurality of accessed objects, the method comprising: Receive an object access request sent by a client, the object access request at least including a user identifier of a target user and an object identifier of a target object, the target object being an accessed object in a target cloud system among the multiple cloud systems; the object access request is redirected by the client to an authentication server corresponding to the target cloud system based on reply information returned by the target cloud system for authenticating the object access request; In the permission policy set, a target permission policy matching the user identifier and the object identifier is obtained, wherein the permission policy set includes a plurality of permission policy information, each of which corresponds to a user or a user group and an accessed object, and the permission policy information corresponding to the user group includes information on whether the users in the user group have access rights to the accessed object, the user group includes at least two or more bound users, and the user exists alone and is not bound to any user group, or is only bound to a user group, or exists alone and is bound to one or more user groups at the same time; Obtaining an authentication result according to the target permission policy, wherein the authentication result indicates whether the target user has permission to access the target object in the target cloud system; Wherein, obtaining a target permission policy that matches the user identifier and the object identifier in the permission policy set includes: In the authority policy set, initial policy information matching the user ID and the user group ID corresponding to the user ID is screened; the user group ID is the ID of the target user group to which the target user belongs; the target user group also includes one or more other users; Filtering out a target permission policy that matches the object identifier from the initial policy information; In the authority policy set, initial policy information matching the user identifier and the user group identifier corresponding to the user identifier is screened, including: In the permission policy set, first policy information matching the user identifier is selected; In the authority policy set, second policy information matching the user group identifier is screened, and the first policy information and the second policy information constitute initial policy information.

2. The method according to claim 1, It is characterized in that Also includes: The authentication result is transmitted to the target cloud system.

3. The method according to claim 1, It is characterized in that The object access request also includes the identity authentication identifier of the target user; The identity verification mark is generated when the target user logs into the target cloud system, and the identity verification mark indicates that the target user has successfully logged into the target.

4. The method according to claim 3, It is characterized in that The method further comprises: receiving a user login request sent by the client, wherein the user login request at least includes verification information of the target user and a system identifier of the target cloud system; Verifying the verification information according to the system identifier to obtain a verification result, wherein the verification result indicates whether the target user has passed the identity authentication of the target cloud system; In a case where the verification result indicates that the target user has passed the identity authentication of the target cloud system, an identity authentication identifier of the target user is obtained.

5. The method according to claim 4, It is characterized in that According to the system identifier, the verification information is verified to obtain a verification result, including: Obtaining verification signature information corresponding to the verification information; The standard signature information corresponding to the system identifier is compared with the verification signature information to obtain a verification result.

6. The method according to claim 5, It is characterized in that Obtaining verification signature information corresponding to the verification information, including: Using a signature algorithm, the user name and password in the verification information are signed to obtain verification signature information; or, The access key in the verification information is signed using a signature algorithm to obtain verification signature information.

7. An access rights control device for a multi-cloud system, It is characterized in that Applied to an authentication server, the authentication server corresponds to a plurality of cloud systems, the cloud systems contain a plurality of accessed objects, the device comprises: A request receiving unit, configured to receive an object access request sent by a client, wherein the object access request includes at least a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems; the object access request is redirected by the client to an authentication server corresponding to the target cloud system based on reply information returned by the target cloud system for authenticating the object access request; a policy obtaining unit, configured to obtain a target permission policy that matches the user identifier and the object identifier in a permission policy set, wherein the permission policy set includes a plurality of permission policy information, each of which corresponds to a user or a user group and an accessed object, and the permission policy information corresponding to the user group includes information on whether the users in the user group have access rights to the accessed object, and the user group includes at least two or more bound users, and the user exists independently and is not bound to any user group, or is only bound to a user group, or exists independently and is bound to one or more user groups at the same time; A result obtaining unit, configured to obtain an authentication result according to the target permission policy, wherein the authentication result indicates whether the target user has permission to access the target object in the target cloud system; Wherein, obtaining a target permission policy that matches the user identifier and the object identifier in the permission policy set includes: In the permission policy set, initial policy information matching the user ID and the user group ID corresponding to the user ID is screened; the user group ID is the ID of the target user group to which the target user belongs; the target user group also includes one or more other users; users in the same user group have the same access rights; Filtering out a target permission policy that matches the object identifier from the initial policy information; In the authority policy set, initial policy information matching the user identifier and the user group identifier corresponding to the user identifier is screened, including: In the permission policy set, first policy information matching the user identifier is selected; In the authority policy set, second policy information matching the user group identifier is screened, and the first policy information and the second policy information constitute initial policy information.

8. An authentication server, It is characterized in that The authentication server corresponds to a plurality of cloud systems, wherein the cloud systems include a plurality of accessed objects, and the authentication server includes: The transmission module is used to receive an object access request sent by a client, wherein the object access request at least includes a user identifier of a target user and an object identifier of a target object, wherein the target object is an object to be accessed in a target cloud system among the multiple cloud systems; the object access request is redirected by the client to an authentication server corresponding to the target cloud system according to reply information returned by the target cloud system for authenticating the object access request; A processor, configured to obtain a target permission policy that matches the user identifier and the object identifier in a permission policy set, wherein the permission policy set includes a plurality of permission policy information, each of which corresponds to a user or a user group, and an accessed object; obtain an authentication result according to the target permission policy, wherein the authentication result indicates whether the target user has permission to access the target object in the target cloud system; the permission policy information corresponding to the user group includes information on whether users in the user group have access rights to the accessed object, wherein the user group includes at least two or more bound users, wherein the user exists alone and is not bound to any user group, or is only bound to a user group, or exists alone and is bound to one or more user groups at the same time; Wherein, obtaining a target permission policy that matches the user identifier and the object identifier in the permission policy set includes: In the permission policy set, initial policy information matching the user ID and the user group ID corresponding to the user ID is screened; the user group ID is the ID of the target user group to which the target user belongs; the target user group also includes one or more other users; users in the same user group have the same access rights; Filtering out a target permission policy that matches the object identifier from the initial policy information; In the authority policy set, initial policy information matching the user identifier and the user group identifier corresponding to the user identifier is screened, including: In the permission policy set, first policy information matching the user identifier is selected; In the authority policy set, second policy information matching the user group identifier is screened, and the first policy information and the second policy information constitute initial policy information.