CN115865383A - Cloud desktop authentication management method and system, electronic device and readable storage medium - Google Patents
Cloud desktop authentication management method and system, electronic device and readable storage medium Download PDFInfo
- Publication number
- CN115865383A CN115865383A CN202111118045.5A CN202111118045A CN115865383A CN 115865383 A CN115865383 A CN 115865383A CN 202111118045 A CN202111118045 A CN 202111118045A CN 115865383 A CN115865383 A CN 115865383A
- Authority
- CN
- China
- Prior art keywords
- data center
- client terminal
- authentication
- personal information
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Abstract
The application provides an authentication management method and system of a cloud desktop, an electronic device and a computer readable storage medium, wherein the authentication management method of the cloud desktop comprises the following steps: receiving a login authentication request sent by a client terminal; wherein the login authentication request comprises: user personal information; obtaining a token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system; and returning the first session identification to the client terminal.
Description
Technical Field
The embodiment of the application relates to the technical field of cloud computing, in particular to an authentication management method and system of a cloud desktop, electronic equipment and a computer readable storage medium.
Background
With the development of cloud computing technology, especially with the increasing demand of remote office, the related deployment of cloud desktops is increasing, and more enterprises adopt private or public cloud desktop systems to perfect remote office scenes, so that the daily office needs are met.
With the increasing scale of cloud desktop base groups, the establishment of multiple data centers is a very important scenario, and users need to be authenticated for the needs of user access, the current authentication method needs to perform authentication certification in each data center respectively, the authentication certification process is complicated, and multiple data centers may have repeated authentication certification situations.
Disclosure of Invention
The embodiment of the application provides a cloud desktop authentication management method and system, electronic equipment and a computer readable storage medium.
In a first aspect, an embodiment of the present application provides an authentication management method for a cloud desktop, which is applied to a data center server or a data center system, and the method includes: receiving a login authentication request sent by a client terminal; wherein the login authentication request comprises: user personal information; obtaining a token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system; and returning the first session identification to the client terminal.
In a second aspect, an embodiment of the present application provides an electronic device, including: at least one processor; the storage is provided with at least one program, and when the at least one program is executed by the at least one processor, the authentication management method of the cloud desktop is realized.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the method for managing authentication of a cloud desktop is implemented.
In a fourth aspect, an embodiment of the present application provides an authentication management system for a cloud desktop, including: the client terminal is used for sending a login authentication request to the data center server or the data center system; wherein the login authentication request comprises: user personal information; receiving a first session identifier sent by the data center server or the data center system; the data center server or the data center system is used for receiving a login authentication request sent by the client terminal; obtaining a token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system; and returning the first session identification to the client terminal.
According to the authentication management method for the cloud desktop, the data center server or the data center system obtains the token corresponding to the personal information of the user from the multi-data center unified authentication server or the multi-data center unified authentication system, multi-user authentication is uniformly achieved through the multi-data center unified authentication server or the multi-data center unified authentication system, authentication and authentication are not needed to be conducted in each data center, the authentication and authentication process is simple, and the situation that the multiple data centers can have repeated authentication and authentication is avoided.
Drawings
Fig. 1 is a flowchart of an authentication management method for a cloud desktop according to an embodiment of the present application;
fig. 2 is an interaction diagram of an authentication management method for a cloud desktop according to an example of the embodiment of the present application;
fig. 3 is a block diagram illustrating an authentication management apparatus of a cloud desktop according to another embodiment of the present disclosure;
fig. 4 is a block diagram of a system for authentication management of a cloud desktop according to another embodiment of the present application.
Detailed Description
In order to enable those skilled in the art to better understand the technical solution of the present application, the following describes in detail an authentication management method and system for a cloud desktop, an electronic device, and a computer-readable storage medium provided in the present application with reference to the accompanying drawings.
Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but which may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In case of conflict, the embodiments and features of the embodiments of the present application can be combined with each other.
As used herein, the term "and/or" includes any and all combinations of at least one of the associated listed items.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," 8230; \8230 "; when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of at least one other feature, integer, step, operation, element, component, and/or group thereof.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present application and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
Fig. 1 is a flowchart of an authentication management method of a cloud desktop according to an embodiment of the present application.
In a first aspect, referring to fig. 1, an embodiment of the present application provides an authentication management method for a cloud desktop, which is applied to a data center server or a data center system, and the method includes:
In some exemplary embodiments, the client terminal may be provided in any hardware device, such as a mobile terminal, a personal computer, and the like.
In the embodiment of the application, the personal information of the user may be any personal information of the user, such as a user name and a password for logging in a cloud desktop.
In some exemplary embodiments, obtaining a token corresponding to personal information of a user from a multi-data center unified authentication server or a multi-data center unified authentication system includes: sending an acquisition request to a multi-data center unified authentication server or a multi-data center unified authentication system; wherein, the obtaining request comprises: user personal information; and receiving a token (token) corresponding to the personal information of the user returned by the multi-data center unified authentication server or the multi-data center unified authentication system.
In the embodiment of the application, after receiving an acquisition request, a multi-data center unified authentication server or a multi-data center unified authentication system authenticates a user according to user personal information in the acquisition request, and sends a token corresponding to the user personal information to a data center server or a data center system when the authentication is passed; when the authentication fails, the token corresponding to the personal information of the user is not sent to the data center server or the data center system, and information indicating authentication failure can be sent to the data center server or the data center system.
In some exemplary embodiments, after obtaining the token corresponding to the personal information of the user from the multi-data center unified authentication server or the multi-data center unified authentication system, the method further includes: and locally caching the token corresponding to the personal information of the user.
In some exemplary embodiments, when a token returned by the multi-data center unified authentication server or the multi-data center unified authentication system is received, valid time of the token sent by the multi-data center unified authentication server or the multi-data center unified authentication system may also be received, and after the valid time of the token is received, the token fails and needs to be obtained from the multi-data center unified authentication server or the multi-data center unified authentication system again.
In some exemplary embodiments, after receiving the login authentication request sent by the client terminal, the method further includes: determining whether a token corresponding to the personal information of the user is cached locally; and under the condition that the token corresponding to the personal information of the user is not cached locally, continuously executing the step of acquiring the token corresponding to the personal information of the user from the multi-data center unified authentication server or the multi-data center unified authentication system.
In some exemplary embodiments, in a case that the token corresponding to the personal information of the user is locally cached, returning a second session identifier to the client terminal; or, determining whether to return a second session identifier to the client terminal according to a preset client terminal management strategy; and in the case that the second session identification is determined to be returned to the client terminal, continuing to execute the step of returning the second session identification to the client terminal.
In some exemplary embodiments, determining whether to return the second session identification to the client terminal according to a preset client terminal management policy includes: determining whether to allow multiple client terminals to log in simultaneously according to a preset client terminal management strategy; and under the condition that the multiple client terminals are allowed to log in simultaneously, returning the second session identification to the client terminals.
In some exemplary embodiments, determining whether to return the second session identifier to the client terminal according to a preset client terminal management policy includes: determining whether a plurality of client terminals are allowed to log in simultaneously according to a preset client terminal management strategy; and returning the second session identification to the client terminal under the condition that a plurality of client terminals are allowed to log in simultaneously.
The embodiment of the application does not limit the client terminal management strategy, and the user can set the strategy according to actual needs.
In some exemplary embodiments, after returning the first session identification to the client terminal, the method further comprises: and under the condition that the client terminal does not receive the operation instruction within the preset time, the first session identifier is invalid. The first session identification fails to mean that the session link between the client terminal and the data center server or the data center system is broken.
In some exemplary embodiments, after returning the second session identifier to the client terminal, the method further comprises: and under the condition that the client terminal does not receive the operation instruction within the preset time, the second session identifier is invalid. The second session identification failure means that the session link between the client terminal and the data center server or the data center system is disconnected.
According to the authentication management method for the cloud desktop, the data center server or the data center system obtains the token corresponding to the personal information of the user from the multi-data center unified authentication server or the multi-data center unified authentication system, multi-user authentication is uniformly achieved through the multi-data center unified authentication server or the multi-data center unified authentication system, authentication and authentication are not needed to be conducted in each data center, the authentication and authentication process is simple, and the situation that the multiple data centers can have repeated authentication and authentication is avoided.
In some exemplary embodiments, the data center server or the data center system maintains the token corresponding to the personal information of the user, instead of maintaining the token corresponding to the personal information of the user by the client terminal, so that a plurality of client terminals can log in the cloud desktop at the same time, and when the plurality of client terminals log in the cloud desktop at the same time, the personal information of the user only needs to be authenticated once, thereby reducing the pressure of authentication and improving the stability of the system.
An example is listed below to illustrate the authentication management method of the cloud desktop, and the listed example is only for convenience of description and is not used to limit the protection scope of the embodiment of the present application.
Examples of the invention
As shown in fig. 2, the authentication management method of the cloud desktop includes:
step 200, the client terminal sends a login authentication request to the data center server; wherein, the login authentication request comprises: user personal information.
In this step, the user personal information includes: and logging in a user name and a password of the cloud desktop.
Step 201, a data center server sends an acquisition request to a multi-data center unified authentication server; wherein, the obtaining request comprises: user personal information.
Step 202, the multi-data center unified authentication server returns a token corresponding to the personal information of the user to the data center server.
Step 203, the data center server caches the token corresponding to the user personal information locally, and returns the first session identifier (SessionID 1) to the client terminal one.
Step 204, the client terminal sends a login authentication request to the data center server; wherein, the login authentication request comprises: user personal information.
Step 205, the data center server returns a second session identifier (SessionID 2) to the second client terminal.
Step 206, the first session identifier is invalid as soon as the client terminal does not receive the operation instruction within the preset time.
Step 207, the second client terminal does not receive the operation instruction within the preset time, and the second session identifier is invalid.
In a second aspect, another embodiment of the present application provides an electronic device, including: at least one processor; the authentication management method of the cloud desktop comprises the steps that at least one program is stored in the memory, and when the at least one program is executed by at least one processor, the authentication management method of the cloud desktop is realized.
Wherein, the processor is a device with data processing capability, which includes but is not limited to a Central Processing Unit (CPU) and the like; memory is a device with data storage capabilities including, but not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), FLASH memory (FLASH).
In some embodiments, the processor, memory, and in turn other components of the computing device are connected to each other by a bus.
In a third aspect, another embodiment of the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements any one of the above authentication management methods for a cloud desktop.
Fig. 3 is a block diagram of an authentication management apparatus for a cloud desktop according to another embodiment of the present disclosure.
In a fourth aspect, another embodiment of the present application provides an authentication management apparatus (e.g., a data center server) for a cloud desktop, including: a communication module 301, configured to receive a login authentication request sent by a client terminal; wherein, the login authentication request comprises: user personal information; an obtaining module 302, configured to obtain a token corresponding to personal information of a user from a multi-datacenter unified authentication server or a multi-datacenter unified authentication system; the communication module 301 is further configured to: the first session identification is returned to the client terminal.
In some exemplary embodiments, the obtaining module 302 is further configured to: determining whether a token corresponding to the personal information of the user is cached locally; and under the condition that the token corresponding to the personal information of the user is not cached locally, continuously executing the step of acquiring the token corresponding to the personal information of the user from the multi-data center unified authentication server or the multi-data center unified authentication system.
In some exemplary embodiments, the communication module 301 is further configured to: and returning the second session identifier to the client terminal under the condition that the token corresponding to the personal information of the user is locally cached.
In some exemplary embodiments, the communication module 301 is further configured to: determining whether to return a second session identifier to the client terminal according to a preset client terminal management strategy; and in case that the second session identification is determined to be returned to the client terminal, continuing to execute the step of returning the second session identification to the client terminal.
In some exemplary embodiments, the communication module 301 is specifically configured to determine whether to return the second session identifier to the client terminal according to a preset client terminal management policy by using the following manner: determining whether to allow multiple client terminals to log in simultaneously according to a preset client terminal management strategy; and under the condition that the multiple client terminals are allowed to log in simultaneously, returning the second session identification to the client terminals.
In some exemplary embodiments, the communication module 301 is further configured to: in case the client terminal is not operated within a preset time, the first session identity is disabled.
In some exemplary embodiments, the obtaining module 302 is specifically configured to: sending an acquisition request to a multi-data center unified authentication server or a multi-data center unified authentication system; wherein, the obtaining request comprises: user personal information; and receiving a token corresponding to the user personal information returned by the multi-data center unified authentication server or the multi-data center unified authentication system.
The specific implementation process of the authentication management device for the cloud desktop is the same as that of the authentication management method for the cloud desktop in the foregoing embodiment, and is not described here again.
Fig. 4 is a block diagram of a system for authentication management of a cloud desktop according to another embodiment of the present application.
In a fifth aspect, another embodiment of the present application provides an authentication management system for a cloud desktop, including:
a client terminal 401, configured to send a login authentication request to a data center server or a data center system; wherein, the login authentication request comprises: user personal information; receiving a first session identifier sent by a data center server or a data center system; a data center server or data center system 402 for receiving a login authentication request sent by a client terminal; obtaining a token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system; the first session identification is returned to the client terminal.
In some exemplary embodiments, the data center server or data center system 402 is further configured to: determining whether a token corresponding to the personal information of the user is cached locally; and under the condition that the token corresponding to the personal information of the user is not cached locally, continuously executing the step of acquiring the token corresponding to the personal information of the user from the multi-data center unified authentication server or the multi-data center unified authentication system.
In some exemplary embodiments, the data center server or data center system 402 is further configured to: and returning the second session identifier to the client terminal under the condition that the token corresponding to the personal information of the user is locally cached.
In some exemplary embodiments, the data center server or data center system 402 is further configured to: determining whether to return a second session identifier to the client terminal according to a preset client terminal management strategy;
and in case that the second session identification is determined to be returned to the client terminal, continuing to execute the step of returning the second session identification to the client terminal.
In some exemplary embodiments, the data center server or the data center system 402 is specifically configured to determine whether to return the second session identifier to the client terminal according to a preset client terminal management policy by using the following method: determining whether to allow multiple client terminals to log in simultaneously according to a preset client terminal management strategy; and under the condition that the multiple client terminals are allowed to log in simultaneously, returning the second session identification to the client terminals.
In some exemplary embodiments, the data center server or data center system 402 is further configured to: in case the client terminal is not operated within a preset time, the first session identification is disabled.
In some exemplary embodiments, the data center server or the data center system 402 is specifically configured to obtain the token corresponding to the personal information of the user from the multiple data center unified authentication server or the multiple data center unified authentication system by the following steps: sending an acquisition request to a multi-data center unified authentication server or a multi-data center unified authentication system; wherein, the obtaining request comprises: user personal information; receiving tokens corresponding to the personal information of the user returned by the multi-data center unified authentication server or the multi-data center unified authentication system;
further comprising: a multi-data center unified authentication server or a multi-data center unified authentication system 403, configured to receive an acquisition request sent by a data center server or a data center system; and authenticating the user according to the personal information of the user in the acquisition request, and sending a token corresponding to the personal information of the user to a data center server or a data center system when the authentication is passed.
The embodiment of the application does not limit the physical implementation of the data center system and the multi-data center unified authentication system, for example, the data center system and the multi-data center unified authentication system may be a cluster, such as a distributed cluster, a multi-place multi-center cluster, and the like.
The specific implementation process of the authentication management system of the cloud desktop is the same as that of the authentication management method of the cloud desktop in the foregoing embodiment, and is not described here again.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, or suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purposes of limitation. In some instances, features, characteristics and/or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics and/or elements described in connection with other embodiments, unless expressly stated otherwise, as would be apparent to one skilled in the art. It will therefore be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the application as set forth in the appended claims.
Claims (10)
1. An authentication management method of a cloud desktop is applied to a data center server or a data center system, and comprises the following steps:
receiving a login authentication request sent by a client terminal; wherein the login authentication request comprises: user personal information;
obtaining a token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system;
and returning the first session identification to the client terminal.
2. The authentication management method of the cloud desktop according to claim 1, after receiving the login authentication request sent by the client terminal, the method further comprising:
determining whether a token corresponding to the personal information of the user is cached locally;
and under the condition that the token corresponding to the user personal information is not cached locally, continuously executing the step of acquiring the token corresponding to the user personal information from the multi-data center unified authentication server or the multi-data center unified authentication system.
3. The authentication management method of the cloud desktop according to claim 2, the method further comprising:
and returning a second session identifier to the client terminal under the condition that the token corresponding to the user personal information is locally cached.
4. The authentication management method of the cloud desktop according to claim 3, wherein before returning the second session identifier to the client terminal, the method further comprises:
determining whether to return the second session identifier to the client terminal according to a preset client terminal management strategy;
and under the condition that the second session identification is confirmed to be returned to the client terminal, continuing to execute the step of returning the second session identification to the client terminal.
5. The authentication management method of the cloud desktop according to claim 4, wherein the determining whether to return the second session identifier to the client terminal according to a preset client terminal management policy includes:
determining whether to allow multiple client terminals to log in simultaneously according to a preset client terminal management strategy;
and under the condition that a plurality of client terminals are allowed to log in simultaneously, returning the second session identification to the client terminals.
6. The authentication management method of the cloud desktop according to claim 1, wherein after the first session identifier is returned to the client terminal, the method further comprises:
and under the condition that the client terminal does not receive the operation instruction within the preset time, the first session identifier is invalid.
7. The cloud desktop authentication management method according to any one of claims 1 to 6, wherein the obtaining the token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system includes:
sending an acquisition request to the multi-data center unified authentication server or the multi-data center unified authentication system; wherein the obtaining request comprises: the user personal information;
and receiving a token corresponding to the personal information of the user returned by the multi-data center unified authentication server or the multi-data center unified authentication system.
8. An electronic device, comprising:
at least one processor;
a memory having at least one program stored thereon, the at least one program, when executed by the at least one processor, implementing the authentication management method of the cloud desktop of any of claims 1-7.
9. A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the authentication management method of a cloud desktop according to any one of claims 1 to 7.
10. An authentication management system of a cloud desktop, comprising:
the client terminal is used for sending a login authentication request to the data center server or the data center system; wherein the login authentication request comprises: user personal information; receiving a first session identifier sent by the data center server or the data center system;
the data center server or the data center system is used for receiving a login authentication request sent by the client terminal; obtaining a token corresponding to the personal information of the user from a multi-data center unified authentication server or a multi-data center unified authentication system; and returning the first session identification to the client terminal.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111118045.5A CN115865383A (en) | 2021-09-23 | 2021-09-23 | Cloud desktop authentication management method and system, electronic device and readable storage medium |
| PCT/CN2022/108227 WO2023045548A1 (en) | 2021-09-23 | 2022-07-27 | Cloud desktop authentication management method and system, and electronic device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111118045.5A CN115865383A (en) | 2021-09-23 | 2021-09-23 | Cloud desktop authentication management method and system, electronic device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115865383A true CN115865383A (en) | 2023-03-28 |
Family
ID=85652408
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111118045.5A Pending CN115865383A (en) | 2021-09-23 | 2021-09-23 | Cloud desktop authentication management method and system, electronic device and readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115865383A (en) |
| WO (1) | WO2023045548A1 (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102857484B (en) * | 2011-07-01 | 2015-11-25 | 阿里巴巴集团控股有限公司 | A kind of method, system and device realizing single-sign-on |
| CN106375270B (en) * | 2015-07-24 | 2020-12-08 | 华为技术有限公司 | Token generation and authentication method and authentication server |
| US10764273B2 (en) * | 2018-06-28 | 2020-09-01 | Oracle International Corporation | Session synchronization across multiple devices in an identity cloud service |
| CN109587126B (en) * | 2018-11-26 | 2022-12-09 | 平安科技（深圳）有限公司 | User authentication method and system |
-
2021
- 2021-09-23 CN CN202111118045.5A patent/CN115865383A/en active Pending
-
2022
- 2022-07-27 WO PCT/CN2022/108227 patent/WO2023045548A1/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023045548A1 (en) | 2023-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2019246872B2 (en) | Tiered connection pooling methods, systems and computer readable storage media | |
| AU2017242765A1 (en) | Method and device for registering biometric identity and authenticating biometric identity | |
| US8347086B2 (en) | System and method for automatically detecting and then self-repairing corrupt, modified of non-existent files via a communication medium | |
| CN112491776B (en) | Security authentication method and related equipment | |
| CN108965250B (en) | Digital certificate installation method and system | |
| CN110365701B (en) | Client terminal equipment management method and device, computing equipment and storage medium | |
| CN103841560A (en) | Method and equipment to enhance SIM card reliability | |
| CN113132402B (en) | Single sign-on method and system | |
| CN107040560A (en) | A kind of method for processing business and device based on business platform | |
| US8706875B2 (en) | Sharing access to application located on a smart card for clients in parallel | |
| CN113055185A (en) | Token-based authentication method and device, storage medium and electronic device | |
| CN104065674A (en) | Terminal device and information processing method | |
| US7761468B2 (en) | Supporting multiple security mechanisms in a database driver | |
| CN115865383A (en) | Cloud desktop authentication management method and system, electronic device and readable storage medium | |
| CN115065703A (en) | Internet of things system, authentication and communication method thereof and related equipment | |
| CN111988146B (en) | Identity verification method, device, equipment and machine readable storage medium | |
| US10055596B1 (en) | Data protection system | |
| US9928386B1 (en) | Data protection system | |
| CN115098528B (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
| CN113794716B (en) | Network access authentication method, device and equipment for terminal equipment and readable storage medium | |
| US20230254149A1 (en) | Probabilistic data structure for managing tokens | |
| CN114091119A (en) | Information processing method, information processing device, electronic equipment and computer readable storage medium | |
| CN117081782A (en) | Network access method, system, computer equipment and storage medium | |
| CN116208376A (en) | Single sign-on method and device, electronic equipment and storage medium | |
| CN116861402A (en) | Login certificate management method and device, terminal equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication |