User authentication method, system, server, terminal, network device and storage medium

The user authentication identifier is generated and verified by the user authentication server, which solves the problem of user identity information leakage and abuse in Internet applications, realizes the security protection of user information, and reduces the risk of identity information leakage.

CN115037486BActive Publication Date: 2024-12-06CHINA TELECOM CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110192506.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-02-20
Publication Date
2024-12-06
Estimated Expiration
2041-02-20

AI Technical Summary

Technical Problem

The leakage and abuse of user identity information in Internet applications have caused threats to user information security, especially in service applications that do not have real-name authentication. There is a risk of information leakage when users need to provide ID number information.

Method used

A user authentication method is proposed, which receives the user's authentication identification request through the authentication server, generates and stores the user authentication identification, and feeds it back to the user. The user does not need to directly provide identity information to the third-party application. The third-party application verifies the user through the authentication server. Identity, ensure that verification passes or fails information feedback, and sets the failure time to reduce the probability of information leakage.

Benefits of technology

Users can realize real-name authentication of third-party applications without providing identity information, reduce the probability of identity information leakage, improve user information security, and avoid information abuse and service threats.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115037486B_ABST
    Figure CN115037486B_ABST
Patent Text Reader

Abstract

The present disclosure proposes a user authentication method, system and server, terminal, network device and storage medium, which relates to the field of information security technology. A user authentication method disclosed in the present disclosure includes: receiving an authentication identification request from a user, the authentication identification request includes user identity information; generating and storing a user authentication identification according to the authentication identification request; feeding back the user authentication identification to the user so that the user can provide it to a third-party application; receiving a user authentication request from a third-party application; verifying the user authentication request according to the stored user authentication identification; and feeding back authentication pass information to the third-party application if the verification passes. Through such a method, the user does not need to provide identity information to a third-party application, that is, real-name authentication can be achieved in a third-party application, reducing the probability of leakage of user identity information and improving user information security.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of information security technology, and in particular to a user authentication method, system, server, terminal, network device, and storage medium. Background Art

[0002] Internet applications are providing users with an increasing number of services and features, making our lives more convenient. This can also lead to the leakage and abuse of personal privacy. Even some services that don't require real-name authentication require users' ID numbers during registration. This can be caused by inherent security vulnerabilities in the application system itself, or by malicious exploitation of user information, threatening user information security. Summary of the Invention

[0003] One purpose of the present disclosure is to improve the security protection of user information.

[0004] According to one aspect of some embodiments of the present disclosure, a user authentication method is proposed, including: receiving an authentication identification request from a user, the authentication identification request including user identity information; generating and storing a user authentication identification according to the authentication identification request; feeding back the user authentication identification to the user so that the user can provide it to a third-party application; receiving a user authentication request from a third-party application; verifying the user authentication request based on the stored user authentication identification; and if the verification is successful, feeding back authentication success information to the third-party application.

[0005] In some embodiments, the user authentication method further includes: in the event of a verification failure, feeding back authentication failure information to a third-party application.

[0006] In some embodiments, verifying the user authentication request according to the stored user authentication identifier includes: verifying whether the user authentication identifier in the user authentication request matches the stored user authentication identifier, if the match is successful, the verification is successful; if the match is unsuccessful, the verification is failed.

[0007] In some embodiments, the authentication identification request also includes a third-party application identification; verifying the user authentication request based on the stored user authentication identification includes: verifying whether the user authentication identification in the user authentication request matches the stored user authentication identification, and verifying whether the identification of the source third-party application of the user authentication request matches the third-party application identification in the authentication identification request corresponding to the user authentication identification; if the user authentication identification matches and the third-party application identification matches, it is determined that the verification is successful; otherwise, the verification fails.

[0008] In some embodiments, the authentication identifier request also includes an expiration time; and further includes: when the expiration time is reached, deleting the stored corresponding user authentication identifier so that when a user authentication request including the corresponding user authentication identifier is subsequently received, the verification fails.

[0009] Through this method, users do not need to provide their identity information to third-party applications, and can achieve real-name authentication in third-party applications, reducing the probability of leakage of user identity information and improving user information security.

[0010] According to one aspect of some embodiments of the present disclosure, a user authentication method is proposed, including: receiving a user authentication identifier from a user, wherein the user authentication identifier is generated and stored by an authentication server according to an authentication identifier request of the user, and the authentication identifier request includes user identity information; generating a user authentication request according to the user authentication identifier, and sending it to the authentication server, wherein the authentication server verifies the user authentication request according to the stored user authentication identifier, and feeds back authentication pass information if the verification is successful; upon receiving the authentication pass information, determining that the user authentication is successful.

[0011] In some embodiments, the user authentication method further includes: determining that the user authentication has failed when authentication failure information is received from the authentication server, wherein the authentication server feeds back the authentication failure information to the third-party application when the user authentication request fails to be verified according to the stored user authentication identifier.

[0012] In some embodiments, the user authentication method further includes: upon receiving an application request from the user, sending an authentication instruction to the user so that the user provides a user authentication identifier.

[0013] In some embodiments, the user authentication method further includes: feeding back an authentication result to the user, where the authentication result includes user authentication passing or user authentication failing.

[0014] According to one aspect of some embodiments of the present disclosure, a user authentication method is proposed, including: a user terminal sends an authentication identification request to an authentication server, wherein the authentication identification request includes user identity information, so that the authentication server generates a user authentication identification according to the authentication identification request and stores it; receiving the user authentication identification fed back by the authentication server and sending it to a third-party application, so that the third-party application generates a user authentication request according to the user authentication identification and sends it to the authentication server, wherein the authentication server verifies the user authentication request according to the stored user authentication identification, and feeds back authentication pass information if the verification is successful.

[0015] In some embodiments, the authentication identifier request further includes at least one of a third-party application identifier and an expiration time.

[0016] In some embodiments, the user authentication method further includes: sending an application request to a third-party application, and upon receiving an authentication instruction fed back by the third-party application, executing an operation of sending an authentication identification request to an authentication server.

[0017] In some embodiments, the user authentication method further includes: receiving an authentication result fed back by a third-party application, where the authentication result includes user authentication passing or user authentication failing.

[0018] According to one aspect of some embodiments of the present disclosure, an authentication server is proposed, including: an identification processing unit, configured to receive an authentication identification request from a user, the authentication identification request including user identity information; generate and store a user authentication identification according to the authentication identification request; feed back the user authentication identification to the user so that the user can provide it to a third-party application; an authentication unit, configured to receive a user authentication request from a third-party application; verify the user authentication request according to the stored user authentication identification; and if the verification is successful, feed back authentication success information to the third-party application.

[0019] According to one aspect of some embodiments of the present disclosure, an application server is proposed, including: an authentication identifier acquisition unit, configured to receive a user authentication identifier from a user, wherein the user authentication identifier is generated and stored by an authentication server according to an authentication identifier request of the user, and the authentication identifier request includes user identity information; an authentication request unit, configured to generate a user authentication request according to the user authentication identifier, and send it to the authentication server, wherein the authentication server verifies the user authentication request according to the stored user authentication identifier, and feeds back authentication pass information if the verification is successful; and upon receiving the authentication pass information, it is determined that the user authentication is successful.

[0020] According to one aspect of some embodiments of the present disclosure, a user terminal is proposed, including: an authentication identification request unit, configured so that the user terminal sends an authentication identification request to an authentication server, the authentication identification request including user identity information, so that the authentication server generates and stores a user authentication identification based on the authentication identification request; receives the user authentication identification fed back by the authentication server; an identification forwarding unit, configured to send the user authentication identification to a third-party application, so that the third-party application generates a user authentication request based on the user authentication identification, and sends it to the authentication server, wherein the authentication server verifies the user authentication request based on the stored user authentication identification, and feeds back authentication pass information if the verification is successful.

[0021] According to one aspect of some embodiments of the present disclosure, a network device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute any one of the above user authentication methods based on instructions stored in the memory.

[0022] According to one aspect of some embodiments of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the instructions are executed by a processor, the steps of any one of the user authentication methods described above are implemented.

[0023] According to one aspect of some embodiments of the present disclosure, a user authentication system is proposed, comprising: an authentication server, configured to execute any one of the user authentication methods described above executed by the authentication server; an application server, configured to execute any one of the user authentication methods described above executed by the application server; and a user terminal, configured to execute any one of the user authentication methods described above executed by the user terminal.

[0024] In such a user authentication system, users can authenticate themselves through the authentication server, obtain a user authentication identifier, and then provide the user authentication identifier to a third-party application. The third-party application uses the authentication server to authenticate itself, thereby preventing the third-party application from obtaining the user's real identity information and improving the security protection of the user's identity information. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present disclosure and constitute a part of the present disclosure. The exemplary embodiments of the present disclosure and their descriptions are used to explain the present disclosure and do not constitute an improper limitation of the present disclosure. In the drawings:

[0026] Figure 1 The present invention provides a flowchart of some embodiments of the user authentication method on the authentication server side.

[0027] Figure 2 Flowcharts of some embodiments of the user authentication method on the application server side of the present disclosure.

[0028] Figure 3 Flowcharts of some embodiments of the user authentication method on the user side of the present disclosure.

[0029] Figure 4 The following is a signaling flow chart of some embodiments of the user authentication method disclosed herein.

[0030] Figure 5 Schematic diagram of some embodiments of the authentication system disclosed herein.

[0031] Figure 6 Schematic diagram of some embodiments of the network device disclosed herein.

[0032] Figure 7 Schematic diagrams of other embodiments of the network device disclosed herein. DETAILED DESCRIPTION

[0033] The technical solution of the present disclosure is further described in detail below through the accompanying drawings and examples.

[0034] The flowcharts of some embodiments of the user authentication method on the authentication server side of the present disclosure are as follows: Figure 1 shown.

[0035] In step 101, the authentication server receives an authentication identification request from a user, which includes user identity information, such as the user's ID number, phone number, name, etc. In some embodiments, the authentication server may be owned and maintained by a credible organization, such as a public security agency or an operator.

[0036] In step 102, a user authentication identifier is generated and stored based on the authentication identifier request. In some embodiments, the user authentication identifier may be an authentication code, such as a verification code. In some embodiments, the authentication server may pre-store user real-name information and verify the user's identity by matching it with the user identity information provided by the user. If a match is successful, a user authentication identifier is generated and stored.

[0037] In some embodiments, the authentication server stores the user identification code for a certain time limit, which can be a predetermined time period, such as 1 to 5 minutes, or 10 minutes, a day, etc. After the time limit is reached, the stored corresponding user authentication identifier is deleted to make the user authentication identifier invalid.

[0038] In some embodiments, if the authentication identification request includes an expiration time, the authentication server will set a time limit for storing the user identification code according to the expiration time, thereby improving personalized adaptability to different applications or different users.

[0039] In step 103, the user authentication identifier is fed back to the user. In some embodiments, after obtaining the user authentication identifier, the user terminal provides it to a third-party application that needs to perform real-name authentication on the user. After obtaining the user authentication identifier, the third-party application sends a user authentication request to the authentication server, and the user authentication request includes the user authentication identifier.

[0040] In step 104 , a user authentication request is received from a third-party application.

[0041] In step 105, the authentication server verifies the user authentication request based on the stored user authentication identifier. In some embodiments, the verification method can be to match the user authentication identifier with the stored user authentication identifiers.

[0042] In step 106, it is determined whether the verification is successful. If the verification is successful, step 107 is executed; otherwise, step 108 is executed. In some embodiments, if the user authentication identifier in the user authentication request successfully matches the stored user authentication identifier, step 107 is executed; otherwise, step 108 is executed.

[0043] In step 107, the authentication server feeds back authentication success information to the third-party application.

[0044] In step 108, the authentication server feeds back authentication failure information to the third-party application.

[0045] Through this method, users do not need to provide their identity information to third-party applications, and can achieve real-name authentication in third-party applications, reducing the probability of leakage of user identity information and improving user information security.

