Login-free identity verification method and device based on dynamic identity code and storage medium
Through device registration and dynamic identity code binding, tokens are generated and refreshed, the problem of repeated login for users in scenarios with high business level is solved, simplification of user login and data security is achieved, and the flexibility and security of the system are improved.
Patent Information
- Application Number
- CN202310507510.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-08
- Publication Date
- 2024-11-08
AI Technical Summary
In the scenario where the existing technology has a high level of business and the user has a dependency relationship with the terminal device, there are repetitive login problems, and the traditional login method has reliability, privacy and compatibility problems, and the login-free method implemented by cookies and sessions There are security and cumbersome login process issues.
Through device registration, the binding between physical devices and logical users is realized, and the identification code with a long valid period and a short valid period are generated based on the device binding information and timestamps. It is used to identify the terminal device and refresh the token to obtain the client Request and verify the validity of the token according to the verification code, update and save the identity code and token, and realize the dynamic identity code refreshing data access token.
Simplify user login operations in scenarios with high business level, ensure the security of requested data, and manually renew the identity code in case of system downtime, avoid large-scale failures, and improve system flexibility and security.
Smart Images

Figure CN118921171A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of Internet technology, and in particular to a method, device and storage medium for identity authentication without login based on a dynamic identity code. Background Art
[0002] With the development of Internet technology, more and more scenarios are undergoing digital and information transformation. Identity authentication is very important for information systems, which is not only related to the security of users' personal privacy, but also to the security of internal enterprise data.
[0003] Mobile device technology, encryption technology and network protocol technology are the core technologies of the current mainstream dynamic authentication and login-free authentication mechanism. The commonly used traditional login methods include cookies to achieve login-free. When logging in for the first time, the server will first use the md5 encryption algorithm to encrypt the secret key and user ID to obtain an encrypted string, and then encapsulate this string and account ID into a cookie object with the key ssid and pass it to the front end. The next time you log in, the browser will directly pass this ssid object to the server. At this time, the server does not need to query the server to verify whether the password is correct, and only needs to verify whether the encryption rule is correct. The server takes the user ID from the ssid and encrypts the user ID according to the encryption rules and keys known to the server. Then it compares it with the encrypted string sent from the front end. If they are the same, login-free is not required. However, this login method has reliability, privacy and compatibility issues that need to be considered, and cookies have an expiration time. If the user clears the browser cache or cookies, then you need to log in again. There is a cumbersome login process, and the same common Session to achieve login-free still has security issues. In the traditional C / S communication mode, each time a user requests a system service, he needs to enter information such as his account number and password on the client to complete identity recognition and verification, which causes inconvenience in operation. In some scenarios with high business levels and a dependency relationship between users and terminal devices, repetitive operations will seriously reduce users' willingness to use or work efficiency. Summary of the invention
[0004] The embodiment of the present application solves the problem of repeated user logins in scenarios with a high level of business and a dependency relationship between users and terminals by providing a method for login-free identity authentication based on a dynamic identity code, thereby simplifying user login operations in scenarios with a high level of business and a dependency relationship between users and terminal devices, while ensuring the security of requested data, and manually renewing identity codes in situations such as system downtime to avoid large-scale invalidation, thereby improving the flexibility of the system. At the same time, data access tokens are refreshed through dynamic identity codes, and system services are requested through tokens, thereby improving the security of the system.
[0005] In a first aspect, an embodiment of the present invention provides a method for login-free identity authentication based on a dynamic identity code, the method comprising:
[0006] Binding physical devices to logical users is achieved through device registration;
[0007] According to the device binding information and timestamp, an identity code with a long validity period and a data access token with a short validity period are generated and sent to the client. The identity code is used to identify the terminal device and refresh the token, and the token is used for actual data request access;
[0008] Obtaining a client request, extracting the identity code according to the request, and verifying the validity of the token refresh request according to the verification code;
[0009] The identity code and the token are updated and saved.
[0010] In combination with the first aspect, in a possible implementation, generating an identity code with a long validity period and a data access token with a short validity period includes: creating an identity authentication whitelist based on the user's first login information, and adding the device registration address to the identity authentication whitelist.
[0011] In combination with the first aspect, in a possible implementation, the identity code is used to identify the terminal device and refresh the token, including: verifying the identity code in the request header, and if correct, generating a new token and identity code and refreshing the validity period and cache before returning them to the client.
[0012] In combination with the first aspect, in a possible implementation manner, obtaining the client request, extracting the identity code according to the request, and verifying the validity of the token refresh request according to the verification code includes:
[0013] The physical identification of the login device and the token are obtained, the whitelist, the physical identification and the token are bound and saved, and a random identity code and a data access token with a globally unique validity period are generated.
[0014] In combination with the first aspect, in a possible implementation manner, updating and saving the identity code and the token includes:
[0015] Get relevant business requests initiated by the client;
[0016] Verify whether the token in the relevant service request is valid. If it is valid, continue to use it. If it is invalid, obtain a new token returned by the client using the identity code to request a token refresh interface;
[0017] The new token and the related service request are received, and the new token and the identity code are saved.
[0018] In a second aspect, an embodiment of the present invention provides a device for free login identity authentication based on a dynamic identity code, the device comprising:
[0019] Data binding module, used to bind physical devices to logical users through device registration;
[0020] The data generation module is used to generate an identity code with a long validity period and a data access token with a short validity period according to the device binding information and the timestamp, and send them to the client, wherein the identity code is used to identify the terminal device and refresh the token, and the token is used for the actual data request access;
[0021] A data verification module, used to obtain a client request, extract the identity code according to the request, and verify the validity of the token refresh request according to the verification code;
[0022] The data updating module is used to update and save the identity code and the token.
[0023] In combination with the second aspect, in a possible implementation, the data generation module creates an identity authentication whitelist based on the user's first login information, and adds the device registration address to the identity authentication whitelist.
[0024] In combination with the second aspect, in a possible implementation, the data generation module is used to verify the identity code in the request header. If correct, a new token and identity code are generated and the validity period and cache are refreshed before returning them to the client.
[0025] In combination with the second aspect, in a possible implementation method, the data verification module is used to obtain the physical identification of the login device and the token, bind and save the whitelist, the physical identification and the token, and generate a random identity code and data access token with a globally unique validity period.
[0026] In conjunction with the second aspect, in a possible implementation, the data update module is used to obtain a related service request initiated by the client;
[0027] Verify whether the token in the relevant service request is valid. If it is valid, continue to use it. If it is invalid, obtain a new token returned by the client using the identity code to request a token refresh interface;
[0028] The new token and the related service request are received, and the new token and the identity code are saved.
[0029] In a third aspect, an embodiment of the present invention provides a server for login-free identity authentication based on a dynamic identity code, the server comprising a memory and a processor;
[0030] The memory is used to store computer executable instructions;
[0031] The processor is used to execute the computer executable instructions to implement a method for login-free identity authentication based on a dynamic identity code and any method described in the method.
[0032] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores executable instructions. When a computer executes the executable instructions, it can implement a method for login-free identity authentication based on a dynamic identity code and any of the methods described therein.
[0033] One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages:
[0034] The embodiment of the present invention adopts a method for login-free identity authentication based on a dynamic identity code, which includes: generating an identity code with a long validity period and a data access token with a short validity period according to device binding information and a timestamp, and sending them to a client, wherein the identity code is used to identify the terminal device and refresh the token, and the token is used for actual data request access; obtaining a client request, and extracting the identity code according to the request, and verifying the validity of the token refresh request according to the verification code; updating and saving the identity code and the token; effectively solving the problem of repeated user logins in scenarios with a high level of business and a dependency relationship between users and terminals, thereby simplifying user login operations in scenarios with a high level of business and a dependency relationship between users and terminal devices, while ensuring the security of requested data, and manually renewing the identity code in situations such as system shutdown to avoid large-scale invalidation, thereby improving the flexibility of the system, and refreshing the data access token through the dynamic identity code, and requesting system services through the token, thereby improving the security of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments of the present invention or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0036] Figure 1 A flowchart of the steps of a method for free login identity authentication based on a dynamic identity code provided in an embodiment of the present application;
[0037] Figure 2 A flowchart of the steps for updating and saving the identity code and token provided in an embodiment of the present application;
[0038] Figure 3 A schematic diagram of a device for login-free identity authentication based on a dynamic identity code provided in an embodiment of the present application;
[0039] Figure 4 A schematic diagram of a server for dynamic identity code-based login-free identity authentication provided in an embodiment of the present application. DETAILED DESCRIPTION
[0040] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0041] At present, the commonly used traditional login methods include using cookies to achieve login-free. When logging in for the first time, the server will first use the md5 encryption algorithm to encrypt the key and user id to obtain an encrypted string, and then encapsulate this string and account id into a cookie object with the key ssid and pass it to the front end. The next time you log in, the browser will directly pass this ssid object to the server. At this time, the server does not need to query the server to verify whether the password is correct, and only needs to verify whether the encryption rule is correct. The server takes the user id from the ssid and encrypts the user id according to the encryption rules and keys known to the server. Then it compares it with the encrypted string sent from the front end. If they are the same, login-free is not required. However, this login method has reliability, privacy and compatibility issues that need to be considered, and cookies have an expiration time. If the user clears the browser cache or cookies, then you need to log in again. There is a cumbersome login process, and the common Session to achieve login-free still has security issues.
[0042] If the SessionID is stolen or hijacked, the attacker can use the ID to perform unauthorized access or operations. Server pressure: Session information needs to be saved on the server side. If the number of users is too large, the server load pressure will increase. Browser compatibility issues: Different browsers handle cookies and sessions differently, which may lead to some compatibility issues and many other problems. The dual token login method also has some disadvantages: For example, security issues: When the access token expires, the dual token login-free method uses the refresh token to re-obtain a new access token. But if the attacker intercepts the refresh token, they may use this token to obtain a new access token to gain access to the system. Complexity: Implementing the dual token login-free method requires additional code and logic. This may increase the difficulty of development and maintenance. In addition, this method may conflict with other authentication methods, thereby increasing the complexity of the entire authentication system, token management issues, etc. In summary, although the dual token login-free method is a commonly used authentication method, it also has problems in security, complexity, and token management.
[0043] The embodiment of the present invention provides a method for free login identity authentication based on a dynamic identity code, such as Figure 1 The method shown includes the following steps S101 to S104.
[0044] S101, binding the physical device and the logical user through device registration;
[0045] S102, generating an identity code with a long validity period and a data access token with a short validity period respectively according to the device binding information and the timestamp, and sending them to the client, wherein the identity code is used to identify the terminal device and refresh the token, and the token is used for actual data request access.
[0046] S103, obtaining the client request, extracting the identity code according to the request, and verifying the validity of the token refresh request according to the verification code.
[0047] S104, updating and saving the identity code and token.
[0048] In combination with the first aspect, in a possible implementation, generating an identity code with a long validity period and a data access token with a short validity period includes: creating an identity authentication whitelist based on the information of the user's first login, and adding the device registration address to the identity authentication whitelist. The present invention establishes a binding between a physical device and logical data through device registration, so that the system can obtain the identity of the requester and provide customized services without logging in, thereby improving the user-friendliness of the system.
[0049] The identity code is used to identify the terminal device and refresh the token, including: verifying the identity code in the request header. If correct, a new token and identity code are generated and the validity period and cache are refreshed before returning to the client.
[0050] Get the client request, extract the identity code according to the request, and verify the validity of the token refresh request according to the verification code, including: obtaining the physical identification and token of the login device, binding and saving the whitelist, physical identification and token, and generating a random identity code and data access token with a global unique validity period. Using the identity code to replace the account login process avoids the risk of account information leakage during data transmission; at the same time, the data access token is refreshed through the dynamic identity code, and the system service is requested through the token, which improves the security of the system.
[0051] In a possible implementation, the identity code and token are updated and saved, such as Figure 2 The process shown includes the following steps S201 to S203.
[0052] S201, obtaining relevant service requests initiated by the client.
[0053] S202, verify whether the token in the relevant business request is valid. If it is valid, continue to use it. If it is invalid, obtain a new token returned by the client using the identity code to request the token refresh interface.
[0054] S203, receiving a new token and related service request, and saving the new token and identity code.
[0055] A random ID Token is used as the device identity code, and the device binding information and timestamp encryption are used to generate JWT, which fully combines the characteristics of the former maintaining the status by the server and the latter stateless verification; at the same time, by caching the identity code, centralized management of the identity code is achieved. In special circumstances (such as system shutdown maintenance) and when the system is shut down, the identity code can be manually renewed to avoid large-scale invalidation, thereby improving the flexibility of the system.
[0056] In a specific embodiment provided by the present application, S1: the system administrator updates the business data table and creates several configuration accounts in advance; the server adds the relevant request addresses such as device registration to the identity authentication whitelist.
[0057] S2: For the client application on each terminal device used in the system, open its device registration login page and log in using the configured account.
[0058] S3: The server queries the database and verifies the submitted configuration account and password. If the verification is successful, a token JWT' (Json Web Token) with a validity period of T1 is generated based on the account and timestamp information and returned to the client. Otherwise, an error message is returned.
[0059] S4: If the client receives an error message, it continues to execute S2, otherwise it saves the JWT' returned by the server to the local cache and jumps to the device registration page.
[0060] S5: The client automatically obtains and fills in the physical identification of the device. The system administrator sets the device installation information through the client, selects the binding information of the device according to the basic business data and clicks Submit. After the client verifies the form data, it submits the request to the server with the locally cached JWT'. According to one embodiment of the present application, the device physical identification includes at least one or a combination of the following: device physical address (Media Access Control Address, MAC), international mobile equipment identity (International Mobile Equipment Identity, IMEI), international mobile subscriber identification number (International Mobile Subscriber Identification Number, IMSI) and browser fingerprint. Preferably, when the client is a Web application, the browser fingerprint is used as the physical identification of the device, otherwise the MAC address and other information are used.
[0061] S6: The server verifies whether the JWT' in the request is valid. If it is invalid, an error message is returned. Otherwise, the requested device data is saved to complete the device registration. At the same time, a globally unique random identity code with a validity period of T2 is generated, and a data access token JWT with a validity period of T2 is generated based on the device binding and timestamp information, and the identity code and JWT are returned to the client together. Preferably, a universally unique identifier (Universally Unique Identifier, UUID) is used as a dynamic identity code, and the mapping relationship between the registered device information and the identity code assigned by the system is cached in Redis, and the validity period T2 is set to 10 days. Preferably, when creating the JWT, the device binding information and timestamp are added to the payload, so that the server can identify the source of the request and ensure the uniqueness of the JWT, and the validity period T3 is set to 2 days.
[0062] S7: If the client receives an error message, it continues to execute S5, otherwise it saves the JWT and identity code returned by the server to the local cache.
[0063] S8: From now on, all business operation requests initiated by the client will automatically carry JWT.
[0064] S9: The server verifies whether the JWT in the request is valid. If it is invalid, an error message is returned. Otherwise, the business operation is performed normally and a response result is returned.
[0065] S10: If the client receives an error message, it uses the identity code to request the JWT refresh interface.
[0066] S11: The server verifies the identity code in the request header. If it is invalid, an error message is returned. Otherwise, a new JWT and identity code are generated and the validity period and cache are refreshed before being returned to the client.
[0067] S12: If the client receives an error message, it continues to execute S2, otherwise it executes S7.
[0068] The present invention adopts an identity code instead of an account number as a login identifier, thereby avoiding the risk of account information leakage during data transmission and the risk of inferring personal information based on the account number; at the same time, the data access token is refreshed through a dynamic identity code, and system services are requested through the token, wherein the identity code is valid for a long time and is only transmitted in the network when the token is generated or refreshed for the first time, with a smaller risk of exposure; the token is valid for a short time and is refreshed after it expires, thereby reducing the time window for theft and improving the security of the system as a whole.
[0069] The embodiment of the present invention provides a device for free login identity verification based on a dynamic identity code, such as Figure 3 The device shown comprises:
[0070] The data binding module 301 is used to implement the binding of a physical device and a logical user through device registration.
[0071] The data generation module 302 is used to generate an identity code with a long validity period and a data access token with a short validity period according to the device binding information and timestamp, and send them to the client, where the identity code is used to identify the terminal device and refresh the token, and the token is used for actual data request access; based on the user's first login information, create an identity authentication whitelist and add the device registration address to the identity authentication whitelist.
[0072] The data verification module 303 is used to obtain the client request, extract the identity code according to the request, and verify the validity of the token refresh request according to the verification code; it is used to obtain the physical identification and token of the login device, bind and save the whitelist, physical identification and token, and generate a random identity code and data access token with a globally unique validity period.
[0073] The data update module 304 is used to update and save the identity code and token. It is used to obtain the relevant business request initiated by the client; verify whether the token in the relevant business request is valid. If it is valid, continue to use it. If it is invalid, obtain the new token returned by the client using the identity code to request the token refresh interface; receive the new token and related business requests, and save the new token and identity code.
[0074] The device provided in the present application can simplify user login operations in some scenarios where the business level is high and the user has a dependent relationship with the terminal device, while ensuring the security of the requested data.
[0075] The devices or modules described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. For the convenience of description, the above devices are described in various modules according to their functions. When implementing this application, the functions of each module can be implemented in the same or multiple software and / or hardware. Of course, the module that implements a certain function can also be implemented by combining multiple sub-modules or sub-units.
[0076] The methods, devices or modules described in this application can be implemented in the form of computer-readable program codes. The controller can be implemented in any appropriate manner. For example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program codes (such as software or firmware) that can be executed by the (micro) processor, logic gates, switches, application-specific integrated circuits (English: Application Specific Integrated Circuit; Abbreviation: ASIC), programmable logic controllers and embedded microcontrollers. Examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code, the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included in it for implementing various functions can also be regarded as structures within the hardware component. Or even, the means for realizing various functions may be regarded as both a software module for realizing the method and a structure within a hardware component.
[0077] Some modules in the apparatus described in the present application can be described in the general context of computer executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, classes, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments, in which tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.
[0078] The embodiment of the present invention provides a server for free login identity authentication based on dynamic identity code, such as Figure 4 As shown, the server includes a memory 401 and a processor 402; the memory 401 is used to store computer executable instructions; the processor 402 is used to execute computer executable instructions to implement a method for login-free identity authentication based on a dynamic identity code and any one of its methods.
[0079] An embodiment of the present invention provides a computer-readable storage medium storing executable instructions. When a computer executes the executable instructions, a method for free-login identity authentication based on a dynamic identity code and any one of the methods thereof can be implemented.
[0080] The above storage media include but are not limited to random access memory (RAM), read-only memory (ROM), cache, hard disk (HDD) or memory card. The memory can be used to store computer program instructions.
[0081] Although the present application provides method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in this embodiment is only one way of executing the order of many steps and does not represent the only execution order. When the actual device or client product is executed, it can be executed in sequence or in parallel according to the method shown in this embodiment or the accompanying drawings (for example, in a parallel processor or multi-threaded processing environment).
[0082] It can be known from the description of the above implementation mode that a person skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary hardware. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, or it can be reflected in the implementation process of data migration. The computer software product can be stored in a storage medium, such as ROM / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a mobile terminal, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application or some parts of the embodiments.
[0083] The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. All or part of this application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld devices or portable devices, tablet devices, mobile communication terminals, multi-processor systems, microprocessor-based systems, programmable electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, etc.
[0084] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit the present application. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some or all of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the present application.
Claims
1. A method for free login identity authentication based on dynamic identity code, characterized in that: include: Binding physical devices to logical users is achieved through device registration; According to the device binding information and timestamp, an identity code with a long validity period and a data access token with a short validity period are generated and sent to the client. The identity code is used to identify the terminal device and refresh the token, and the token is used for actual data request access; Obtaining a client request, extracting the identity code according to the request, and verifying the validity of the token refresh request according to the verification code; The identity code and the token are updated and saved.
2. The method according to claim 1, characterized in that The generating of the identity code with a long validity period and the data access token with a short validity period includes: creating an identity authentication whitelist according to the information of the user's first login, and adding the device registration address to the identity authentication whitelist.
3. The method according to claim 1, characterized in that The identity code is used to identify the terminal device and refresh the token, including: verifying the identity code in the request header, generating a new token and identity code if correct, refreshing the validity period and cache, and returning them to the client.
4. The method according to claim 1, characterized in that The obtaining of the client request, extracting the identity code according to the request, and verifying the validity of the token refresh request according to the verification code includes: The physical identification of the login device and the token are obtained, the whitelist, the physical identification and the token are bound and saved, and a random identity code and a data access token with a globally unique validity period are generated.
5. The method according to claim 1, characterized in that The updating and saving of the identity code and the token comprises: Get relevant business requests initiated by the client; Verify whether the token in the relevant service request is valid. If it is valid, continue to use it. If it is invalid, obtain a new token returned by the client using the identity code to request a token refresh interface; The new token and the related service request are received, and the new token and the identity code are saved.
6. A device for login-free identity authentication based on a dynamic identity code, characterized in that: include: Data binding module, used to bind physical devices to logical users through device registration; The data generation module is used to generate an identity code with a long validity period and a data access token with a short validity period according to the device binding information and the timestamp, and send them to the client, wherein the identity code is used to identify the terminal device and refresh the token, and the token is used for the actual data request access; A data verification module, used to obtain a client request, extract the identity code according to the request, and verify the validity of the token refresh request according to the verification code; The data updating module is used to update and save the identity code and the token.
7. A server for free login identity authentication based on dynamic identity code, characterized in that: including memory and processor; The memory is used to store computer executable instructions; The processor is used to execute the computer executable instructions to implement the method according to any one of claims 1 to 5.
8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores executable instructions, and when a computer executes the executable instructions, the method according to any one of claims 1 to 5 can be implemented.
Citation Information
Cited By
Zero-trust gateway rapid authentication method and device based on one-time session fingerprint
CN121530625A
