Cloud service authentication method and device, equipment and storage medium

By creating multiple authentication service instances in one authentication service and introducing user IDs, the problem of high resource occupancy and maintenance costs caused by the increase in the scale of tenants in the public cloud is solved, and multi-tenant isolation and resource utilization are improved .

CN119094179APending Publication Date: 2024-12-06BEIJING VOLCANO ENGINE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411155093.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-21
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

When existing public cloud providers adopt authentication services with a centralized security management framework, the resource occupancy rate and maintenance costs are high, and they cannot effectively meet the needs of multi-tenant architecture.

Method used

By creating multiple authentication service instances in one authentication service and introducing user identifiers to distinguish authentication requests from different tenants, using authentication plug-ins to perform authentication processing in the target authentication service instance, achieving multi-tenant isolation and avoiding The problems of high resource occupancy and high maintenance costs caused by multiple tenants opening multiple authentication services are caused by high resource occupancy and high maintenance costs.

Benefits of technology

This has achieved improved resource utilization and reduced costs, ensuring that each tenant can only access its authorized resources, and reducing resource costs and maintenance costs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094179A_ABST
    Figure CN119094179A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to a cloud service authentication method and device, equipment and a storage medium. The method comprises the following steps: in response to a user authentication request, calling an authentication module interface provided by a target authentication service instance to transmit a target user identifier in the user authentication request to an authentication plug-in configured in the target authentication service instance; the authentication module interface and the plug-in interface of the authentication plug-in are configured to transmit user identification parameters through user identification fields; the user authentication request is used for requesting to authenticate a target cloud service operated by a target user; calling the authentication plug-in to search a target authentication strategy matched with the target user identifier from an authentication strategy table configured in the target authentication service instance; the authentication strategy table is used for maintaining a pre-configured authentication strategy; the authentication strategy indicates the operation authority of the user for the cloud service; and authenticating the target cloud service operated by the target user based on the target authentication strategy to obtain an authentication result. Therefore, the resource utilization rate is improved, and the operation and maintenance cost and resource cost are reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to an authentication method, apparatus, device, and storage medium for a cloud service. Background Art

[0002] Currently, many public cloud providers ensure the security and stability of their cloud services by adopting authentication services based on a centralized security management framework.

[0003] To meet security requirements, the centralized security management framework provides each tenant with an independent authentication service, which authenticates each tenant's authentication requests. However, each additional tenant requires the creation of an authentication service. As the number of tenants increases, the number of authentication services required increases, leading to higher resource utilization, resource costs, and maintenance costs. Summary of the Invention

[0004] In order to solve the above technical problems, the embodiments of the present disclosure provide a cloud service authentication method, apparatus, device and storage medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a cloud service authentication method, the method comprising:

[0006] Obtaining a user authentication request; wherein the user authentication request carries a user identifier;

[0007] Determining a target authentication service instance from multiple authentication service instances;

[0008] Passing the user identifier to an authentication plug-in integrated in the target authentication service instance through an authentication module interface of the target authentication service instance; wherein the authentication module interface includes at least one of a role module interface, a security zone module interface, and a policy module interface;

[0009] By using the authentication plug-in, the authentication policy table in the target authentication service instance is searched using the user identifier to determine authentication policy information adapted to the user identifier; wherein the authentication policy table includes at least one of a role information table, a security zone information table, and a service information table;

[0010] Through the authentication plug-in, the user authentication request is authenticated based on the authentication policy information to generate an authentication result

[0011] In a second aspect, an embodiment of the present disclosure further provides an authentication device for a cloud service, the device comprising:

[0012] An authentication request acquisition module is used to obtain a user authentication request; wherein the user authentication request carries a user identifier;

[0013] An instance determination module, configured to determine a target authentication service instance from a plurality of authentication service instances;

[0014] A user identification transfer module, configured to transfer the user identification to an authentication plug-in integrated in the target authentication service instance through an authentication module interface of the target authentication service instance; wherein the authentication module interface includes at least one of a role module interface, a security zone module interface, and a policy module interface;

[0015] a user identification query module configured to query the authentication policy table in the target authentication service instance using the user identification through the authentication plug-in to determine authentication policy information adapted to the user identification; wherein the authentication policy table includes at least one of a role information table, a security zone information table, and a service information table;

[0016] The authentication execution module is used to perform authentication processing on the user authentication request based on the authentication policy information through the authentication plug-in and generate an authentication result.

[0017] In a third aspect, an embodiment of the present disclosure further provides an electronic device, the electronic device comprising:

[0018] processor;

[0019] a memory for storing executable instructions;

[0020] The processor is used to read executable instructions from the memory and execute the executable instructions to implement the cloud service authentication method described in any embodiment of the present disclosure.

[0021] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor implements the cloud service authentication method described in any embodiment of the present disclosure.

[0022] In a fifth aspect, an embodiment of the present disclosure further provides a computer program product, which is used to execute the cloud service authentication method described in any embodiment of the present disclosure.