[0046] In some embodiments, the authentication identifier request may also include a third-party application identifier of the third-party application that the user wants to obtain services from, and the authentication server may store the generated correspondence between the user authentication identifier and the third-party application identifier. The third-party application identifier may be the website address or application name of the third-party application.

[0047] When verifying a user authentication identifier from a third-party application, in addition to checking whether the user authentication identifier is stored, the third-party application's identifier, which originated the user authentication request, must also be verified to see if it matches the third-party application identifier corresponding to the user authentication identifier. If a match is found, the verification is considered successful, and the authentication server returns a message indicating that the authentication was successful to the third-party application. If at least one of the user authentication identifier or the third-party application identifier does not match, the verification is considered unsuccessful, and the authentication server returns a message indicating that the authentication failed to the third-party application.

[0048] Through this method, the authentication server can take into account the application sending the user authentication request during verification, ensuring that only the application sending the request matches the application for which the user authentication identifier was generated, thereby preventing the user authentication identifier from being stolen and used on other application platforms, safeguarding the rights and interests of users and platforms, and avoiding information leakage or service abuse.

[0049] In some embodiments, the authentication server can generate a user authentication identifier randomly. In other embodiments, the authentication server can generate the identifier by encrypting user identity information, such as the user's ID number, third-party application identifier, and expiration time, using a predetermined encryption algorithm. The encryption algorithm and key are known only to the authentication server. In some embodiments, different expiration times can result in different user authentication identifiers. In other embodiments, the key can be dynamic, further enhancing security.

[0050] This method can prevent the user authentication identifier from being deciphered to obtain the user's identity information, thereby improving the security protection of user information.

[0051] The flowcharts of some embodiments of the user authentication method on the application server side of the present disclosure are as follows: Figure 2 shown.

[0052] In step 201, the application server receives a user authentication identifier from the user, wherein the user authentication identifier is generated and stored by the authentication server according to the user's authentication identifier request, and the authentication identifier request includes the user's identity information. In some embodiments, the authentication server can generate the user authentication identifier in the manner described in step 102 above.

[0053] In step 202, a user authentication request is generated based on the user authentication identifier and sent to the authentication server. The authentication server verifies the user authentication request based on the stored user authentication identifier and, if the verification is successful, returns a message indicating that the authentication is successful. In some embodiments, the authentication server may perform authentication using any of the methods described above and return a result.

[0054] In step 203, if the authentication pass information is received, it is determined that the user authentication is successful. In some embodiments, if the authentication failure information is received, it is determined that the user authentication has failed, wherein the authentication server feeds back the authentication failure information to the third-party application if the user authentication request fails to be verified according to the stored user authentication identifier.

[0055] Through this method, the application server can achieve reliable authentication of the user's identity without obtaining the user's real identity information. While achieving real-name authentication of the user's identity, it reduces the application server's requirements for the security of the user's identity information and reduces the security responsibility that the application party needs to bear. At the same time, it also prevents the application server from abusing the user's identity information and improves the security of the user's identity information.

[0056] In some embodiments, as Figure 2 As shown, after the above step 203, the user authentication method on the application server side may further include step 204: feeding back the authentication result to the user, where the authentication result includes user authentication passing or user authentication failing.

[0057] This method enables users to obtain authentication results in a timely manner and then re-initiate authentication identification requests, thereby increasing the probability of obtaining application services.

[0058] In some embodiments, as Figure 2 As shown, before step 201, the user authentication method on the application server side may further include step 205: when the application server receives an application request from the user, the application server sends an authentication instruction to the user, prompting the user to provide a user authentication identifier. This method can proactively trigger the user identity authentication process, improve authentication efficiency, and reduce the probability of user authentication identifier failure.

[0059] In some embodiments, the application server can provide the user with its own application identifier (i.e., the third-party application identifier mentioned above) so that the user can carry it when requesting the user authentication identifier from the authentication server, thereby facilitating the generation of a user authentication identifier for the current application and improving authentication security and service security.

[0060] In some embodiments, the application server can also provide the user with the expiration time of the user authentication identifier so that the user can carry it when requesting the user authentication identifier from the authentication server, so that the authentication server's storage validity period setting for the user authentication identifier meets the application requirements, thereby meeting the authentication security requirements of the application server.

[0061] The flowcharts of some embodiments of the user authentication method on the user side of the present disclosure are as follows: Figure 3 shown.

[0062] In step 301, the user terminal sends an authentication identifier request to the authentication server, the authentication identifier request including user identity information, so that the authentication server generates and stores a user authentication identifier based on the authentication identifier request. In some embodiments, the authentication server can generate the user authentication identifier by any of the methods mentioned above.

[0063] In step 302, the user terminal receives the user authentication identifier fed back by the authentication server and sends it to the third-party application, so that the third-party application generates a user authentication request based on the user authentication identifier and sends it to the authentication server. The authentication server verifies the user authentication request based on the stored user authentication identifier and feeds back authentication success information if the verification is successful.

[0064] Through this method, when a user needs to request a third-party application, he or she can initiate authentication by initiating an authentication identification request to a trusted authentication server, without having to provide personal identity information to a third-party application with low credibility. This avoids leaking personal identity information while meeting the identity authentication requirements of the third-party application, thereby improving the security protection of personal information.

[0065] In some embodiments, as Figure 3 As shown, the user authentication method on the user side may further include step 303 after step 302 above: receiving an authentication result fed back by the third-party application, where the authentication result includes whether the user authentication passed or failed. In some embodiments, if the authentication passes, the user can use the corresponding functions of the third-party application; if the authentication fails, the user can choose not to use the third-party application or re-initiate an authentication identifier request to the authentication server.

[0066] In some embodiments, as Figure 3As shown, the user authentication method on the user side may further include step 304 before the above step 301, where the user terminal sends an application request to the third-party application, and executes step 301 when receiving an authentication instruction fed back by the third-party application.

[0067] Through this method, the user authentication identifier can be generated when the third-party application requires authentication, which reduces the probability of the user authentication identifier expiring and improves the application access efficiency.

[0068] In combination with the above-mentioned user authentication method on the user terminal side, the authentication server side and the application server side, the signaling flow chart of some embodiments of the user authentication method of the present disclosure is as follows: Figure 4 shown.

[0069] In 411 , when the application server 43 initiates an authentication request to the user, the user terminal 41 sends an authentication identification request to the authentication server 42 , carrying its own identity information.

[0070] In step 412, the authentication server 42 authenticates the user identity, generates a user authentication identifier if the authentication is successful, and feeds it back to the user terminal 41. The authentication server 42 stores the user authentication identifier and sets a validity period, deleting the user authentication identifier when the validity period expires.

[0071] In 413 , the user terminal 41 sends the user authentication identifier to the application server 43 .

[0072] In step 414 , the application server 43 requests the authentication server 42 to determine whether the user authentication identifier is valid.

[0073] In 415 , the authentication server 42 performs verification of the user authentication identifier based on the stored information.

[0074] In step 416, the authentication server 42 feeds back the authentication result to the application server 43. In some embodiments, if the authentication result indicates that the user has passed the authentication, the application server 43 opens the service to the user; otherwise, the user is blocked from using the corresponding function of the application.

[0075] In step 417 , the application server 43 feeds back the authentication result to the user terminal.

[0076] Through this method, users can authenticate their identities through the authentication server, obtain a user authentication identifier, and then provide the user authentication identifier to a third-party application. The third-party application uses the authentication server to authenticate its identity, thereby preventing the third-party application from obtaining the user's real identity information and improving the security protection of the user's identity information.

[0077] Schematic diagrams of some embodiments of the user terminal of the present disclosure are as follows Figure 5 shown.

[0078] The user terminal 51 includes an authentication identity request unit 511 and an identity forwarding unit 512 .

[0079] The authentication identifier request unit 511 can send an authentication identifier request to the authentication server and receive a user authentication identifier fed back by the authentication server. The authentication identifier request includes user identity information so that the authentication server can generate and store the user authentication identifier based on the authentication identifier request. In some embodiments, the authentication server can generate the user authentication identifier using any of the methods mentioned above.