[0023] The authentication method, apparatus, device and storage medium of the cloud service of the embodiment of the present disclosure can add a user identification field in advance to the role module interface, security zone module interface and policy module interface of the authentication service to improve the authentication module interface; add a user identification field to the role information table, security zone information table and service information table to improve the authentication policy table; add a user identification field to the authentication plug-in to improve the authentication plug-in; and integrate the authentication plug-in into the authentication service so that the authentication plug-in can be integrated into each authentication service instance to execute the corresponding authentication process; thus, the foundation is laid for creating multiple authentication service instances for one authentication service. Furthermore, one authentication service instance can be used to execute the authentication access of one tenant, realizing the authentication function of multi-tenant isolation, so as to ensure that only the tenant corresponding to the user identification can access specific resources and prevent unauthorized access. Therefore, when the authentication device receives a user authentication request, it can determine the target authentication service instance corresponding to the target user identifier in the multiple authentication service instances provided by the authentication service according to the user identifier, and pass the target user identifier to the authentication plug-in configured in the target authentication service instance for authentication by calling the authentication module interface provided by the target authentication service instance; in this way, each tenant can share the same authentication service, and each additional tenant will create an authentication service instance of the authentication service to implement its authentication process isolated from other tenants, avoiding the problems of high resource occupancy and high maintenance cost caused by multiple tenants opening multiple authentication services, thereby improving resource utilization and greatly reducing resource cost and maintenance cost because only one authentication service needs to be maintained. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0025] Figure 1 A flowchart of a cloud service authentication method provided by an embodiment of the present disclosure;

[0026] Figure 2 A schematic diagram of a process for determining a target authentication service instance in an embodiment of the present disclosure;

[0027] Figure 3 Schematic diagram of the process of determining the target shard in an embodiment of the present disclosure;

[0028] Figure 4 This is a schematic diagram of the process of assigning users to shards in an embodiment of the present disclosure;

[0029] Figure 5 A schematic diagram of the structure of an authentication device for a cloud service provided by an embodiment of the present disclosure;

[0030] Figure 6 A schematic structural diagram of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0031] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0032] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0033] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." Other terms are defined in the following description.

[0034] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0035] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0036] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0037] Currently, many public cloud providers utilize authentication services based on centralized security management frameworks to ensure the security and stability of their cloud services. In a distributed computing platform ecosystem, integrating a centralized security management framework into each component enables fine-grained data access control for those components, providing a centralized platform to manage permission policies across all components and offering centralized authentication services for the distributed computing platform. In some scenarios, when users access or operate cloud services, the centralized security management framework can provide a shared authentication method, allowing users from different tenants to authenticate and verify permissions through the same authentication interface. However, as the number of tenants increases and permission configuration becomes more complex, permission management becomes more difficult. Furthermore, different tenants may have different permission requirements, making a shared authentication method unsuitable for multi-tenant architectures. To ensure flexible management, in some scenarios, for tenants with higher security requirements, independent authentication services are provided for each tenant. However, each additional tenant requires the creation of an authentication service, resulting in high resource utilization and maintenance costs.

[0038] Based on the above situation, the embodiment of the present disclosure provides a solution that satisfies multiple tenants using the same authentication service and can achieve resource isolation and authentication policy isolation. By creating multiple authentication service instances in one authentication service and introducing user identifiers, it is used to distinguish authentication requests from different tenants and to distinguish corresponding authentication service instances. As a result, when the authentication device receives a user authentication request, it can determine the corresponding target authentication service instance based on the user identifier in the user authentication request and perform authentication based on the target authentication service instance. For each additional tenant, there is no need to create an authentication service for each tenant. Instead, it is only necessary to create an authentication service instance of the authentication service to implement its authentication process isolated from other tenants. This avoids the problems of high resource occupancy and high maintenance costs caused by multiple tenants opening up multiple authentication services, thereby improving resource utilization and greatly reducing resource costs and maintenance costs because only one authentication service needs to be maintained.

[0039] The authentication method for cloud services provided by the embodiments of the present disclosure can be applied to authentication scenarios when users access public cloud resources and services. The method can be executed by an authentication device for cloud services, which can be implemented by software and / or hardware, and the device can be integrated into a device with an authentication function. The device can be an electronic device, and the electronic device can include but is not limited to a smartphone, a laptop computer, a tablet computer (Tablet Personal Computer, Tablet PC), a desktop computer, a server, an edge computing platform or a server cluster. In the following embodiments, a device with an authentication function is referred to as an authentication device, and the authentication method for cloud services described in the following embodiments can be executed based on the authentication device.

[0040] Figure 1 The following is a flow chart showing a method for authenticating a cloud service provided by an embodiment of the present disclosure. Figure 1 As shown, the authentication method of the cloud service may include the following steps:

[0041] S110 : In response to a user authentication request, call an authentication module interface provided by a target authentication service instance to pass the target user identifier in the user authentication request to an authentication plug-in configured in the target authentication service instance.

[0042] The authentication module interface and the authentication plug-in's plug-in interface are configured to pass a user identification parameter via a user identification field. A user authentication request is used to request authentication for a target user to operate a target cloud service. A user authentication request is an access request that triggers the authentication process. The user authentication request carries the target user's identification, and the target authentication service instance is determined from multiple authentication service instances to authenticate the target user's operation of the target cloud service.

[0043] The authentication service instance is the core service of the authentication service. Administrators can create, modify or delete it through the web page provided by the authentication service. The authentication service instance is an authentication service instance of a tenant pre-created in the authentication service. The same authentication service includes multiple authentication service instances. The target authentication service instance is an authentication service instance corresponding to the target user identifier. Each authentication service instance is configured with an authentication module interface and an authentication plug-in. A user identification field is added to the authentication module interface of the authentication service instance. The target authentication module interface can pass parameters such as the target user identifier through the user identification field. The target user identifier is an identifier used to distinguish different tenants, and can be a user ID, etc. The target user operations on the target cloud service may include: login, access, service selection, configuration, data management, security maintenance and other operations performed by the target user on the cloud service.