[0080] The identification forwarding unit 512 can send the user authentication identification to a third-party application so that the third-party application generates a user authentication request based on the user authentication identification and sends it to the authentication server, wherein the authentication server verifies the user authentication request based on the stored user authentication identification and feeds back authentication success information if the verification is successful.

[0081] By using such a user terminal, when a user needs to request a third-party application, he or she can initiate authentication by initiating an authentication identification request to a trusted authentication server, without having to provide personal identity information to a third-party application with low credibility. This avoids leaking personal identity information while meeting the identity authentication requirements of the third-party application, thereby improving the security protection of personal information.

[0082] Schematic diagrams of some embodiments of the authentication server disclosed in the present invention are as follows Figure 5 shown.

[0083] The authentication server 52 includes an identification processing unit 521 and an authentication unit 522 .

[0084] The identification processing unit 521 is capable of receiving an authentication identification request from a user, generating and storing a user authentication identification based on the authentication identification request, and then feeding the user authentication identification back to the user. In some embodiments, the authentication identification request includes user identity information, such as the user's ID number, phone number, name, etc. In some embodiments, the authentication server may be owned and maintained by a credible organization, such as a public security agency or operator. In some embodiments, the user authentication identification may be an authentication code, such as a verification code.

[0085] In some embodiments, the identification processing unit 521 may pre-store user real-name information and complete the user identity verification by matching it with the user identity information provided by the user. If the match is successful, a user authentication identifier is generated and stored.

[0086] Authentication unit 522 can receive a user authentication request from a third-party application and verify the user authentication request based on a stored user authentication identifier. In some embodiments, the verification method can be to match the user authentication identifier with the stored user authentication identifiers. If the user authentication identifier in the user authentication request successfully matches the stored user authentication identifiers, a successful authentication message is fed back to the third-party application; otherwise, a failed authentication message is fed back to the third-party application.

[0087] Such an authentication server can act as a reliable third-party agency to relay identity authentication. Users do not need to provide their identity information to third-party applications, which means that real-name authentication can be achieved in third-party applications, reducing the probability of leakage of user identity information and improving user information security.

[0088] Schematic diagrams of some embodiments of the application server disclosed in the present invention are as follows Figure 5 shown.

[0089] The application server 53 includes an authentication identification obtaining unit 531 and an authentication requesting unit 532 .

[0090] The authentication identifier acquisition unit 531 can receive a user authentication identifier from a user, wherein the user authentication identifier is generated and stored by the authentication server according to the user's authentication identifier request, and the authentication identifier request includes user identity information.

[0091] The authentication request unit 532 can generate a user authentication request according to the user authentication identifier and send it to the authentication server. If the authentication pass information is received, it is determined that the user authentication is passed. In some embodiments, if the authentication failure information is received, it is determined that the user authentication fails.

[0092] Such an application server can achieve reliable authentication of user identity without obtaining the user's real identity information, thereby reducing the application server's requirements for the security of user identity information while achieving real-name authentication of the user's identity, and reducing the security responsibility that the application party needs to bear; at the same time, it also prevents the application server from abusing user identity information and improves the security of user identity information.

[0093] Schematic diagrams of some embodiments of the authentication system disclosed herein are as follows Figure 5 As shown. The authentication system includes a user terminal 51, an authentication server 52, and an application server 53. In some embodiments, the user terminal 51, the authentication server 52, and the application server 53 can each be any of the corresponding devices mentioned above, executing the steps of the user authentication method described above by the corresponding device. In some embodiments, the user terminal 51, the authentication server 52, and the application server 53 can also be the network devices mentioned below.

[0094] In such a user authentication system, users can authenticate themselves through the authentication server, obtain a user authentication identifier, and then provide the user authentication identifier to a third-party application. The third-party application uses the authentication server to authenticate itself, thereby preventing the third-party application from obtaining the user's real identity information and improving the security protection of the user's identity information.