[0044] The authentication module interface includes at least one of the following: the role module interface, the security zone module interface, and the policy module interface. The authentication module is the core component of the authentication service for implementing security management. Policy management, user and resource information management, plug-in support, and more can be performed through the authentication module interface. The role module interface, the security zone module interface, and the policy module interface are three key components of the authentication module interface, collectively supporting the access control and security policy management functions of the authentication service. For example, the role module interface is primarily used for operations on tenant information, including adding, deleting, and binding permissions for tenants. The security zone module interface allows administrators to allocate resources within the service into different security zones for better security policy management, such as creating, deleting, and updating security zones. The policy module interface is a key component for defining and managing security policies, which determine which tenants can access which resources and which operations they can perform, such as creating, updating, deleting, and retrieving policy information. An authentication plugin is integrated into the target authentication service instance and periodically pulls and executes policies from the authentication module.

[0045] In order to achieve multi-tenant isolation in an authentication service, the embodiment of the present disclosure has made multiple modifications to the authentication service. The first modification is to modify the authentication module interface in the authentication service, including: adding a user identification field to the role module interface, security zone module interface, and policy module interface to distinguish the authentication module interface by user identification, thereby achieving multi-user isolation. The second modification is to modify the authentication plug-in in the authentication service, including: adding a user identification field to the interface where the authentication plug-in pulls roles and policies from the authentication module, and integrating the authentication plug-in into the authentication service so that it can be included in each authentication service instance and execute the corresponding authentication process. The third modification is to modify the authentication policy table in the authentication service, including: adding a user identification field to the role information table, security zone information table, and service information table to distinguish authentication policies that do not use user identification. Thus, it is possible to distinguish authentication modules, authentication plug-ins, authentication policy tables, etc. based on user identification, and to create multiple authentication service instances for multiple users.

[0046] Specifically, the embodiments of the present disclosure can be implemented through an authentication device, which is deployed with an authentication service that can provide a centralized permission management framework and perform fine-grained permission access control on cloud services that provide big data products and services. A user can trigger a resource access operation based on the access page of a client device. In response to the user's triggered resource access operation, the client device obtains a unique target user identifier, adds it to the authentication request, generates a user authentication request carrying the target user identifier, and sends the user authentication request to the authentication device so that the authentication device authenticates the received user authentication request. The introduction of the target user identifier can implement a fine-grained permission control policy, ensuring that each user can only access the resources for which they are authorized. Since the authentication module interface of each authentication service instance in each authentication service group contains a user identifier, after determining the target authentication service instance corresponding to the user authentication request, the corresponding target user identifier can be assembled into the authentication request based on the authentication module interface of the target authentication service instance. By sending the authentication request to the authentication plug-in, the target user identifier is passed to the authentication plug-in integrated in the target authentication service instance.

[0047] S120: Call the authentication plug-in to search the authentication policy table configured in the target authentication service instance for a target authentication policy that is compatible with the target user identifier.

[0048] The authentication policy table is used to maintain pre-configured authentication policies; the authentication policies indicate the user's operation permissions for cloud services.

[0049] The authentication policy table includes at least one of a role information table, a security zone information table, and a service information table. The role information table contains user information and records the role to which a user belongs. A role is equivalent to a collection of users, and each role can be used to categorize users. For example, project administrators belong to the same role, and project operations and maintenance members belong to another role. Access control to system resources is achieved by assigning users to specific roles and assigning corresponding permissions to these roles. Therefore, role-based authentication is equivalent to authenticating users within roles. Role-based authentication only requires managing roles and role permissions, rather than directly managing the permissions of each user, simplifying permissions management. The security zone information table contains information such as the location and information of security zones, user IDs, etc. The security zone information table records the security zone to which resources belong. It can indicate the resource storage location, which users with certain permissions can access resources in which locations, and so on. Security zones are equivalent to resource collections, and security zones can be used to isolate resource permissions. The service information table contains records of authentication services, user IDs, and other information. It records the services associated with the tenant and indicates which users have certain permissions for which services.

[0050] Specifically, the authentication policy table may be stored in a preset database. Based on the target user ID, the authentication plug-in retrieves the authentication policy table containing the target user ID from the preset database and determines the authentication policy that matches the target user ID in the authentication policy table. For example, the authentication policy table may contain security zones and authentication service records that match the target user ID.

[0051] In some embodiments, authentication policies can be pre-configured in the authentication policy table, including one or more of the following: role-based authentication policy, used to indicate the operating authority of the role to which the user belongs for cloud services; security-based authentication policy, used to indicate the operating authority of the user for resources in the security zone; service-based authentication policy, used to indicate the operating authority of the user for services associated with the user.

[0052] Specifically, configuring a role-based authentication strategy can include categorizing users and assigning each category to a different role. For example, project administrators could be assigned to the same role, while project operations and maintenance staff could be assigned to another role. By assigning users to specific roles and assigning corresponding permissions to those roles, role-based authentication is equivalent to authenticating users within the role, simplifying permission management.

[0053] Configuring a security-based authentication policy may include: recording the security zone to which each cloud service resource belongs in an authentication policy table, where a security zone is equivalent to a resource collection, and recording the tenant with operation authority corresponding to each security zone.

[0054] Configuring a service-based authentication policy may include recording services associated with each tenant in an authentication policy table, reflecting which services the tenant has which permissions.

[0055] In the disclosed embodiment, an authentication policy adapted to a user identifier is configured in an authentication policy table to achieve authentication policy isolation. This allows the user to search the authentication policy table for a target authentication policy adapted to the target user identifier upon receiving a user authentication request, thereby improving authentication efficiency.

[0056] S130: Authenticate the target user to operate the target cloud service based on the target authentication policy to obtain an authentication result.

[0057] Operational permissions for the target cloud service refer to permissions for the entire cloud service or a specific service category within the cloud service. These permissions include permissions to create, manage, and configure cloud services, as well as permissions to operate specific resources such as storage buckets, virtual machines, and database instances. Authentication results can be either passed or failed. Passing the authentication allows the user to operate the requested target cloud service; failing the authentication prevents the user from operating the requested target cloud service.

[0058] Specifically, when the target authentication policy determined to be a role-based authentication policy is determined, it is determined whether the role to which the user belongs has the operation authority of the target cloud service. For example, if the target user's operation on the target cloud service is to configure the cloud service for authentication, if it is determined that the role to which the user belongs is a project administrator, it is determined that the target user's operation on the target cloud service is authenticated. When the target authentication policy determined to be adapted to the target user's identity is a security-based authentication policy, it is determined whether the target cloud service requested by the target user is in the security zone corresponding to the target user's identity. If so, it is determined that the authentication is passed. When the target authentication policy determined to be adapted to the target user's identity is a service-based authentication policy, it is determined whether the target cloud service requested by the target user is related to the target user's identity. If so, it is determined that the authentication is passed.

[0059] The authentication device authenticates the target user's operation on the target cloud service through the authentication plug-in to determine whether the user has the permission to operate specific resources. If the authentication result is authentication passed, it means that the user's operation meets the authentication policy requirements. The authentication plug-in will allow the user's access operation to continue, and the user can operate the target cloud service or access the resources they requested. If the authentication result is authentication failed, it means that the user's operation does not meet the authentication policy requirements. The authentication plug-in will reject the operation and may return an error message. The user cannot operate the target cloud service or access the resources they requested. In this way, if the authentication passes, fine-grained authorization can be performed based on the target user's identity and permissions to ensure that the user can only access the resources they are authorized to.

[0060] The authentication method for cloud services of the embodiments of the present disclosure, the authentication method, apparatus, device and storage medium for cloud services of the embodiments of the present disclosure can pre-add a user identification field to the role module interface, security zone module interface and policy module interface of the authentication service to improve the authentication module interface; add a user identification field to the role information table, security zone information table and service information table to improve the authentication policy table; add a user identification field to the authentication plug-in to improve the authentication plug-in; and integrate the authentication plug-in into the authentication service so that the authentication plug-in can be integrated into each authentication service instance to execute the corresponding authentication process; thus, the foundation is laid for creating multiple authentication service instances for one authentication service. Furthermore, one authentication service instance can be used to execute authentication access for one tenant, thereby realizing the authentication function of multi-tenant isolation, to ensure that only the tenant corresponding to the user identification can access specific resources, and to prevent unauthorized access. Therefore, when the authentication device receives a user authentication request, it can determine the target authentication service instance corresponding to the target user identifier in the multiple authentication service instances provided by the authentication service according to the user identifier, and pass the target user identifier to the authentication plug-in configured in the target authentication service instance for authentication by calling the authentication module interface provided by the target authentication service instance; in this way, each tenant can share the same authentication service, and each additional tenant will create an authentication service instance of the authentication service to implement its authentication process isolated from other tenants, avoiding the problems of high resource occupancy and high maintenance cost caused by multiple tenants opening multiple authentication services, thereby improving resource utilization and greatly reducing resource cost and maintenance cost because only one authentication service needs to be maintained.

[0061] Based on the authentication method of the cloud service provided by the embodiment of the present disclosure, by integrating the authentication plug-in into the authentication service, the authentication plug-in can be increased synchronously with the increase of the authentication service instance, so that each authentication service instance created has the authentication function. Therefore, when the number of tenants increases, the corresponding authentication service instance can be created based on the above method to perform authentication processing. However, if the architecture of the centralized security management framework of the authentication service is fixed, it does not have the ability to expand or shrink horizontally, so that the number of authentication service instances that can be created is limited and cannot adapt to the dynamic changes in the tenant scale. In order to improve resource utilization and adapt to the dynamic changes in the tenant scale, the authentication method of the cloud service provided by the embodiment of the present disclosure also includes a process of sharding the authentication service instance, storing the created authentication service instance in shards, so that at least one authentication service instance is stored in one shard, and dynamically adapting to changes in the user scale by adding or reducing shards. When the number of tenants increases, shards are added to accommodate more authentication service instances; when the number of tenants decreases, instances are released and shards are reduced to save resources. This allows for dynamic scaling of authentication services, rather than a fixed number of authentication service instances, improving resource utilization. Consequently, upon receiving a user authentication request, the authentication device can search for the target shard corresponding to the authentication service instance associated with the target user identifier carried in the request and perform authentication in the target shard.