[0095] A structural diagram of an embodiment of the network device disclosed in the present invention is shown in FIG. Figure 6 As shown, the network device can be any one of an authentication server, an application server or a user terminal. The network device includes a memory 601 and a processor 602. Among them: the memory 601 can be a disk, a flash memory or any other non-volatile storage medium. The memory is used to store the instructions in the corresponding embodiment of the user authentication method above. The processor 602 is coupled to the memory 601 and can be implemented as one or more integrated circuits, such as a microprocessor or a microcontroller. The processor 602 is used to execute the instructions stored in the memory, which can reduce the probability of leakage of user identity information and improve the security of user information.

[0096] In one embodiment, it is also possible to Figure 7 As shown, network device 700 includes memory 701 and processor 702. Processor 702 is coupled to memory 701 via BUS 703. Network device 700 can also be connected to external storage device 705 via storage interface 704 to access external data, and can also be connected to a network or another computer system (not shown) via network interface 706. Detailed description is omitted here.

[0097] In this embodiment, by storing data instructions in a memory and then processing the instructions through a processor, the probability of leakage of user identity information can be reduced and the security of user information can be improved.

[0098] In another embodiment, a computer-readable storage medium stores computer program instructions thereon, which, when executed by a processor, implement the steps of the method in the corresponding embodiment of the user authentication method. Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, devices, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transitory storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0099] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0100] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0101] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0102] The present disclosure has been described in detail so far. To avoid obscuring the concept of the present disclosure, some details known in the art have not been described. Based on the above description, those skilled in the art can fully understand how to implement the technical solutions disclosed herein.

[0103] The methods and apparatus of the present disclosure may be implemented in many ways. For example, the methods and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above order of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above, unless otherwise specifically stated. In addition, in some embodiments, the present disclosure may also be implemented as programs recorded in a recording medium, which include machine-readable instructions for implementing the methods according to the present disclosure. Therefore, the present disclosure also covers recording media that store programs for executing the methods according to the present disclosure.

[0104] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present disclosure and not to limit it. Although the present disclosure has been described in detail with reference to the preferred embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present disclosure can still be modified or some technical features can be replaced by equivalents without departing from the spirit of the technical solutions of the present disclosure, which should all be included in the scope of the technical solutions requested for protection in the present disclosure.

Claims

1. A user authentication method, comprising: Receiving an authentication identification request from a user, wherein the authentication identification request includes user identity information and a third-party application identification, wherein the authentication identification request is sent by a user terminal and does not pass through a third-party application; Generate and store a user authentication identifier according to the authentication identifier request; Feeding back the user authentication identifier to the user so that the user can provide it to a third-party application; Receiving a user authentication request from the third-party application; Verifying the user authentication request according to the stored user authentication identifier includes: verifying whether the user authentication identifier in the user authentication request matches the stored user authentication identifier, and verifying whether the identifier of the source third-party application of the user authentication request matches the third-party application identifier in the authentication identifier request corresponding to the user authentication identifier; if the user authentication identifier matches and the third-party application identifier matches, determining that the verification is passed; otherwise, the verification is failed; If the verification is successful, authentication success information is fed back to the third-party application.

2. The method according to claim 1, further comprising: In the event of a verification failure, authentication failure information is fed back to the third-party application.

3. The method according to claim 1 or 2, wherein: The authentication identification request also includes an expiration time; The method further includes: when the expiration time is reached, deleting the stored corresponding user authentication identifier, so that when a user authentication request including the corresponding user authentication identifier is subsequently received, the verification fails.

4. A user authentication method, comprising: The user terminal sends an authentication identification request to the authentication server, wherein the authentication identification request includes user identity information and a third-party application identifier, so that the authentication server generates and stores a user authentication identifier according to the authentication identification request, wherein the authentication identification request does not pass through the third-party application; Receive the user authentication identifier fed back by the authentication server and send it to a third-party application, so that the third-party application generates a user authentication request according to the user authentication identifier and sends it to the authentication server, wherein the authentication server verifies the user authentication request according to the stored user authentication identifier, and verifies whether the identifier of the source third-party application of the user authentication request matches the third-party application identifier in the authentication identifier request corresponding to the user authentication identifier; if the user authentication identifier matches and the third-party application identifier matches, determine that the verification is successful; otherwise, the verification fails; if the verification is successful, feedback authentication success information is given.