[0062] In some embodiments, before executing the call to the authentication module interface provided by the target authentication service instance to pass the target user identifier in the user authentication request to the authentication plug-in configured in the target authentication service instance, a process of determining the target authentication service instance is also included. Exemplarily, the target authentication service instance is determined from multiple authentication service instances through a load balancing algorithm. For example, an authentication service instance is determined as the target authentication service instance by polling, and the user authentication request is assigned to the target authentication service instance; or, the authentication capability of each authentication service instance is determined by calculating the hardware configuration and processing capability of each authentication service instance, and the authentication service instance with the strongest authentication capability is determined as the target authentication service instance.

[0063] Reference Figure 2 As shown, Figure 2 A flowchart of determining a target authentication service instance provided in one embodiment of the present disclosure includes the following steps S210 to S230, wherein explanations of terms identical or corresponding to those in the above embodiments are omitted here.

[0064] S210 : In response to a user authentication request, call a load balancing node to determine an intermediate authentication service instance from multiple authentication service instances.

[0065] The intermediate authentication service instance is one of the authentication service instances, and is used to calculate the target slice to which the target user identifier belongs. The target slice contains one or more authentication service instances including the target authentication service instance.

[0066] Specifically, after receiving a user authentication request, a load balancing node can be invoked to perform load balancing calculations on multiple authentication service instances in the authentication service. An authentication service instance that meets the load balancing requirements is then determined as an intermediate authentication service instance to ensure that the intermediate authentication service instance has sufficient remaining computing resources to execute the computing task. Alternatively, in some embodiments, an intermediate authentication service instance can be randomly determined from authentication service instances with remaining computing resources.

[0067] In some embodiments, as an implementable manner of determining an intermediate authentication service instance from each authentication service instance, the method includes: determining an intermediate authentication service instance from each authentication service instance based on a target user identifier and a load balancing policy of the authentication service.

[0068] Specifically, based on the target user identifier, at least one authentication service instance containing the target user identifier is determined from each authentication service instance, and then, based on the load balancing policy of the authentication service, an intermediate authentication service instance is determined from the at least one authentication service instance. Exemplarily, when determining, based on the target user identifier, at least one authentication service instance containing the target user identifier from each authentication service instance can be determined by matching the target user identifier carried in the user authentication request with the target user identifier contained in the authentication module interface of each authentication service instance. Then, based on the load balancing policy of the authentication service, an intermediate authentication service instance is determined from the at least one matched authentication service instance.

[0069] After the intermediate authentication service instance is determined, the computing task of the target shard may be assigned to the intermediate authentication service instance, and the following step S220 is executed.

[0070] S220: Call the intermediate authentication service instance to determine the target shard to which the target user identifier belongs, and forward the user authentication request to the target shard.

[0071] A shard can be understood as a collection of authentication service instances. A shard is associated with a user ID, and each shard contains at least one authentication service instance. The target shard is the shard where the target authentication service instance resides. If multiple shards exist, the authentication processing for a user authentication request can be assigned to the target shard based on the target user ID carried in the request.

[0072] Specifically, multiple tenants' authentication service instances may be stored in the same shard. If a tenant has multiple authentication service instances, these instances may also be stored across multiple shards. Therefore, the authentication device leverages the computing power of intermediate authentication service instances and, based on a pre-defined sharding strategy or algorithm, determines the target shard to which the target user ID belongs. The pre-defined sharding algorithm can be a hash algorithm, a range algorithm, or other algorithms, and is not limited here.

[0073] Combine Figure 3 As shown, Figure 3 A schematic diagram of the target shard determination process provided in one embodiment of the present disclosure. For the user 001 authentication request, user 002 authentication request, and user 00x authentication request, respectively, corresponding to user 001, user 002, and user 00x, the authentication device uses a load balancing policy to determine an authentication service instance as an intermediate authentication service instance. Based on the intermediate authentication service instance, the device calculates the target shards to which the three user authentication requests belong. Based on the intermediate authentication service instance, the device forwards the three user authentication requests to their corresponding target shards, where authentication is performed using the authentication service instances within the target shards. For example, assuming that the target shard to which the authentication request of user 001 belongs is shard 0, the target shard to which the authentication request of user 002 belongs is shard 1, and the target shard to which the authentication request of user 00x belongs is shard 2, then based on the intermediate authentication service instance, the target user is identified as user 001, and the authentication request of user 002 is forwarded to shard 1, and the authentication request of user 00x is forwarded to shard 2.

[0074] In some embodiments, the specific implementation method of determining the target shard to which the target user identifier belongs includes: calling an intermediate authentication service instance to determine the target shard to which the target user identifier belongs based on the hash value of the target user identifier, the number of shards and the shard identifiers of each shard.

[0075] The number of shards refers to the number of shards, which can also be understood as the set number of service authentication instances. The shard identifier is used to distinguish different shards, and the shard identifier corresponds to the shard one-to-one.

[0076] Specifically, in order to find the target authentication service instance corresponding to the target user identifier, the target shard to which the target user identifier belongs can be determined first, so as to determine the target authentication service instance in the target shard. Exemplarily, the authentication device calls the intermediate authentication service instance to perform hash processing on the target user identifier to obtain the hash value of the target user identifier, and calculates the hash value of the target user identifier and the number of shards of the shard according to a preset algorithm to obtain a first processing result. The preset algorithm can be a remainder calculation. The first processing result is compared with the shard identifier of each shard, and the shard whose shard identifier is equal to the first processing result is determined to be the target shard. The specific hash function for hashing the target user identifier can be selected according to the scenario and is not limited here.

[0077] S230: Determine a target authentication service instance from multiple authentication service instances included in the target shard.

[0078] Specifically, after calculating the target shard to which the target user identifier belongs based on the intermediate authentication service instance, the calculation task of determining which authentication service instance in the target shard the target authentication service instance belongs to can be further assigned to the intermediate authentication service instance, and the authentication device calls the intermediate authentication service instance to make the determination. The target shard contains at least one authentication service instance. If the target shard contains one authentication service instance, the authentication service instance is directly determined as the target authentication service instance. If the target shard contains multiple authentication service instances, the intermediate authentication service instance can be used to determine an idle authentication service instance among the multiple authentication service instances as the target authentication service instance. This achieves load balancing between the authentication service instances in the target shard, thereby improving the overall performance and reliability of the system.

[0079] For example, continue to combine Figure 3 As shown, shard 0 contains authentication service instance 0 and authentication service instance 3, shard 1 contains authentication service instance 1 and authentication service instance 4, and shard 2 contains authentication service instance 2 and authentication service instance 5. Then, a target authentication service instance is determined in authentication service instance 0 and authentication service instance 3 to perform authentication of user 001's authentication request; a target authentication service instance is determined in authentication service instance 1 and authentication service instance 4 to perform authentication of user 002's authentication request; and a target authentication service instance is determined in authentication service instance 2 and authentication service instance 5 to perform authentication of user 00x's authentication request.

[0080] In some embodiments, the authentication method of the cloud service also includes a process of dividing or assigning the authentication service instance to each shard. The division process can be performed before the above-mentioned step S230, including: calling the authentication management service to determine the instance identifier of each authentication service instance; calling the authentication management service based on the instance identifier and the number of shards to determine the shard to which the authentication service instance belongs and store it.

[0081] The authentication management service is a core component in the centralized security management framework, providing various management services as a server. The instance identifier is used to distinguish between authentication service instances. The disclosed embodiments do not specify how the instance identifier is determined; as long as it can distinguish between authentication service instances, it is sufficient.

[0082] Specifically, the authentication device may determine the instance identifier of each authentication service instance and calculate the number of shards in some manner, and then allocate the shards to be stored in each authentication service instance according to the instance identifier and the number of shards.

[0083] In some embodiments, the specific implementation method of assigning and storing the authentication service instance to the shard includes: determining the instance identification range corresponding to each shard based on the number of shards and the range of instance identifications, then traversing the instance identifications to determine the instance identification range to which each instance identification belongs, assigning instance identifications with the same instance identification range to the same shard, and storing them.

[0084] In some embodiments, the specific implementation method of assigning and storing the authentication service instance to the shard includes: calling the authentication management service to perform hash operation based on the hash value of the instance identifier and the number of shards to obtain a hash result; and storing each authentication service instance with the same hash result to the same shard.

[0085] Specifically, the authentication device calls the authentication management service to perform hash processing on each instance identifier, obtains the hash value corresponding to the instance identifier of each authentication service instance, and performs hash operation processing based on the hash value of the instance identifier and the number of shards. For example, based on a preset hash algorithm, a remainder calculation is performed on the hash value of each instance identifier and the number of shards, and the calculated remainder is used as the hash result, and the authentication service instances corresponding to the instance identifiers with the same remainder are stored in the same shard.

[0086] In the above embodiment, one possible implementation of calling the authentication management service to determine the instance identifier of each authentication service instance includes: calling the authentication management service to configure the authentication service as a stateful deployment mode, and determining the instance identifier of each authentication service instance.

[0087] The stateful deployment mode of the authentication service refers to a mode in which the authentication device records and maintains client device information for each session during the authentication service deployment, allowing it to identify the client device and process requests based on the user's identity. This facilitates tracking user login status and session information, enabling fine-grained access control based on user identity and permissions.

[0088] Specifically, by changing the state deployment of the authentication service to a stateful deployment mode, a unique identifier (instance identifier) ​​can be assigned and stored for each authentication service instance. The instance identifier remains unchanged during the scaling of the authentication service, ensuring the stability, persistence and scalability of the authentication service. For example, a UUID (Universally Unique Identifier) ​​can be used to generate a globally unique instance identifier for each authentication service instance. A timestamp and a serial number can also be used to generate a globally unique instance identifier for each authentication service instance. The timestamp can ensure the temporal sequence of the instance identifier, while the serial number is used to distinguish different authentication service instances within the same timestamp.

[0089] Combine Figure 4 As shown, in stateful deployment mode, the user ID is calculated according to a preset algorithm to determine the shard to which the user belongs. The stored instance ID, authentication policy, and user ID are obtained from the preset database. The instance ID, authentication policy, and user ID belonging to shard one are stored in shard one, the instance ID, authentication policy, and target user ID belonging to shard two are stored in shard two, and the instance ID, authentication policy, and target user ID belonging to shard three are stored in shard three.

[0090] By storing multiple authentication service instances in multiple shards, load balancing can be achieved among the multiple shards to improve the overall performance and reliability of the system.

[0091] The cloud service authentication method provided by the disclosed embodiments improves the processing capacity and scalability of the authentication service by sharding authentication service instances. This allows the authentication service to handle a large number of user authentication and authorization requests. Sharding can distribute the authentication service's data and computing tasks across multiple nodes as the number of users increases, thereby enabling parallel processing and improving overall system performance. Furthermore, by creating multiple user authentication requirements as multiple authentication service instances within a single authentication service, the operation and maintenance of a single tenant, which previously required multiple tenants, is reduced to a single tenant, significantly reducing resource and maintenance costs.