5. The method according to claim 4, wherein: The authentication identification request also includes an expiration time.

6. The method according to claim 4, further comprising: An application request is sent to a third-party application, and upon receiving an authentication instruction fed back by the third-party application, an operation of sending an authentication identification request to an authentication server is executed.

7. The method according to claim 4, further comprising: An authentication result fed back by the third-party application is received, where the authentication result includes user authentication passing or user authentication failing.

8. An authentication server, comprising: The identification processing unit is configured to receive an authentication identification request from a user, wherein the authentication identification request includes user identity information and a third-party application identification, wherein the authentication identification request is sent by a user terminal and does not pass through a third-party application; generate and store a user authentication identification according to the authentication identification request; and feed back the user authentication identification to the user so that the user can provide it to a third-party application; The authentication unit is configured to receive a user authentication request from the third-party application; verify whether the user authentication identifier in the user authentication request matches the stored user authentication identifier, and verify whether the identifier of the source third-party application of the user authentication request matches the third-party application identifier in the authentication identifier request corresponding to the user authentication identifier; if the user authentication identifier matches and the third-party application identifier matches, determine that the verification is successful; otherwise, the verification fails; if the verification is successful, feedback authentication success information to the third-party application.

9. A user terminal, comprising: An authentication identification request unit is configured to send an authentication identification request to an authentication server, wherein the authentication identification request includes user identity information and a third-party application identifier, so that the authentication server generates and stores a user authentication identification according to the authentication identification request, wherein the authentication identification request does not pass through the third-party application; and receive the user authentication identification fed back by the authentication server; The identification forwarding unit is configured to send the user authentication identification to a third-party application so that the third-party application generates a user authentication request according to the user authentication identification and sends it to an authentication server, wherein the authentication server verifies the user authentication request according to the stored user authentication identification, and verifies whether the identification of the source third-party application of the user authentication request matches the third-party application identification in the authentication identification request corresponding to the user authentication identification. If the user authentication identification matches and the third-party application identification matches, it is determined that the verification is successful; otherwise, the verification fails. If the verification is successful, authentication success information is fed back.

10. A network device comprising: Memory; as well as A processor coupled to the memory, the processor being configured to execute the method according to any one of claims 1 to 7 based on instructions stored in the memory.

11. A computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, implement the steps of the method according to any one of claims 1 to 7.

12. A user authentication system, comprising: An authentication server configured to execute the method according to any one of claims 1 to 3; A user terminal, configured to execute the method according to any one of claims 4 to 7; and The application server is configured as: Receiving a user authentication identifier from a user, wherein the user authentication identifier is generated and stored by an authentication server according to an authentication identifier request of the user, and the authentication identifier request includes user identity information; A user authentication request is generated according to the user authentication identifier, and sent to an authentication server, wherein the authentication server verifies whether the user authentication identifier in the user authentication request matches the stored user authentication identifier, and verifies whether the identifier of the source third-party application of the user authentication request matches the third-party application identifier in the authentication identifier request corresponding to the user authentication identifier; if the user authentication identifier matches and the third-party application identifier matches, it is determined that the verification is passed; otherwise, the verification fails; if the verification is passed, authentication pass information is fed back; When the authentication success information is received, it is determined that the user authentication is successful.

13. The system according to claim 12, wherein: The application server is also configured to: When receiving authentication failure information from the authentication server, it is determined that the user authentication has failed, wherein when the authentication server fails to verify the user authentication request according to the stored user authentication identifier, the authentication server feeds back the authentication failure information to the third-party application.

14. The system according to claim 12, wherein: The application server is also configured to: When receiving an application request from a user, an authentication instruction is sent to the user so that the user provides the user authentication identifier.

15. The system according to any one of claims 12 to 14, wherein: The application server is also configured to: The authentication result is fed back to the user, and the authentication result includes whether the user authentication passes or fails.