[0092] The following is an embodiment of an authentication device for a cloud service provided by an embodiment of the present invention. This device and the authentication method for a cloud service of the above-mentioned embodiments belong to the same inventive concept. For details not fully described in the embodiment of the authentication device for a cloud service, please refer to the embodiment of the authentication method for the above-mentioned cloud service.

[0093] Figure 5 The following is a schematic diagram showing the structure of an authentication device for a cloud service provided by an embodiment of the present disclosure. Figure 5 As shown, the authentication device 500 of the cloud service may include:

[0094] The target user identification transfer module 510 is configured to, in response to a user authentication request, call an authentication module interface provided by a target authentication service instance to transfer the target user identification in the user authentication request to an authentication plug-in configured in the target authentication service instance; the authentication module interface and the plug-in interface of the authentication plug-in are configured to transfer a user identification parameter via a user identification field; the user authentication request is used to request authentication for the target user to operate the target cloud service;

[0095] A target authentication policy search module 520 is configured to call the authentication plug-in to search the authentication policy table configured in the target authentication service instance for a target authentication policy that is compatible with the target user identifier; the authentication policy table is configured to maintain pre-configured authentication policies; the authentication policy indicates the user's operation permissions for the cloud service;

[0096] The authentication module 530 is configured to authenticate the target user's operation of the target cloud service based on the target authentication policy to obtain an authentication result.

[0097] When the authentication device of the cloud service provided by the embodiment of the present disclosure executes the authentication method of the aforementioned cloud service, the authentication method, device, equipment and storage medium of the cloud service of the embodiment of the present disclosure can pre-add a user identification field to the role module interface, security zone module interface and policy module interface of the authentication service to improve the authentication module interface; add a user identification field to the role information table, security zone information table and service information table to improve the authentication policy table; add a user identification field to the authentication plug-in to improve the authentication plug-in; and integrate the authentication plug-in into the authentication service so that the authentication plug-in can be integrated into each authentication service instance to execute the corresponding authentication process; thus, the foundation is laid for creating multiple authentication service instances for one authentication service. Furthermore, one authentication service instance can be used to execute the authentication access of one tenant, realizing the authentication function of multi-tenant isolation, so as to ensure that only the tenant corresponding to the user identification can access specific resources and prevent unauthorized access. Therefore, when the authentication device receives a user authentication request, it can determine the target authentication service instance corresponding to the target user identifier in the multiple authentication service instances provided by the authentication service according to the user identifier, and pass the target user identifier to the authentication plug-in configured in the target authentication service instance for authentication by calling the authentication module interface provided by the target authentication service instance; in this way, each tenant can share the same authentication service, and each additional tenant will create an authentication service instance of the authentication service to implement its authentication process isolated from other tenants, avoiding the problems of high resource occupancy and high maintenance cost caused by multiple tenants opening multiple authentication services, thereby improving resource utilization and greatly reducing resource cost and maintenance cost because only one authentication service needs to be maintained.

[0098] In some embodiments, the cloud service authentication device 500 further includes an authentication policy configuration module for:

[0099] Receive a preconfigured authentication policy, where the authentication policy includes one or more of the following:

[0100] Role-based authentication policy, used to indicate the user's role's permissions for cloud service operations;

[0101] Security-based authentication policy, used to indicate the user's operation rights on resources in the security zone;

[0102] A service-based authentication policy is used to indicate a user's authority to operate services associated with the user.

[0103] In some embodiments, the cloud service authentication device 500 further includes a target authentication service instance determination module, which is configured to:

[0104] In response to a user authentication request, calling a load balancing node to determine an intermediate authentication service instance from multiple authentication service instances;

[0105] Calling the intermediate authentication service instance to determine the target shard to which the target user identifier belongs, and forwarding the user authentication request to the target shard;

[0106] The target authentication service instance is determined from multiple authentication service instances included in the target slice.

[0107] In some embodiments, the target authentication service instance determination module is specifically configured to:

[0108] The intermediate authentication service instance is called to determine the target shard to which the target user identifier belongs based on the hash value of the target user identifier, the number of shards, and the shard identifiers of each shard.

[0109] In some embodiments, the cloud service authentication device 500 further includes an authentication service instance attribution module, which is configured to:

[0110] Invoking the authentication management service to determine the instance identifier of each authentication service instance;

[0111] The authentication management service is called to determine the shard to which the authentication service instance belongs based on the instance identifier and the number of shards and store the shard.

[0112] In some embodiments, the authentication service instance attribution module is specifically configured to:

[0113] Calling the authentication management service to perform a hash operation based on the hash value of the instance identifier and the number of shards to obtain a hash result;

[0114] The authentication service instances having the same hash result are stored in the same shard.

[0115] In some embodiments, the authentication service instance attribution module is specifically configured to: call the authentication management service to configure the authentication service into a stateful deployment mode, and determine the instance identifier of each authentication service instance.

[0116] The cloud service authentication device provided by the embodiment of the present disclosure can execute the cloud service authentication method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0117] It is worth noting that in the embodiment of the authentication device for the above-mentioned cloud service, the various modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the various functional modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this disclosure.

[0118] The present disclosure also provides an electronic device that may include a processor and a memory, wherein the memory may be used to store executable instructions. The processor may be used to read the executable instructions from the memory and execute the executable instructions to implement the cloud service authentication method in the above embodiment.

[0119] Figure 6 A schematic structural diagram of an electronic device provided by an embodiment of the present disclosure is shown.

[0120] like Figure 6 As shown, the electronic device 600 may include a processing device 601 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. Various programs and data required for the operation of the electronic device 600 are also stored in the RAM 603. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output interface (I / O interface) 605 is also connected to the bus 604.

[0121] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data.

[0122] It should be noted that Figure 6 The electronic device 600 shown is only an example and should not limit the functions and scope of use of the embodiments of the present disclosure. Figure 6 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0123] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 609, or installed from the storage device 608, or installed from the ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the authentication method of the cloud service of any embodiment of the present disclosure are performed.

[0124] An embodiment of the present disclosure further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor implements the cloud service authentication method in any embodiment of the present disclosure.

[0125] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), etc., or any suitable combination thereof.

[0126] In some embodiments, the client and server can communicate using any currently known or later developed network protocol, such as HTTP, and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or later developed network.

[0127] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0128] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device executes the steps of the cloud service authentication method described in any embodiment of the present disclosure.

[0129] In embodiments of the present disclosure, computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0130] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the devices, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0131] The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, and without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chip (SOCs), complex programmable logic devices (CPLDs), and the like.

[0132] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0133] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0134] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0135] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A cloud service authentication method, characterized in that: include: In response to a user authentication request, calling an authentication module interface provided by a target authentication service instance to pass a target user identifier in the user authentication request to an authentication plug-in configured in the target authentication service instance; the authentication module interface and the plug-in interface of the authentication plug-in are configured to pass a user identifier parameter through a user identifier field; the user authentication request is used to request authentication of a target user operating a target cloud service; Calling the authentication plug-in to search for a target authentication policy that is compatible with the target user identifier from an authentication policy table configured in the target authentication service instance; The authentication policy table is used to maintain pre-configured authentication policies; the authentication policies indicate the user's operation permissions for cloud services; Based on the target authentication policy, the target user is authenticated to operate the target cloud service to obtain an authentication result.

2. The method according to claim 1, characterized in that The method further comprises: Receive a preconfigured authentication policy, the authentication policy including one or more of the following: Role-based authentication strategy, used to indicate the user's role's operation permissions for cloud services; Security-based authentication policy, used to indicate the user's operation rights on resources in the security zone; A service-based authentication policy is used to indicate a user's authority to operate services associated with the user.

3. The method according to claim 1, characterized in that Before calling the authentication module interface provided by the target authentication service instance to pass the target user identifier in the user authentication request to the authentication plug-in configured in the target authentication service instance, the method further includes: In response to a user authentication request, calling a load balancing node to determine an intermediate authentication service instance from multiple authentication service instances; Calling the intermediate authentication service instance to determine the target slice to which the target user identifier belongs, and forwarding the user authentication request to the target slice; The target authentication service instance is determined from a plurality of authentication service instances included in the target slice.

4. The method according to claim 3, characterized in that The calling of the intermediate authentication service instance to determine the target slice to which the target user identifier belongs includes: The intermediate authentication service instance is called to determine the target shard to which the target user identifier belongs based on the hash value of the target user identifier, the number of shards, and the shard identifiers of each shard.

5. The method according to claim 3, characterized in that: Before calling the target slice to determine the target authentication service instance from the multiple authentication service instances included in the target slice, each authentication service instance is pre-stored in each slice in the following manner: Calling the authentication management service to determine the instance identifier of each authentication service instance; The authentication management service is called to determine and store the shard to which the authentication service instance belongs based on the instance identifier and the number of shards.

6. The method according to claim 5, characterized in that The calling of the authentication management service to determine and store the shard to which the authentication service instance belongs based on the instance identifier and the number of shards includes: Calling the authentication management service to perform hash operation based on the hash value of the instance identifier and the number of shards to obtain a hash result; The authentication service instances having the same hash result are stored in the same shard.

7. The method according to claim 5, characterized in that The calling of the authentication management service to determine the instance identifier of each authentication service instance includes: The authentication management service is called to configure the authentication service into a stateful deployment mode, and the instance identifier of each authentication service instance is determined.

8. An authentication device for a cloud service, characterized in that: include: A target user identification transmission module is used to respond to a user authentication request, call an authentication module interface provided by a target authentication service instance to transmit the target user identification in the user authentication request to an authentication plug-in configured in the target authentication service instance; the authentication module interface and the plug-in interface of the authentication plug-in are configured to transmit a user identification parameter through a user identification field; the user authentication request is used to request authentication of the target user operating the target cloud service; A target authentication policy search module, used to call the authentication plug-in to search for a target authentication policy that is compatible with the target user identifier from the authentication policy table configured in the target authentication service instance; The authentication policy table is used to maintain pre-configured authentication policies; The authentication policy indicates the user's operation authority for the cloud service; The authentication module is used to authenticate the target user's operation of the target cloud service based on the target authentication policy to obtain an authentication result.

9. An electronic device, characterized in that: include: processor; A memory for storing executable instructions; The processor is used to read the executable instructions from the memory and execute the executable instructions to implement the cloud service authentication method described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the cloud service authentication method described in any one of claims 1 to 7.