WO2019037373A1 - 身份验证 - Google Patents

身份验证 Download PDF

Info

Publication number
WO2019037373A1
WO2019037373A1 PCT/CN2017/119701 CN2017119701W WO2019037373A1 WO 2019037373 A1 WO2019037373 A1 WO 2019037373A1 CN 2017119701 W CN2017119701 W CN 2017119701W WO 2019037373 A1 WO2019037373 A1 WO 2019037373A1
Authority
WO
WIPO (PCT)
Prior art keywords
password
user
client
additional password
server
Prior art date
Application number
PCT/CN2017/119701
Other languages
English (en)
French (fr)
Inventor
周天冀
Original Assignee
北京三快在线科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京三快在线科技有限公司 filed Critical 北京三快在线科技有限公司
Priority to CA3068090A priority Critical patent/CA3068090A1/en
Priority to EP17922615.4A priority patent/EP3618381A4/en
Priority to KR1020197035648A priority patent/KR102307665B1/ko
Priority to JP2019565469A priority patent/JP6936340B2/ja
Priority to US16/619,931 priority patent/US20200213293A1/en
Publication of WO2019037373A1 publication Critical patent/WO2019037373A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/36—User authentication by graphic or iconic representation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint

Definitions

  • This application relates to authentication.
  • the website or application asks the user to set a username and password, and at the same time requires the user to set a mobile phone number or mailbox associated with the username and password for easy access. Authentication or password retrieval.
  • the embodiment of the present application provides an identity verification method, and the security of the identity verification method has been improved.
  • an embodiment of the present application provides an identity verification method, including:
  • the client on the terminal device obtains the user identifier and password to be verified in response to the user's identity verification operation
  • the client obtains an additional password according to the user identifier
  • the client sends an authentication request to the server, wherein the authentication request includes the user identification, the password, and the additional password to enable the server to respond to the identity verification request based on the
  • the user ID, password, and additional password stored on the server are authenticated.
  • an embodiment of the present application provides an identity verification method, including:
  • the server obtains an additional password that matches the user identifier carried in the user registration request according to the received user registration request;
  • the server stores the additional password in association with the user identifier
  • the server performs identity verification according to the received identity verification request, where the identity verification request includes a user identity to be verified, a password, and an additional password stored on the client associated with the user identity.
  • the embodiment of the present application further provides a terminal device, including:
  • the machine readable storage medium stores machine executable instructions executable by the processor, the processor being caused by the machine executable instructions:
  • the server Sending an authentication request to the server, wherein the authentication request includes the user identification, the password, and the additional password to enable the server to be based on the storage on the server in response to the identity verification request User ID, password, and additional password for authentication.
  • the client on the terminal device obtains the user identifier and password to be verified in response to the identity verification operation of the user; the client obtains an additional password according to the user identifier; the client Sending an authentication request to the server, wherein the authentication request includes the user identifier, the password, and the additional password to enable the server to be stored on the server in response to the identity verification request User ID, password, and additional password for authentication.
  • the verification method disclosed in the embodiment of the present application effectively authenticates the user by combining the additional password, thereby effectively improving the security of the user identity verification, and effectively avoiding the leakage of the user account information caused by the theft of the registration password.
  • the thief can not obtain the additional password when the other client authenticates. Therefore, even if the user name and password are stolen, the authentication cannot be completed, and the user account cannot be successfully logged in to obtain the user's account. information.
  • FIG. 3 is a flowchart of an identity verification method provided by an embodiment of the present application.
  • FIG. 5 is a flowchart of an identity verification method according to an embodiment of the present application.
  • FIG. 6 is a flowchart of an identity verification method provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of identity verification logic provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of identity verification logic provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of identity verification logic provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of identity verification logic provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of hardware of a terminal device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a hardware of a server provided by an embodiment of the present application.
  • account information may also be leaked.
  • a user usually logs in to a website or an application on a different terminal device.
  • a malware in a terminal device steals a user's login password and then logs in to the user's account at another terminal device, the user account can be made. Information security will be threatened.
  • An authentication method disclosed by the example of the present application includes: Step 100 to Step 120.
  • Step 100 Obtain a user identifier and password to be verified according to the user's identity verification operation.
  • the user login portal set on the website page or the application page for authentication. After the authentication is passed, Access to personal information in the user's account is allowed.
  • the user authentication function is triggered, and the user identifier and the password to be verified are obtained by calling the website page or the interface of the application page to be sent to the server for identity verification.
  • the user identifier may be a username.
  • Step 110 obtaining an additional password.
  • the client stores an additional password, and can directly read the additional password stored locally by the client, that is, read and perform the identity verification.
  • An additional password pre-stored by the operating client.
  • the client can initiate a request for generating an additional password to the server through an entry that generates an additional password on the interface. To get an additional password. Then, get the additional password entered by the user for the authentication operation.
  • the user may first log in on the terminal device or the registered terminal device that has already logged in, and then initiate a request for generating an additional password to the server through the preset entry for obtaining the additional password on the client, and the server will add the matching with the login user.
  • the password is sent to the logged in client that initiated the request for display.
  • the additional password is then manually entered by the user into the client to be logged in.
  • the user through the client to be logged in, that is, the client that does not store the additional password, initiates the generation of the additional password to the server through the preset entry for generating the additional password, such as generating the additional password button, if at least the user identifier is input.
  • Request to get an additional password An additional password matching the entered user identification is transmitted by the server through a registration information receiving manner that matches the entered user identification. Then, the user adds the additional password in the received information to the client to be logged in manually.
  • the additional password may be generated by a client or may be generated by a server that performs authentication.
  • the additional password is stored at the same time on the client side and the server side performing authentication.
  • Step 120 Send the user identifier and password to be verified and the additional password to the server for identity verification.
  • the user identifier to be verified, the password to be verified, and the additional password are obtained, the user identifier to be verified, the password to be verified, and the additional password are further sent to the server, so that the server identifies the user. verification.
  • the to-be-verified user identifier, the to-be-verified password, and the additional password may be sent to the server for authenticating, and the server may use the password to be verified based on the user identifier and pre-stored user information. And verifying the additional password separately, and confirming that the user identity verification is successful when the password to be verified and the additional password are all verified.
  • the password to be verified is encrypted by the additional password, and then the encrypted password to be verified and the user identifier to be verified are sent to the server for authentication, first by the server. Acquiring a pre-stored additional password matched by the user identifier, decrypting the encrypted password to be verified based on a pre-stored additional password matching the user identifier, and verifying the password to be verified obtained after decryption, When the password to be verified obtained after decryption is verified, the user authentication is confirmed to be successful.
  • the additional password used for encryption is inconsistent with the pre-stored additional password that is obtained by the server and matches the user identifier, even if the password that is input by the user is the registration password, the password to be verified after decryption is not the user-entered password to be verified. The password will also verify the failure.
  • the identity verification method disclosed in the embodiment of the present application obtains the user identifier and password to be verified according to the identity verification operation of the user, and obtains the corresponding additional password, and then the user identifier and password to be verified and the additional The password is sent to the server for authentication.
  • the user is authenticated by combining the additional password, thereby effectively improving the security of the user identity verification, and effectively avoiding the theft of the user account information caused by the password theft.
  • the thief can authenticate with other clients.
  • the additional password cannot be obtained, even if the user name and password are stolen, the authentication cannot be completed, the user account cannot be successfully logged in, and the user's account is obtained. information.
  • An identity verification method disclosed in another embodiment of the present application includes: Step 200 to Step 240.
  • Step 200 In response to the registration operation of the user, the client sends a user registration request to obtain an additional password of the user.
  • the page of the website or application can be provided with a user registration portal for user registration so that the user can manage personal information through the website or application and can use the richer functionality provided by the website or application.
  • User registration you need to enter the user ID and registration password, the user ID as the unique identifier of the user in the website or application, can distinguish different users; the registration password is used as the authentication information of the user ID, so that the server pairs through the client The logged in user authenticates.
  • the user ID and registration password are stored on the server side for authentication.
  • the user identifier and the registration password input by the user may be obtained by calling the interface of the website page or the application page, and a user registration request is generated, and then the user registration request is sent to The user of the website or application corresponds to the user registration.
  • the user registration request may include at least: a user identifier and a registration password.
  • the user identification is usually a username.
  • the additional password can be generated by the client or server when the user registers.
  • the registration information is included in the user registration request, and includes at least: a user identifier.
  • the additional password may be generated by the client, or generated by the server, and stored on the client and the server respectively.
  • the additional password is generated according to the registration information of the user, and includes: generating, according to the user identifier, a random password that matches the user identifier, as an additional password; or generating, according to the user identifier and the device identifier of the client where the registration operation is located.
  • the additional password that the user identification matches. Taking the additional password on the server side as an example, generating the additional password includes at least the following two methods.
  • the server In the first manner, according to the user identifier included in the user registration request sent by the client, the server generates a random password matching the user identifier as an additional password. For example, according to the user identifier, according to a preset algorithm, such as using the rand() function, a random password is generated as an additional password.
  • the server of the website or the application After receiving the user registration request sent by the client, the server of the website or the application generates a matching additional password for the user according to the user identifier in the user registration request, and locally stores the user identifier, the registration password, and the server locally. The correspondence of additional passwords.
  • an additional password matching the user identifier is generated according to the user identifier included in the user registration request sent by the client and the device identifier of the client. For example, according to the user identifier and the device identifier, according to a preset algorithm, for example, the device identifier is used as an additional password or the device identifier and the user identifier are XORed by a front-to-back basis. And generating an additional password that matches the user identifier, and storing, in the server, a correspondence between the user identifier, the registration password, and the additional password.
  • the device identifier may be: a device IP address, a device serial number, and the like.
  • the client After generating the additional password, the client sends the user ID, registration password, and additional password to the server for storage by using the user registration request or generating an additional password request. And the additional password is stored locally at the same time.
  • the existing website or application usually requires the user to preset the way to receive the information (such as verification code, additional password).
  • the preset manner of receiving information includes, but is not limited to, any one of the following: receiving information by mail, receiving information by mobile phone short message, receiving information by telephone, receiving information by instant communication message, and the like.
  • Step 210 The client that performs the registration operation stores the acquired password.
  • the client After the client generates the additional password, the user ID, the registration password, and the additional password are sent to the server for storage by the user registration request or the generated additional password request, and the additional password is stored locally at the same time. After the server generates an additional password, it will send the generated additional password to the client for storage in response to the user registration request.
  • Step 220 In response to the user's identity verification operation, the client obtains the user identifier and password to be verified.
  • Step 230 The client reads an additional password pre-stored by the client executing the identity verification operation.
  • the user When the user logs in through the client on the registered terminal device, the user triggers the login button after inputting the user identifier and the password to be verified at the login entry of the client, and the client reads the locally stored additional password, and according to the user to be verified.
  • the identity and password, as well as the additional password generation authentication request, are sent to the server for authentication by the server.
  • the pre-stored additional password is obtained by any one of the following methods: when the user registers, the client or the server generates; when the user passes the verification code, the user downloads from the server; the user passes the non-registered terminal device for the first time. When logging in, it is received by the logged-in client or received by the pre-registered information receiving method.
  • Step 240 Send the user identifier and password to be verified and the additional password to the server, so that the server authenticates the user.
  • the verification password and the user identifier are sent to the server, and the server performs identity verification based on the encrypted password to be verified and the user identifier; or the user identifier and password to be verified and the additional password are simultaneously sent.
  • the server performs identity verification based on the received user identifier and password to be verified, and the additional password.
  • the client may send the to-be-verified user ID and password PW 2 for authentication, and the additional password PW 1 in the following two manners.
  • the additional encrypted by the password PW. 1 to be authenticated password PW 2, to be verified is encrypted password PW after 3, transmits the encrypted password PW 3 to be authenticated and the user ID to the identification
  • the server is used for authentication.
  • the server can authenticate in two ways.
  • the server first obtains the locally stored additional password PW 1 corresponding to the identity identifier according to the user identity ID sent with the encrypted password to be verified. ', and decrypting the received ciphered password PW 3 by using the additional password PW1', obtaining the decrypted password PW 2 'to be verified, and further obtaining the password PW 2 'to be verified after decryption
  • the registration password PW that is locally stored on the server side and matches the user identifier is compared. If the comparison is successful, the authentication is passed, otherwise the authentication fails.
  • the user identifier stored by the server may have more than one additional password.
  • the encrypted password to be verified is decrypted
  • the encrypted password is decrypted by each additional password to obtain the same password as the additional password.
  • the number of decoded passwords to be verified, and the decoded passwords to be verified are compared with the registration passwords locally stored by the server and matched with the user identifiers, and the authentication is performed as long as one of the comparisons is successful. by.
  • the server receives the to-be-verified user ID and password PW 2 and the additional password PW 1 that are simultaneously sent, the server first obtains the locally stored registration password PW corresponding to the identity ID according to the user identity ID. And the additional password PW 1 ', and the received additional password PW 1 is compared with the local storage additional password PW 1 ', and the received password to be verified PW 2 and the local storage registration password PW are performed. The comparison is successful, and only when the two match are successful, the authentication is determined to be successful. Otherwise, authentication fails because an array of passwords fails.
  • the received additional password needs to be compared with the multiple additional passwords stored by the server and matched with the user identifier. As long as one match is successful, the additional password is considered to be successful.
  • the identity verification method disclosed in the embodiment of the present application obtains the user ID and password to be verified input by the user when the user performs the identity authentication operation, and reads the additional password stored locally by the client. Then, the user ID and password to be verified and the additional password are sent to the server for identity verification, thereby authenticating the user by combining the additional password, and storing the additional password on the client, effectively improving
  • the security of user authentication can effectively prevent the theft of user account information caused by password theft.
  • the thief can not obtain the additional password when the other client authenticates. Therefore, even if the user name and password are stolen, the authentication cannot be completed, and the user account cannot be successfully logged in to obtain the user's account. information.
  • a user may register with the same username and password on multiple platforms or applications, but if the username and password on one of the platforms is compromised, the pirate can log in with the stolen username and password.
  • Other apps that cause insecure issues with accounts for other apps.
  • the identity verification method disclosed in the embodiment of the present application since the thief cannot obtain the additional password stored on the application client, the identity verification cannot be successfully performed. Even if the thief steals the additional password stored by one of the application clients, since the additional password is randomly generated and stored on the application server by the application server, the server of the different application to be logged in cannot verify the additional password of the other application, so The thief cannot successfully authenticate. Further enhance the security of authentication.
  • An identity verification method disclosed in another embodiment of the present application includes: Step 300 to Step 340.
  • Step 300 In response to the user acquiring an additional password, sending an additional password request to the server to obtain the additional password of the user.
  • the user when the user switches to the unregistered client to log in or the password stored in the registered client is damaged or lost, the user can obtain an additional password entry through the client interface, such as obtaining an additional password button, and obtaining an additional call to the server. password.
  • the user inputs at least the user identifier on the client to be logged in, and triggers the button for acquiring the additional password.
  • the client detects the user obtaining the additional password, it generates an additional password request and sends it to the server.
  • the generating additional password request includes at least a user identifier.
  • the server After receiving the request for generating the additional password sent by the client to be logged in, the server determines that the user identifier is currently in the unlogged state, and then the server obtains the registration information corresponding to the user identifier, where the registration information includes the preset receiving.
  • the way information is.
  • the manner of receiving the information includes, but is not limited to, any one of the following: receiving information by mail, receiving information by mobile phone short message, receiving information by telephone, receiving information by instant communication message, and the like.
  • the information is received by mail in the manner of receiving information, and the registration information includes an email address of the received information.
  • the registration information corresponding to the user identifier further includes: a registration password and an additional password.
  • the server sends the additional password corresponding to the user identifier to the user to which the user identifier belongs by using the preset email address through the preset email address.
  • the server may regenerate the additional password according to the user identifier, and then send the password to the user corresponding to the user identifier in a preset manner.
  • the user When the user switches the client to log in, in another embodiment, the user first logs in through the client storing the additional password. After successfully logging in, the user obtains the additional password through the accessing the additional password entry set by the client interface. operating. After the client detects the user obtaining the additional password, it generates an additional password request and sends it to the server to obtain the additional password.
  • the generating the additional password request includes at least: a user identifier.
  • the user may perform another login password verification when the user performs the operation of acquiring the additional password through the acquisition of the additional password entry set by the client interface.
  • the server After the server receives the request for generating an additional password sent by the client to be logged in, it is determined that the user identifier is currently in the logged-in state, and then the server obtains the registration information corresponding to the user identifier, where the registration information includes an additional password. And sending the additional password to the client that sent the request to generate an additional password. After receiving the additional password sent by the server, the client sending the additional password request displays the additional password on the client interface, so that the client to be logged in can input.
  • Step 310 Acquire an additional password input by the user at the client performing the authentication operation.
  • the additional password is obtained by the logged-in client, or obtained by the pre-registered information receiving manner corresponding to the user identifier.
  • the user obtains an additional password by means of pre-registered receiving information, such as receiving an email, receiving a call, or receiving a short message, or receiving an additional password through a client that has already logged in.
  • pre-registered receiving information such as receiving an email, receiving a call, or receiving a short message, or receiving an additional password through a client that has already logged in.
  • the user receives the email through the pre-registered mailbox receiving the information, and obtains the additional password as an example, and the additional password carried in the email can be input to the client to be logged in.
  • the additional password may be a character string or a two-dimensional code.
  • the client scan code that performs the identity verification operation inputs the additional password.
  • the client to be logged in obtains the additional password obtained by scanning by calling the system interface, or calls the system interface to obtain the additional password entered in the additional password edit box.
  • Step 320 Acquire a user identifier and a password to be verified in response to the user's identity verification operation.
  • Step 330 Send the user identifier and password to be verified and the additional password to the server for identity verification.
  • the user identity and the password to be verified and the additional password are sent to the server.
  • Step 340 storing the additional password.
  • the client After the user switches the client to log in successfully, or the user re-acquires the additional password and successfully logs in, the client stores the additional password locally for direct reading after subsequent login.
  • the identity verification method disclosed in the embodiment of the present application obtains an additional password by using a client that has already logged in or a pre-registered information receiving manner, and then performs identity verification according to the additional password and the user identifier and password to be verified, thereby improving identity verification. Security.
  • the verification method disclosed in the embodiment of the present application acquires an additional password through a trusted identity, so that the user can log in normally when the password is lost or the machine is easy to be used.
  • For criminals who have stolen the username and password because they do not have a trusted identity, that is, they cannot receive additional passwords, they cannot obtain additional passwords, and cannot pass authentication, which effectively improves the security of user authentication. It can effectively prevent theft of user account information caused by password theft.
  • the additional password can be transmitted in the form of a two-dimensional code, and a function module for displaying and identifying the two-dimensional code can be set on the client, so that the user can input the additional password quickly and accurately, thereby further improving the authentication efficiency.
  • an identity verification method disclosed in another embodiment of the present application is as shown in FIG. 4, and the method includes: Step 400 to Step 450.
  • Step 400 in response to the user acquiring an additional password, sending an additional password request to the server to obtain the additional password of the user.
  • the user when the user switches to the unregistered client to log in or the password stored in the registered client is damaged or lost, the user can obtain an additional password entry through the client interface, such as obtaining an additional password button, and obtaining an additional call to the server. password.
  • the user needs to input at least the user identifier on the client to be logged in, and then trigger the button for obtaining the additional password.
  • the client user obtains an additional password, generates an additional password request, and sends it to the server.
  • the generating additional password request includes at least a user identifier.
  • the server After receiving the request for generating the additional password sent by the client to be logged in, the server determines that the user identifier is currently in the unlogged state, and then the server obtains the registration information corresponding to the user identifier, where the registration information includes the preset receiving.
  • the way information is.
  • the manner of receiving the information includes, but is not limited to, any one of the following: receiving information by mail, receiving information by mobile phone short message, receiving information by telephone, receiving information by instant communication message, and the like.
  • the information is received by mail in the manner of receiving information, and the registration information includes an email address of the received information.
  • the server sends a verification code in the form of an email through a preset email address, and performs authentic identity verification on the logged-in user.
  • Step 410 Acquire a verification code input by a client that performs an identity verification operation, and perform verification code verification.
  • the user obtains the verification code by means of pre-registered receiving information, such as receiving the verification code sent by the server by receiving the mail, receiving the call, or receiving the short message.
  • the user receives the email through the mailbox that receives the pre-registered information, and takes the verification code as an example. The user forwards the verification code carried in the email to the client to be logged in.
  • the user sends a verification code to the server to complete the verification code verification by triggering the verification code set button set by the client.
  • Step 420 receiving an additional password.
  • the server After the server verifies the verification code of the client successfully, the server sends the additional password corresponding to the user identifier to the client that sends the acquisition. After sending the verification code, the client receives the additional password sent by the server in real time.
  • Step 430 Acquire a user identifier and password to be verified according to the user's identity verification operation.
  • Step 440 Send the user identifier and password to be verified and the additional password to the server for identity verification.
  • the user ID and password to be verified and the additional password are sent to the server for specific real-time mode for identity verification.
  • the embodiment shown in FIG. 2 is not described here.
  • Step 450 storing the additional password.
  • the client After the user switches the client to log in successfully, or the user re-acquires the additional password and successfully logs in, the client stores the additional password locally for direct reading after subsequent login.
  • the identity verification method disclosed in the embodiment of the present application first performs verification code verification, and after the verification code is verified, downloads an additional password from the server, and then combines the additional password and the user identifier and password to be verified to perform identity verification.
  • the problem of low security exists in the prior art authentication method.
  • the verification method disclosed in the embodiment of the present application determines the true identity of the user by first performing verification code verification, and then generates an additional password for the client to be logged in, and the identity verification has been completed, so that in the case of a lost password or an easy machine login, Users can log in normally through the client.
  • the client silently obtains the additional password from the server and saves it locally on the client, so that the next time the client is logged in, and the user is prevented from manually inputting the additional password, thereby further improving the authentication efficiency and accuracy.
  • An identity verification method disclosed in another embodiment of the present application includes: Step 500 to Step 510.
  • Step 500 Acquire an additional password that matches the user identifier carried in the user registration request according to the received user registration request, and simultaneously store the additional password at the server and the client.
  • the server receives the request sent by the client in real time, including but not limited to: a user registration request.
  • the client sends a user registration request to the server when the registration button is triggered after the user inputs the user identification and the registration password.
  • the user registration request at least includes: a user identifier and a registration password. If the additional password is generated by the client, the user registration request further includes: an additional password. If the additional password is generated by the server, the user registration request may further include: a device identifier of the terminal device where the client is located. The device identifier may be: a device IP address, a device serial number, and the like.
  • the server obtains the additional password according to the received user registration request, including: generating a random password matching the user identifier as the additional password according to the received user identifier included in the user registration request; or Generating an additional password that matches the user identifier according to the received user identifier and the device identifier of the client, or acquiring the additional password carried in the user registration request.
  • the additional password is stored locally at the server.
  • the server stores the matching relationship between the user identifier, the registration password, and the additional password.
  • the server sends the additional password to the client in response to the user registration request, so that the client stores the additional password.
  • Step 510 Perform identity verification according to the received identity verification request.
  • the identity verification request includes a user identifier and password to be verified, and an additional password.
  • Authenticating the current user of the client according to the authentication request sent by the client including: obtaining, by using the user identifier in the authentication request, an additional password and a registration password that are stored by the server and matched with the user identifier. Decrypting the encrypted password to be verified in the authentication request, and matching the decrypted password to be verified with the registration password to perform identity verification; or, by using the identity verification request.
  • the user identifier in the server obtains an additional password and a registration password that are stored by the server and matched with the user identifier, and are used to match the additional password and the password to be verified included in the authentication request to perform identity verification.
  • the client may send the password to be verified and the additional password for performing authentication in two forms.
  • the server authenticates in two ways. For a specific implementation manner of authenticating the current user of the client according to the authentication request sent by the client, refer to the detailed description of the authentication in the second embodiment, and details are not described herein again.
  • the identity verification method disclosed in the embodiment of the present application obtains an additional password according to the user registration request sent by the client, and then stores the additional password at the server local and the client simultaneously, when the client When the terminal sends the authentication request, the current user of the client is authenticated based on the to-be-verified user ID and password included in the authentication request sent by the client, and the existing user is authenticated, and the identity in the prior art is solved.
  • the verification method has a lower security issue.
  • the verification method disclosed in the embodiment of the present application authenticates the user by combining the additional password, and stores the additional password on the client, thereby effectively improving the security of the user identity verification, and effectively avoiding the user account information caused by the password being stolen. Stolen.
  • the identity verification method disclosed in another embodiment of the present application includes: Step 600 to Step 640.
  • Step 600 Receive an additional password request, the generate additional password request including at least a user identifier.
  • the server receives the request sent by the client in real time, including but not limited to: generating an additional password request.
  • the client deletes the data due to the terminal device, the additional password is lost, or the user cannot obtain the additional password stored locally by the client due to the switchover of the terminal device.
  • the user can re-acquire the additional password by obtaining the additional password entry at the client to be logged in. .
  • the client sends a request for obtaining an additional password to the server.
  • the obtaining an additional password request includes at least: a user identifier. If the additional password is generated by the client, the user registration request further includes: an additional password. If the additional password is generated by the server, the user registration request may further include: a device identifier of the client.
  • the device identifier may be: a device IP address, a device serial number, and the like.
  • the server receives the request sent by the client in real time. After receiving the request for obtaining the additional password sent by the client, the server first determines whether the user identifier carried in the request for obtaining the additional password has been logged in, and takes a corresponding response according to the login status of the user identifier.
  • Step 610 Determine whether the user identifier has been logged in. If the user identifier is not logged in, go to step 620. Otherwise, go to step 630.
  • the server determines the login status of the user identity according to the stored user information. The server determines whether the user identifier has been logged in, and if the user identifier is not logged in, sending an additional password matching the user identifier by using the received information pre-registered by the user identifier; if the user identifier is already logged in, Sending an additional password that matches the user ID to the client that sent the request to generate an additional password.
  • Step 620 Send an additional password matching the user identifier by means of the user identifier pre-registered receiving information.
  • the server determines that the user identifier is not logged in, sending an additional password that matches the user identifier by using the pre-registered receiving information of the user identifier, or first performing verification code verification on the user identifier, and After the verification code is verified, an additional password is sent to the client that sends the request for the additional password.
  • the user registers the manner for receiving information when registering, including but not limited to any of the following: receiving information by mail, receiving information by mobile phone short message, receiving information by telephone, receiving information by instant communication message, and the like.
  • the server determines, according to the user identifier, the manner in which the user identifier is registered for accepting information, such as receiving information by using a mail, and then passing the stored additional password corresponding to the user identifier or the regenerated password corresponding to the identifier through the West Sydney.
  • the receiving mode is transmitted, so that the user can receive the additional password by means of the received information.
  • Step 630 Send an additional password matching the user identifier to the client that sends the request for generating an additional password.
  • the server determines that the user identifier has been logged in, it confirms that the user is in a scenario for obtaining an additional password for logging in at the other client through the client that has logged in, and therefore, the server adds an additional password matching the user identifier to The client that generates the additional password request, that is, the client that has logged in, is sent, so that the user can complete the input of the additional password on the client to be logged in through the additional password displayed by the client that has already logged in.
  • Step 640 Perform identity verification according to the received identity verification request.
  • the identity verification request includes a user identifier and password to be verified, and an additional password.
  • the additional password may be a character string or a two-dimensional code.
  • the client scan code that performs the identity verification operation inputs the additional password.
  • the verification code verification is initiated; if the verification code verification is passed, the additional password matching the user identifier carried in the generating the additional password request is obtained. And sending the additional password to a client that generates an additional password request for storing the additional password at the client.
  • the client When the user switches to another terminal device for account login, the client will not be able to obtain the additional password stored locally. Therefore, the client prompts the user to initiate an operation for acquiring the additional password, and sends an additional password request according to the operation.
  • the verification code is received by receiving the information in advance, and verification code verification is performed to verify the true identity of the user. Then, after the verification code verification is passed, the additional password is further obtained.
  • the generating an additional password request includes at least: a user identifier.
  • the server After receiving the request for generating the additional password, the server obtains the manner of receiving the information set by the user in advance according to the user identifier carried in the generating the additional password request, and sends the verification code by using the received information manner,
  • the user performs identity verification, that is, performs verification code verification, such as sending a verification code to the user by using a short message or a telephone or a mailbox, and asking the user to input the verification code at the client to complete the verification code verification.
  • the server acquires an additional password that matches the user identifier carried in the generated additional password request, and stores the additional password locally at the server, and simultaneously sends the additional password to the client that sends the request for generating the additional password. End, the client is convenient to store the additional password.
  • the generating the additional password request further includes: an additional password.
  • the server After receiving the request for generating an additional password, the server directly stores the additional password in the correspondence between the user identifier and the additional password.
  • the user registration request may further include: a device identifier of the client. The server generates an additional password based on the device identification and the user identification.
  • the device identifier may be: a device IP address, a device serial number, and the like.
  • the verification method disclosed in this embodiment can implement normal identity verification on different terminal devices by generating an additional password request according to the client.
  • a sinister who steals a password because it cannot obtain a verification code through a pre-set information receiving method, it cannot be verified by a verification code, and an additional password cannot be obtained. Therefore, the authentication cannot be successfully performed, thereby effectively preventing the password from being stolen. The resulting user account information is stolen, and the security of the user account information is protected.
  • FIG. 11 is a hardware structural diagram of a terminal device according to some embodiments of the present disclosure.
  • the terminal device 1000 can include a processor 1010 and a machine readable storage medium 1020.
  • the processor 1010 and the machine readable storage medium 1020 can communicate via the system bus 1030. And, by reading and executing the machine executable instructions stored in the machine readable storage medium 1020 corresponding to the authentication logic, the processor 1010 can perform the method of identity verification described above.
  • the machine-readable storage medium 1020 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • the machine-readable storage medium 1020 may be a RAM (Random Access Memory), a volatile memory, a non-volatile memory, a flash memory, a storage drive (such as a hard disk drive), a solid state drive, or any type of A storage disk (such as a compact disc, a DVD, etc.), or a similar storage medium, or a combination thereof.
  • the functional verification logic in the terminal device may be:
  • the first verification information obtaining module 700 is configured to obtain a user identifier and a password to be verified in response to an identity verification operation of the user;
  • the second verification information obtaining module 710 is configured to obtain an additional password according to the user identifier.
  • the verification information sending module 720 is configured to send an identity verification request to the server, where the identity verification request includes the user identifier, the password, and the additional password to enable the server to respond to the identity verification request.
  • the authentication is performed based on the user ID, password, and additional password stored on the server.
  • the second verification information obtaining module 710 further includes:
  • the first verification information obtaining unit 7101 is configured to read, by the client, an additional password that is pre-stored in the client and that matches the user identifier.
  • the pre-stored additional password is obtained by: in response to the user registering operation on the client, the client acquiring a user identifier and a password to be registered; the client generating An additional password that matches the user identification; the client stores the additional password in association with the user identification in the client; the client identifies the user identification, the password, and the The additional password is sent to the server by a user registration request such that the server stores the additional password in association with the user identification.
  • the pre-stored additional password is obtained by: in response to the user registering operation on the client, the client acquiring a user identifier and password to be registered; the client The server sends a user registration request, where the user registration request includes the user identifier and the password; the client receives an additional password generated by the server in response to the user registration request; the client The additional password is stored in the client in association with the user identification.
  • the second verification information obtaining module 710 further includes:
  • a second verification information obtaining unit 7102 configured to: when the client does not store the additional password that matches the user identifier, the client responds to the additional password acquisition operation of the user, to the The server sends an additional password acquisition request, wherein the additional password acquisition request includes the user identifier; the client acquires an additional password input by the user at the client, wherein the additional password is the server response And sending to the user by using the information received by the logged-in client or pre-registered by the user identifier in the additional password acquisition request.
  • the client when the additional password is transmitted by the two-dimensional code, the client inputs the additional password by scanning the two-dimensional code.
  • the verification information sending module 720 further includes any one of the following:
  • a first identity verification unit 7201 configured to: the client encrypts and fuses the password by using the additional password to obtain a fusion password; and the client loads the fusion password and the user identifier into the identity Verifying the request; the client sends the authentication request to the server.
  • a second identity verification unit 7202 configured by the client to simultaneously load the user identifier, the password, and the additional password into the identity verification request; the client sends the identity verification request to the server.
  • the client on the terminal device obtains the user identifier and password to be verified in response to the identity verification operation of the user; the client obtains an additional password according to the user identifier; the client Sending an authentication request to the server, wherein the authentication request includes the user identifier, the password, and the additional password to enable the server to be stored on the server in response to the identity verification request User ID, password, and additional password for authentication.
  • the user is authenticated by combining the additional password, which effectively improves the security of the user identity verification, and can effectively prevent the user account information from being stolen due to the theft of the password.
  • the thief can not obtain the additional password when the other client authenticates. Therefore, even if the user name and password are stolen, the authentication cannot be completed, and the user account cannot be successfully logged in to obtain the user's account. information.
  • the user ID and password to be verified and the additional password are then sent to the server for identity verification.
  • the thief uses other clients.
  • the additional password cannot be obtained, even if the user name and password are stolen, the authentication cannot be completed, the user account cannot be successfully logged in, and the user's account information is obtained, thereby further improving the authentication security.
  • the user can be guaranteed to log in normally on different clients.
  • the client to be logged in can input an additional password by scanning the code, so that the user can input the additional password quickly, conveniently and accurately, thereby improving the verification efficiency.
  • FIG. 12 is a hardware structural diagram of a server according to some embodiments of the present disclosure.
  • the terminal device 1100 can include a processor 1110 and a machine readable storage medium 1120.
  • the processor 1110 and the machine readable storage medium 1120 can communicate via the system bus 1130. And, by reading and executing machine executable instructions corresponding to the authentication logic stored in the machine readable storage medium 1120, the processor 1110 can perform the method of identity verification described above.
  • the machine-readable storage medium 1120 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • the machine-readable storage medium 1120 may be a RAM (Random Access Memory), a volatile memory, a non-volatile memory, a flash memory, a storage drive (such as a hard disk drive), a solid state drive, or any type of A storage disk (such as a compact disc, a DVD, etc.), or a similar storage medium, or a combination thereof.
  • the authentication logic in the server may include:
  • the first additional password obtaining module 900 is configured to acquire, according to the received user registration request, an additional password that matches the user identifier carried in the user registration request, and store the additional password in association with the user identifier;
  • the verification module 910 is configured to perform identity verification according to the received identity verification request, where the identity verification request includes a user identifier to be verified, a password, and an additional password stored on the client and associated with the user identifier;
  • the logic further includes: a second additional password obtaining module 920, the second additional password obtaining module 920 further comprising: a request receiving unit 9201, a determining unit 9202, and a first additional password.
  • the request receiving unit 9201 is configured to receive an additional password acquisition request, where the additional password acquisition request includes at least a user identifier;
  • the determining unit 9202 is configured to determine whether the user identifier is already logged in;
  • the first additional password obtaining unit 9203 is configured to send, by using the received information pre-registered by the user identifier, an additional password that matches the user identifier, if the user identifier is not logged in;
  • the second additional password obtaining unit 9204 is configured to acquire an additional password that matches the user identifier carried in the additional password acquisition request, if the verification code verification is passed;
  • the third additional password obtaining unit 9205 is configured to: if the user identifier has been logged in, the server sends an additional password that matches the user identifier to a client that sends the additional password acquisition request.
  • the verification module 910 includes any of the following:
  • the first verification unit 9101 is configured to obtain, by using the user identifier in the identity verification request, an additional password and a registration password that are stored by the server and match the user identifier, and are used to encrypt and merge the identity verification request. Declaring the verification password for decryption, and matching the decrypted password to be verified with the registration password to perform identity verification;
  • the second verification unit 9102 is configured to obtain, by using the user identifier in the identity verification request, an additional password and a registration password stored by the server that match the user identifier, and the additional password and the password included in the identity verification request.
  • the passwords to be verified are matched separately to perform authentication.
  • the server acquires an additional password that matches the user identifier carried in the user registration request according to the received user registration request; the server associates the additional password with the user identifier. Storing; the server performs authentication according to the received authentication request, wherein the authentication request includes a user identifier to be verified, a password, and an additional password stored on the client associated with the user identifier.
  • the server disclosed in the embodiment of the present application authenticates the user by combining the additional password, and stores the additional password on the client, thereby effectively improving the security of the user identity verification, and effectively preventing the user account information caused by the password being stolen. Pirates.
  • the user can implement normal identity verification on different devices.
  • a sinister who steals a password because it cannot obtain a verification code through a pre-set information receiving method, it cannot be verified by a verification code, and an additional password cannot be obtained. Therefore, the authentication cannot be successfully performed, thereby effectively preventing the password from being stolen. The resulting user account information is stolen, and the security of the user account information is protected.
  • Embodiments of the subject matter and functional operations described in this specification can be implemented in the following: digital electronic circuits, tangible embodied computer software or firmware, computer hardware including the structures disclosed in the specification and their structural equivalents, or One or more combinations.
  • Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one of computer program instructions encoded on a tangible, non-transitory program carrier to be executed by a data processing device or to control operation of a data processing device or Multiple modules.
  • the program instructions may be encoded on an artificially generated propagating signal, such as a machine-generated electrical, optical or electromagnetic signal that is generated to encode and transmit the information to a suitable receiver device for data
  • the processing device executes.
  • the computer storage medium can be a machine readable storage device, a machine readable storage substrate, a random or serial access memory device, or a combination of one or more of them.
  • the processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform the corresponding functions by operating in accordance with input data and generating an output.
  • the processing and logic flow may also be performed by dedicated logic circuitry, such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the apparatus may also be implemented as dedicated logic circuitry.
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • Computers suitable for the execution of a computer program include, for example, a general purpose and/or special purpose microprocessor, or any other type of central processing unit.
  • the central processing unit will receive instructions and data from a read only memory and/or a random access memory.
  • the basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data.
  • the computer will also include one or more mass storage devices for storing data, such as a magnetic disk, magneto-optical disk or optical disk, or the like, or the computer will be operatively coupled to the mass storage device for receiving data or It transmits data, or both.
  • the computer does not have to have such a device.
  • the computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or, for example, a universal serial bus (USB) ) Portable storage devices for flash drives, to name a few.
  • PDA personal digital assistant
  • GPS global positioning system
  • USB universal serial bus
  • Computer readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media and memory devices including, for example, semiconductor memory devices (eg, EPROM, EEPROM, and flash memory devices), magnetic disks (eg, internal hard drives or Mobile disk), magneto-optical disks, and CD ROM and DVD-ROM disks.
  • semiconductor memory devices eg, EPROM, EEPROM, and flash memory devices
  • magnetic disks eg, internal hard drives or Mobile disk
  • magneto-optical disks e.g, CD ROM and DVD-ROM disks.
  • the processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Power Engineering (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Storage Device Security (AREA)

Abstract

一种身份验证方法和终端设备。在一示例中，终端设备上的客户端响应于用户的身份验证操作，获取待验证的用户标识和密码（100）；所述客户端根据所述用户标识，获取附加密码（110、220）；所述客户端向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码（120、240），以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。

Description

身份验证
相关申请的交叉引用
本专利申请要求于2017年8月24日提交的、申请号为201710737863.0、发明名称为“一种身份验证方法及装置，电子设备”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
技术领域
本申请涉及身份验证。
背景技术
为了保障用户信息安全，当用户在网站或者应用程序上注册时，该网站或应用程序会要求用户设置用户名和密码，并且同时要求用户设置与该用户名和密码相关联的手机号或者邮箱，便于进行身份验证或密码找回。
发明内容
本申请实施例提供一种身份验证方法，已提高身份验证方法安全性。
第一方面，本申请实施例提供了一种身份验证方法，包括：
终端设备上的客户端响应于用户的身份验证操作，获取待验证的用户标识和密码；
所述客户端根据所述用户标识，获取附加密码；
所述客户端向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。
第二方面，本申请实施例提供了一种身份验证方法，包括：
服务器根据接收到的用户注册请求，获取与所述用户注册请求中携带的用户标识匹配的 附加密码；
所述服务器将所述附加密码与所述用户标识相关联地存储；
所述服务器根据接收到的身份验证请求进行身份验证，其中，所述身份验证请求包括待验证的用户标识、密码及客户端上存储的与所述用户标识关联的附加密码。
第三方面，本申请实施例还提供了一种终端设备，包括：
处理器和机器可读存储介质，
所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，所述处理器被所述机器可执行指令促使：
响应于用户的身份验证操作，获取待验证的用户标识和密码；
根据所述用户标识，获取附加密码；
向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。
本申请实施例公开的身份验证方法，终端设备上的客户端响应于用户的身份验证操作，获取待验证的用户标识和密码；所述客户端根据所述用户标识，获取附加密码；所述客户端向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。本申请实施例公开的验证方法，通过结合附加密码对用户进行身份验证，有效提高了用户身份验证的安全性，可以有效避免注册密码被盗导致的用户账户信息泄露。当用户的密码被盗后，盗用者通过其他客户端进行身份验证时，由于无法获取附加密码，因此即使盗取了用户名和密码，也无法完成身份验证，无法成功登录用户账户，获取用户的账户信息。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其 他的附图。
图1是本申请实施例提供的身份验证方法的流程图；
图2是本申请实施例提供的身份验证方法的流程图；
图3是本申请实施例提供的身份验证方法的流程图；
图4是本申请实施例提供的身份验证方法的流程图；
图5是本申请实施例提供的身份验证方法的流程图；
图6是本申请实施例提供的身份验证方法的流程图；
图7是本申请实施例提供的身份验证逻辑的结构示意图；
图8是本申请实施例提供的身份验证逻辑的结构示意图；
图9是本申请实施例提供的身份验证逻辑的结构示意图；
图10是本申请实施例提供的身份验证逻辑的结构示意图；
图11是本申请实施例提供的终端设备的硬件结构示意图；
图12是本申请实施例提供的服务器的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
当用户登录注册获得网站或应用程序时，输入注册的用户名和密码，如果用户输入的应户名和密码与服务器端保存的用户名和密码匹配，则身份验证成功，完成用户登录，用户可以获得该用户名对应的用户相关信息和权限。
由于密码长度有限，容易被破解，导致上述身份验证方式的安全性较低。另外，账号信息也可能被泄露。例如，用户通常会在不同终端设备上某一登录网站或应用程序，当某个终端设备中的恶意软件盗取了用户的登录密码，然后在其他终端设备登录该用户的账户，可使得用户账户的信息安全将受到威胁。
本申请示例公开的一种身份验证方法。如图1所示，该方法包括：步骤100至步骤120。
步骤100，根据用户的身份验证操作，获取待验证的用户标识和密码。
当用户登录某个网站或者应用程序并需要获取用户相关的信息时，通常需要通过网站页面或应用程序页面上设置的用户登录入口输入用户标识和待验证密码进行身份验证，在身份验证通过后，才允许访问用户账户中的个人信息。具体实施时，当用户输入用户标识和密码之后触发身份验证按钮时，可以通过调用网站页面或应用程序页面的接口获取用户输入的用户标识和待验证密码，以发送至服务器进行身份验证。具体实施时，所述用户标识可以为用户名。
步骤110，获取附加密码。
如果用户在已经登录过的终端设备或者注册终端设备上通过客户端进行登录，通常该客户端会存储附加密码，可以直接读取该客户端本地存储的附加密码，即读取执行所述身份验证操作的客户端预先存储的附加密码。
如果用户更换终端设备或者终端设备上存储的附加密码由于管理不善而丢失了，如进行数据清理时删除了，客户端可以通过设置在界面上的生成附加密码的入口向服务器发起生成附加密码的请求，以获取附加密码。然后，获取用户在进行身份验证操作的客户端输入的附加密码。
例如，用户可以先在已经登录过的终端设备或者注册终端设备上登录，然后通过客户端上预设的获取附加密码的入口向服务器发起生成附加密码的请求，由服务器将与登录用户匹配的附加密码发送至发起请求的已登录客户端进行展示。然后，由用户手动将所述附加密码输入至待登录的客户端。
或者，用户通过待登录客户端，即没有存储附加密码的客户端，在至少输入用户标识的情况下，通过预先设置的生成附加密码的入口，如生成附加密码按钮，向服务器发起生成附加密码的请求，以获取附加密码。由服务器通过与所述输入的用户标识匹配的注册信息接收方式发送与所述输入的用户标识匹配的附加密码。然后，由用户手动将接收到的信息中的附加密码输入至所述待登录客户端。
具体实施时，所述附加密码可以由客户端生成，也可以由进行身份验证的服务器端生成。所述附加密码在客户端和进行身份验证的服务器端同时存储。
步骤120，将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证。
在一示例中，当获取到待验证用户标识、待验证密码和附加密码，进一步将所述待验证的用户标识、待验证密码及所述附加密码发送至服务器，以使服务器对该用户进行身份验证。具体实施时，可以将所述待验证用户标识、待验证密码和所述附加密码发送至进行身份验证的服务器，由所述服务器基于所述用户标识和预先存储的用户信息对所述待验证密码和所述附加密码分别进行验证，并且，当所述待验证密码和所述附加密码全部验证通过时，才确认用户身份验证成功。
在另一示例中，通过所述附加密码对所述待验证密码进行加密，然后把加密后的所述待验证密码和所述待验证用户标识发送至进行身份验证的服务器，由所述服务器首先获取预先存储的所述用户标识匹配的附加密码，基于预先存储的与所述用户标识匹配的附加密码对所述加密后的待验证密码进行解密，并对解密后得到的待验证密码进行验证，当解密后得到的待验证密码验证通过时，才确认用户身份验证成功。如果加密时使用的附加密码与服务器获取的预先存储的与所述用户标识匹配的附加密码不一致，即使用户输入的是待验证密码是注册密码，解密后得到的待验证密码不是用户输入的待验证密码，也会验证失败。
本申请实施例公开的身份验证方法，通过根据用户的身份验证操作，获取待验证的用户标识和密码，并获取对应的附加密码，然后，将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证。在上述方法中，通过结合附加密码对用户进行身份验证，有效提高了用户身份验证的安全性，能够有效避免密码被盗导致的用户账户信息被盗。当用户的密码被盗后，盗用者可通过其他客户端进行身份验证，但由于无法获取附加密码，即使盗取了用户名和密码，也无法完成身份验证，无法成功登录用户账户，获取用户的账户信息。
本申请另一实施例公开的一种身份验证方法，如图2所示，该方法包括：步骤200至步骤240。
步骤200，响应于用户的注册操作，客户端发送用户注册请求，以获取所述用户的附加密码。
网站或应用程序的页面可设置有用户注册入口，用于进行用户注册，以便于用户可以通过网站或应用程序管理个人信息，并能使用网站或应用程序提供的更丰富的功能。用户注册，需要输入用户标识和注册密码，用户标识作为该用户在网站或应用内的唯一标识，可以区分不同用户；注册密码则作为该用户标识的身份验证信息，以使服务器对通过客户端进行登陆的用户进行身份验证。通常，用户标识和注册密码存储在用于身份验证的服务器端。当用户输入用户标识和注册密码并触发用户注册按钮，可以通过调用网站页面或应用程序页面的接口获取用户输入的用户标识和注册密码，并生成用户注册请求，然后将所述用户注册请求发 送至网站或应用程序对应的服务器进行用户注册。其中，所述用户注册请求中可至少包括：用户标识、注册密码。所述用户标识通常为用户名。
所述附加密码可在用户注册时由客户端或服务器生成。所述注册信息包含在用户注册请求中，至少包括：用户标识。具体实施时，所述附加密码可以由客户端生成，也可以由服务器端生成，并分别在客户端和服务器端存储。所述附加密码根据用户的注册信息生成，包括：根据用户标识，生成与所述用户标识匹配的随机密码，作为附加密码；或者，根据所述用户标识和注册操作所在客户端的设备标识，生成与所述用户标识匹配的附加密码。以附加密码在服务器端生成为例，生成所述附加密码至少包括以下两种方法。
第一种方式，根据客户端发送的用户注册请求中包含的用户标识，由服务器生成与所述用户标识匹配的随机密码，作为附加密码。例如，根据所述用户标识按照预设算法，如使用rand()函数，生成一个随机密码，作为附加密码。当网站或应用程序的服务器接收到客户端发送的用户注册请求之后，根据所述用户注册请求中的用户标识，为用户生成匹配的附加密码，并在服务器本地存储所述用户标识、注册密码和附加密码的对应关系。
第二种方式，根据客户端发送的所述用户注册请求中包含的用户标识和所述客户端的设备标识，生成与所述用户标识匹配的附加密码。例如，根据所述用户标识和所述设备标识，按照预设算法，例如，将所述设备标识作为附加密码或将所述设备标识与所述用户标识按照由前向后按位异或的方法，生成与所述用户标识匹配的附加密码，并在服务器本地存储所述用户标识、注册密码和附加密码的对应关系。其中，所述设备标识可以为：设备IP地址、设备序列号等。
客户端生成附加密码的具体方法参见在服务器端生成附加密码的具体方法，此处不再赘述。客户端在生成附加密码后，将用户标识、注册密码、附加密码通过用户注册请求或生成附加密码请求发送至服务器端进行存储。并同时在本地存储所述附加密码。
为了便于用户在密码丢失或者执行安全级别较高的操作时，对用户进行真实性验证，现有网站或应用程序通常还要求用户预先设置接收信息(如验证码、附加密码)的方式验证码的方式，以对用户进行身份真实性验证。所述预先设置的接收信息的方式包括但不限于以下任意一项：通过邮件接收信息、通过手机短信接收信息、通过电话接收信息、通过即时通信消息接收信息等。
步骤210，执行所述注册操作的客户端存储获取的所述附加密码。
客户端生成附加密码后，将用户标识、注册密码、附加密码通过用户注册请求或生成附 加密码请求发送至服务器端进行存储，并同时在本地存储所述附加密码。服务器端生成附加密码后，会响应用户注册请求，将生成的附加密码发送至客户端进行存储。
步骤220，响应于用户的身份验证操作，客户端获取待验证的用户标识和密码。
根据用户的身份验证操作，获取待验证的用户标识和密码的具体实施方式参见图1所示的实施例，此处不再赘述。
步骤230，客户端读取执行所述身份验证操作的客户端预先存储的附加密码。
当用户在注册终端设备上通过客户端登录时，该用户在客户端的登录入口输入用户标识和待验证密码之后触发登录按钮，客户端会读取本地存储的附加密码，并根据所述待验证用户标识和密码，以及所述附加密码生成身份验证请求发送至服务器，由服务器进行身份验证。
具体实施时，所述预先存储的附加密码通过以下任意一种方式获得：用户注册时由客户端或服务器生成；当用户通过验证码验证后，从服务器端下载；用户通过非注册终端设备上首次登录时，通过已登录客户端获取或通过预先注册的信息接收方式接收。
步骤240，将所述待验证的用户标识和密码及所述附加密码发送至服务器，以使服务器对该用户进行身份验证。
将所述待验证的用户标识和密码及所述附加密码发送至服务器，以使服务器对该用户进行身份验证，包括：通过所述附加密码对所述待验证密码进行加密，把加密后的待验证密码和所述用户标识发送至服务器，由所述服务器基于加密后的待验证密码和所述用户标识进行身份验证；或者，将所述待验证用户标识和密码，及所述附加密码同时发送至服务器，由所述服务器基于接收到的所述待验证用户标识和密码，及所述附加密码进行身份验证。
具体实施时，客户端可以通过以下两种方式发送用于进行身份验证的待验证用户标识ID和密码PW 2，以及附加密码PW 1。第一种方式，通过所述附加密码PW 1对所述待验证密码PW 2进行加密，得到加密后的待验证密码PW 3，把加密后的待验证密码PW 3和所述用户标识ID发送至服务器用于进行身份验证。第二种方式，把所述待验证用户标识ID和密码PW 2和所述附加密码PW 1一起发送到服务器，用于进行身份验证。
相应的，服务器可通过两种方式进行身份验证。
例如，如果服务器接收到加密后的待验证密码PW 3，则服务器首先根据与所述加密后的待验证密码一起发送的用户身份标识ID获取本地存储的与所述身份标识对应的附加密码PW 1’，并利用所述附加密码PW1’对接收到的所述融合后的密码PW 3进行解密，获取解密后 的待验证密码PW 2’，并进一步将解密后得到的待验证密码PW 2’与所述服务器端本地存储的与所述用户标识匹配的注册密码PW进行比对。若比对成功，则身份验证通过，否则，身份验证失败。
具体实施时，该服务器存储的用户标识对应的附加密码可能不止一个，对加密后的待验证密码进行解密时，通过每个附加密码分别对所述加密后的密码进行解密，得到与附加密码相同数量的解码后的待验证密码，并将所解码后的待验证密码与所述服务器端本地存储的与所述用户标识匹配的注册密码逐一进行比对，只要有一个比对成功，则身份验证通过。
再例如，如果服务器接收到同时发送的待验证用户标识ID和密码PW 2和附加密码PW 1，则服务器首先根据所述用户身份标识ID获取本地存储的与所述身份标识ID对应的注册密码PW和附加密码PW 1’，并将接收到的所述附加密码PW 1与本地存储附加密码PW 1’进行比对，以及，将接收到的所述待验证密码PW 2与本地存储注册密码PW进行比对，只有两者均匹配成功时，才确定身份验证成功。否则，只要有一组密码匹配失败，则认为身份验证失败。同样的，当服务器端存在与所述用户标识匹配的多个附加密码时，需要将接收到的附加密码与所述服务器端存储的与所述用户标识匹配的多个附加密码逐一进行比对，只要有一个比对成功，则认为附加密码匹配成功。
本申请实施例公开的身份验证方法，通过在客户端预先存储附加密码，当用户执行身份认证操作时，获取用户输入的待验证的用户标识和密码，并读取客户端本地存储的附加密码，然后，将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证，从而通过结合附加密码对用户进行身份验证，并且，将附加密码存储在客户端，有效提高了用户身份验证的安全性，可以有效避免密码被盗导致的用户账户信息被盗。当用户的密码被盗后，盗用者通过其他客户端进行身份验证时，由于无法获取附加密码，因此即使盗取了用户名和密码，也无法完成身份验证，无法成功登录用户账户，获取用户的账户信息。
在一示例中，用户可能会在多个平台或应用上使用相同的用户名和密码进行注册，但是，如果其中一个平台上的用户名和密码被盗用了，盗用者可以通过盗取的用户名和密码登录其他应用，导致其他应用的账户存在不安全问题。通过本申请实施例公开的身份验证方法，由于盗用者无法获取存储在应用客户端上附加密码，所以无法成功通过身份验证。即便盗用者盗取了其中一个应用客户端存储的附加密码，由于附加密码为应用服务器随机生成并保存在应用的服务器上，待登录的不同应用的服务器无法对其他应用的附加密码验证通过，因此盗用者无法成功通过身份验证。进一步提升了身份验证的安全性。
本申请另一实施例公开的一种身份验证方法，如图3所示，该方法包括：步骤300至步 骤340。
步骤300，响应于用户获取附加密码的操作，发送生成附加密码请求至服务器，以获取所述用户的附加密码。
具体实施时，当用户切换到未注册客户端进行登录或者注册客户端存储的密码损坏或丢失时，用户可以通过客户端界面设置的获取附加密码的入口，如获取附加密码按钮，向服务器获取附加密码。
具体实施时，用户在待登录客户端至少输入用户标识，并触发获取附加密码按钮。客户端检测到用户获取附加密码的操作之后，生成附加密码请求，并发送至服务器。所述生成附加密码请求中至少包括用户标识。
服务器接收到待登录客户端发送的生成附加密码请求之后，判断所述用户标识当前为未登录状态，然后，服务器获取所述用户标识对应的注册信息，其中，所述注册信息包括预设的接收信息的方式。所述接收信息的方式包括但不限于以下任意一种：通过邮件接收信息、通过手机短信接收信息、通过电话接收信息、通过即时通信消息接收信息等。以所述接收信息的方式通过邮件接收信息为例，所述注册信息中包括接收信息的邮箱地址。所述用户标识对应的注册信息还包括：注册密码和附加密码。然后，服务器将所述附加密码通过预设的邮箱地址，通过邮件的形式发送所述用户标识对应的附加密码至所述用户标识所属用户。具体实施时，服务器也可以根据所述用户标识重新生成附加密码，然后通过预设形式发送给所述用户标识对应的用户。服务器根据所述用户标识重新生成附加密码的方法参见实施例二，此处不再赘述。
当用户切换客户端进行登录时，在另一种实施方式中，用户首先通过存储有附加密码的客户端进行登录，当成功登陆后，用户通过客户端界面设置的获取附加密码入口执行获取附加密码操作。客户端检测到用户获取附加密码的操作后，产生生成附加密码请求，并发送至服务器，以获取附加密码。所述生成附加密码请求中至少包括：用户标识。具体实施时，为了进一步提升密码验证的安全性，可以在用户通过客户端界面设置的获取附加密码入口执行获取附加密码操作时，对用户再进行一次登陆密码验证。
当服务器接收到待登录客户端发送的生成附加密码请求之后，判断所述用户标识当前为已登录状态，然后，服务器获取所述用户标识对应的注册信息，其中，所述注册信息包括附加密码，并将所述附加密码发送至发送生成附加密码请求的客户端。发送生成附加密码请求的客户端接收到服务器发送的附加密码后，在客户端界面显示所述附加密码，以便于待登录 的客户端进行输入。
步骤310，获取用户在进行身份验证操作的客户端输入的附加密码。
其中，所述附加密码通过已登录客户端获取，或通过所述用户标识对应的预先注册的信息接收方式获取。
具体实施时，用户通过预先注册的接收信息的方式获取附加密码，如通过接收邮件、接听电话或接收短信，或者通过已经登录的客户端接收附加密码。本实施例中以用户通过预先注册的接收信息的邮箱接收邮件，以获取附加密码为例，可将邮件中携带的附加密码输入至待登录的客户端。
具体实施时，所述附加密码可以为字符串或二维码，当接收到记录附加密码的二维码时，进行身份验证操作的客户端扫码输入所述附加密码。
待登录客户端通过调用系统接口获取扫描得到的附加密码，或者调用系统接口获取附加密码编辑框中输入的附加密码。
步骤320，响应于用户的身份验证操作，获取待验证的用户标识和密码。
响应于用户的身份验证操作，获取待验证的用户标识和密码的具体实施方式参见实施例一，此处不再赘述。
步骤330，将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证。
将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证的具体实时方式参见实施例二，此处不再赘述。
步骤340，存储所述附加密码。
当用户切换客户端进行登录成功后，或者，用户重新获取附加密码并登录成功后，客户端在本地存储所述附加密码，以便后续登录时直接读取。
本申请实施例公开的身份验证方法，通过已经登录的客户端或者预先注册的信息接收方式获取附加密码，然后，结合所述附加密码和待验证用户标识和密码，进行身份验证，提高了身份验证的安全性。本申请实施例公开的验证方法，通过可信的身份获取附加密码，使得在密码丢失或者易机的情况，用户能够正常登录。同时，对于盗用了用户名和密码的不法分子，由于其不具备可信的身份，即其不能够接收附加密码，因此无法获得附加密码，不能通过身份验证，有效提高了用户身份验证的安全性，可以有效避免密码被盗导致的用户账户信息被盗。在验证通过后，在客户端保存附加密码，便于下一次登录此客户端。另一方面，可 通过二维码的形式传输附加密码，并在客户端设置展示和识别二维码的功能模块，便于用户快速、准确的输入附加密码，进一步提高身份验证效率。
基于图3所示的实施例，本申请另一实施例公开的一种身份验证方法，如图4所示，该方法包括：步骤400至步骤450。
步骤400，响应于用户获取附加密码的操作，发送生成附加密码请求至服务器，以获取所述用户的附加密码。
具体实施时，当用户切换到未注册客户端进行登录或者注册客户端存储的密码损坏或丢失时，用户可以通过客户端界面设置的获取附加密码的入口，如获取附加密码按钮，向服务器获取附加密码。
具体实施时，用户需要在待登录客户端至少输入用户标识，然后，触发获取附加密码按钮。客户端用户获取附加密码的操作，产生生成附加密码请求，并发送至服务器。所述生成附加密码请求中至少包括用户标识。
服务器接收到待登录客户端发送的生成附加密码请求之后，判断所述用户标识当前为未登录状态，然后，服务器获取所述用户标识对应的注册信息，其中，所述注册信息包括预设的接收信息的方式。所述接收信息的方式包括但不限于以下任意一种：通过邮件接收信息、通过手机短信接收信息、通过电话接收信息、通过即时通信消息接收信息等。以所述接收信息的方式通过邮件接收信息为例，所述注册信息中包括接收信息的邮箱地址。然后，服务器通过预设的邮箱地址，通过邮件的形式发送验证码，对待登录用户进行真实身份验证。
步骤410，获取用户在进行身份验证操作的客户端输入的验证码，并进行验证码验证。
具体实施时，用户通过预先注册的接收信息的方式获取验证码，如通过接收邮件、接听电话或接收短信等方式接收服务器发送的验证码。本实施例中以用户通过预先注册的接收信息的邮箱接收邮件，以接收验证码为例，用户将邮件中携带的验证码转输入至待登录的客户端。
然后，用户通过触发客户端设置的验证码验证按钮发送验证码至服务器完成验证码验证。
服务器端对客户端进行验证码验证的具体方案参见现有技术，此处不再赘述。
步骤420，接收附加密码。
当服务器对客户端进行验证码验证成功后，服务器将所述用户标识对应的附加密码发送至发送获取的客户端。客户端在发送验证码之后，实时接收服务器发送的附加密码。
步骤430，根据用户的身份验证操作，获取待验证的用户标识和密码。
根据用户的身份验证操作，获取待验证的用户标识和密码的具体实施方式参见实施例一，此处不再赘述。
步骤440，将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证。
将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证的具体实时方式图2所示的实施例，此处不再赘述。
步骤450，存储所述附加密码。
当用户切换客户端进行登录成功后，或者，用户重新获取附加密码并登录成功后，客户端在本地存储所述附加密码，以便后续登录时直接读取。
本申请实施例公开的身份验证方法，通过首先进行验证码验证，并在验证码验证通过后，从服务器下载附加密码，然后结合所述附加密码和待验证用户标识和密码，进行身份验证，解决了现有技术中的身份验证方法存在的安全性较低的问题。本申请实施例公开的验证方法，通过首先进行验证码验证以确定用户的真实身份，然后，为待登录客户端生成附加密码，已完成身份验证，使得在密码丢失或者易机登录的情况下，用户能够通过客户端正常登录。同时，对于盗用了用户名和密码的不法分子，由于其不具备可信的身份，即其不能够接收附加密码，因此无法获得附加密码，不能通过身份验证，有效提高了用户身份验证的安全性，可以有效避免密码被盗导致的用户账户信息被盗。同时，在验证码验证通过后，客户端静默从服务器获取附加密码并保存在客户端本地，便于下一次登录此客户端，同时，避免了用户手动输入附加密码，进一步提高身份验证效率和准确率。
本申请另一实施例公开的一种身份验证方法，如图5所示，该方法包括：步骤500至步骤510。
步骤500，根据接收到的用户注册请求，获取与所述用户注册请求中携带的用户标识匹配的附加密码，并在服务器本地和所述客户端同时存储所述附加密码。
具体实施时，服务器实时接收客户端发送的请求，包括但不限于：用户注册请求。
当用户通过客户端进行用户注册时，在用户输入用户标识和注册密码之后，触发注册按钮时，客户端会向服务器发送用户注册请求。具体实施时，所述用户注册请求至少包括：用户标识和注册密码。如果附加密码由客户端生成，所述用户注册请求还包括：附加密码。 如果附加密码由服务器生成，所述用户注册请求还可以包括：客户端所在终端设备的设备标识。其中，所述设备标识可以为：设备IP地址、设备序列号等。
然后，服务器根据接收到的所述用户注册请求，获取附加密码，包括：根据接收到的所述用户注册请求中包含的用户标识，生成与所述用户标识匹配的随机密码作为附加密码；或者，根据接收到的所述用户注册请求中包含的用户标识和所述客户端的设备标识，生成与所述用户标识匹配的附加密码；或者，获取所述用户注册请求中携带的所述附加密码。
服务器根据所述用户注册请求中包括的用户标识获取附加密码的方法参见图2所示实施例中的相关步骤的介绍，此处不再赘述。服务器根据所述用户注册请求中包括的用户标识、客户端的设备标识生成附加密码的方法参见实施例二中的相关步骤的介绍，此处不再赘述。
当服务器获取到附加密码之后，会在服务器本地存储所述附加密码。具体实施时，服务器存储用户标识、注册密码和附加密码的匹配关系。所述服务器会通过响应所述用户注册请求的方式，将所述附加密码发送给客户端，便于所述客户端存储所述附加密码。
步骤510，根据接收到的身份验证请求，进行身份验证。
其中，所述身份验证请求包括待验证用户标识和密码，及附加密码。
根据客户端发送的身份验证请求，对所述客户端的当前用户进行身份验证，包括：通过所述身份验证请求中的用户标识，获取服务器存储的与所述用户标识匹配的附加密码和注册密码，用于对所述身份验证请求中加密融合后的所述待验证密码进行解密，并将解密得到的待验证密码与所述注册密码进行匹配，以执行身份验证；或者，通过所述身份验证请求中的用户标识，获取服务器存储的与所述用户标识匹配的附加密码和注册密码，用于与所述身份验证请求中包括的附加密码和待验证密码分别进行匹配，以执行身份验证。
具体实施时，如图2所示实施例，客户端可以通过两种形式发送用于进行身份验证的待验证密码和附加密码。相应的，服务器通过两种方式进行身份验证。服务器根据客户端发送的身份验证请求，对所述客户端的当前用户进行身份验证的具体实施方式参见实施二中关于身份验证的具体描述，此处不再赘述。
本申请实施例公开的身份验证方法，通过接收客户端发送的用户注册请求，并根据所述用户注册请求，获取附加密码，然后在服务器本地和所述客户端同时存储所述附加密码，当客户端发送身份验证请求时，则基于客户端发送的身份验证请求中过包括的待验证用户标识和密码，及附加密码，对所述客户端的当前用户进行身份验证，解决了现有技术中的身份 验证方法存在的安全性较低的问题。本申请实施例公开的验证方法，通过结合附加密码对用户进行身份验证，并且，将附加密码存储在客户端，有效提高了用户身份验证的安全性，可以有效避免密码被盗导致的用户账户信息被盗。
基于图5所示的实施例，本申请另一实施例中公开的身份验证方法，如图6所示，包括：步骤600至步骤640。
步骤600，接收生成附加密码请求，所述生成附加密码请求至少包括用户标识。
服务器实时接收客户端发送的请求，所述请求包括但不限于：生成附加密码请求。
在客户端由于终端设备清理数据而导致附加密码丢失，或者，由于切换登陆终端设备而无法成功获取客户端本地存储的附加密码时，用户可以在待登陆客户端通过获取附加密码入口重新获取附加密码。例如，当用户在待登陆客户端通过获取附加密码入口输入用户表标识之后，触发获取附加密码按钮时，客户端会向服务器发送获取附加密码请求。具体实施时，所述获取附加密码请求至少包括：用户标识。如果附加密码由客户端生成，所述用户注册请求还包括：附加密码。如果附加密码由服务器生成，所述用户注册请求还可以包括：客户端的设备标识。其中，所述设备标识可以为：设备IP地址、设备序列号等。
服务器实时接收到客户端发送的请求。当服务器接收到客户端发送的获取附加密码请求之后，首先判断所述获取附加密码请求中携带的用户标识是否已经登陆，并根据用户标识的登陆情况采取相应的响应。
步骤610，判断所述用户标识是否已经登录，若所述用户标识未登录，则执行步骤620，否则，执行步骤630。
服务器根据存储的用户信息判断用户标识的登陆情况。服务器判断所述用户标识是否已经登录，若所述用户标识未登录，则通过所述用户标识预先注册的接收信息方式发送与所述用户标识匹配的附加密码；若所述用户标识已经登录，则发送与所述用户标识匹配的附加密码至发送所述生成附加密码请求的客户端。
步骤620，通过所述用户标识预先注册的接收信息的方式发送与所述用户标识匹配的附加密码。
当服务器判断所述用户标识未登录时，则通过所述用户标识预先注册的接收信息的方式发送与所述用户标识匹配的附加密码，或者，首先对所述用户标识进行验证码验证，并在验证码验证通过后，再向发送获取附加密码请求的客户端发送附加密码。
具体实施时，用户在注册时会注册用于接收信息的方式，包括但不限于以下任意一项：通过邮件接收信息、通过手机短信接收信息、通过电话接收信息、通过即时通信消息接收信息等。服务器根据用户标识确定该用户标识注册的用于接受信息的方式，如通过邮件接收信息，然后，将存储的该用户标识对应的附加密码或重新生成的与标识对应的附加密码通过所述西悉尼接收方式进行发送，使得用户通过所述接收信息的方式可以接收到附加密码。
步骤630，发送与所述用户标识匹配的附加密码至发送所述生成附加密码请求的客户端。
当服务器判断所述用户标识已经登录时，则确认该用户处于通过已经登陆的客户端获取附加密码用于在其他客户端进行登录的场景，因此，服务器将与所述用户标识匹配的附加密码至发送所述生成附加密码请求的客户端，即已经登陆的客户端，使得用户可以通过已经登陆的客户端展示的附加密码在待登陆的客户端完成输入附加密码。
步骤640，根据接收到的身份验证请求，进行身份验证。
其中，所述身份验证请求包括待验证用户标识和密码，及附加密码。
根据客户端发送的身份验证请求，对所述客户端的当前用户进行身份验证的具体实施方式参见图5所示的实施例，此处不再赘述。
具体实施时，所述附加密码可以为字符串或二维码，当所述附加密码通过二维码发送时，进行身份验证操作的客户端扫码输入所述附加密码。
可选的，在另一个实施例中，若判断所述用户标识未登录，则启动验证码验证；若验证码验证通过，则获取与所述生成附加密码请求中携带的用户标识匹配的附加密码，并发送所述附加密码至生成附加密码请求的客户端，用于在所述客户端存储所述附加密码。
当用户切换到其他终端设备进行账户登录时，客户端将无法获取本地存储的附加密码，因此，所述客户端会提示用户发起获取附加密码的操作，并根据所述操作发送生成附加密码请求，以通过预先设置的接收信息的方式接收验证码，进行验证码验证，以验证用户的真实身份。然后，在验证码验证通过后，进一步获取附加密码。具体实施时，所述生成附加密码请求至少包括：用户标识。
所述服务器收到生成附加密码请求之后，根据所述生成附加密码请求中携带的用户标识获取所述用户标识所述用户预先设置的接收信息方式，并通过所述接收信息方式发送验证码，对所述用户执行身份真实性验证，即进行验证码验证，如通过短信或电话或邮箱向用户发送验证码，并要求用户在客户端输入所述验证码，以完成验证码验证。
验证码验证的具体实施方式参见现有技术，本申请的实施例中不再赘述。
若验证码验证通过，服务器获取与所述生成附加密码请求中携带的用户标识匹配的附加密码，并在服务器本地存储所述附加密码，同时，发送所述附加密码至发送生成附加密码请求的客户端，便于所述客户端存储所述附加密码。
如果附加密码由客户端生成，所述生成附加密码请求还包括：附加密码。服务器接收到所述生成附加密码请求之后，直接将所述附加密码存储在用户标识和附加密码的对应关系中。如果附加密码由服务器生成，所述用户注册请求还可以包括：客户端的设备标识。服务器根据所述设备标识和用户标识生成附加密码。其中，所述设备标识可以为：设备IP地址、设备序列号等。
服务器根据生成附加密码请求，生成与所述用户标识匹配的附加密码的具体方法参见实施例二，此处不再赘述。
基于图5所示的实施例公开的身份验证方法，本实施例公开的验证方法通过根据客户端发送的生成附加密码请求，使得用户在不同终端设备上可以实现正常的身份验证。而对于盗用密码的不法分子，因其无法通过预先设置的信息接收方式获取验证码，因此无法通过验证码验证，也无法获取附加密码，所以，无法成功进行身份验证，进而可以有效避免密码被盗导致的用户账户信息被盗，保护了用户账户信息的安全。
以上对本申请提供的方法进行了描述。下面对本申请提供的装置进行描述：
参见图11，图11为本申请一些实施例提供的终端设备的硬件结构图。该终端设备1000可包括处理器1010以及机器可读存储介质1020。其中，处理器1010和机器可读存储介质1020可经由系统总线1030通信。并且，通过读取并执行机器可读存储介质1020中存储的与身份验证逻辑对应的机器可执行指令，处理器1010可执行上文所述的身份验证的方法。
本文提到的机器可读存储介质1020可以是任何电子、磁性、光学或其他物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，所述机器可读存储介质1020可以是RAM(Random Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)，或者类似的存储介质，或者它们的组合。
如图7所示，从功能上划分，所述该终端设备中的身份验证逻辑可包括：
第一验证信息获取模块700，用于响应于用户的身份验证操作，获取待验证的用户标识和密码；
第二验证信息获取模块710，用于根据所述用户标识，获取附加密码；
验证信息发送模块720，用于向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。
在一示例中，如图8所示，所述第二验证信息获取模块710进一步包括：
第一验证信息获取单元7101，用于所述客户端读取所述客户端中预先存储的与所述用户标识匹配的附加密码。
在一示例中，所述预先存储的附加密码通过以下方式获得：响应于所述用户在所述客户端上的注册操作，所述客户端获取待注册的用户标识和密码；所述客户端生成与所述用户标识匹配的附加密码；所述客户端将所述附加密码与所述用户标识相关联地存储于所述客户端；所述客户端将所述用户标识、所述密码以及所述附加密码通过用户注册请求发送至所述服务器，以使得所述服务器将所述附加密码与所述用户标识相关联地存储。
在一示例中，所述预先存储的附加密码通过以下方式获得：响应于所述用户在所述客户端上的注册操作，所述客户端获取待注册的用户标识和密码；所述客户端向所述服务器发送用户注册请求，其中，所述用户注册请求包括所述用户标识和所述密码；所述客户端接收所述服务器响应于所述用户注册请求而生成的附加密码；所述客户端将所述附加密码与所述用户标识相关联地存储于所述客户端。
在一示例中，如图8所示，所述第二验证信息获取模块710进一步包括：
第二验证信息获取单元7102，用于在所述客户端未存储与所述用户标识匹配的所述附加密码的情况下，所述客户端响应于所述用户的附加密码获取操作，向所述服务器发送附加密码获取请求，其中，所述附加密码获取请求包括所述用户标识；所述客户端获取所述用户在所述客户端输入的附加密码，其中，所述附加密码是所述服务器响应于所述附加密码获取请求而通过已登录客户端获取或所述用户标识预先注册的信息接收方式发送至所述用户。
在一示例中，当当所述附加密码通过二维码发送时，所述客户端通过扫描所述二维码输入所述附加密码。
在一示例中，如图8所示，所述验证信息发送模块720进一步包括以下任意一项：
第一身份验证单元7201，用于所述客户端通过所述附加密码对所述密码进行加密融合，以获得融合密码；所述客户端把所述融合密码和所述用户标识载入所述身份验证请求； 所述客户端将所述身份验证请求发送至所述服务器。
第二身份验证单元7202，用于所述客户端将所述用户标识、所述密码及所述附加密码同时载入所述身份验证请求；所述客户端将所述身份验证请求发送至所述服务器。
本申请实施例公开的终端设备，该终端设备上的客户端响应于用户的身份验证操作，获取待验证的用户标识和密码；所述客户端根据所述用户标识，获取附加密码；所述客户端向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。通过结合附加密码对用户进行身份验证，有效提高了用户身份验证的安全性，可以有效避免密码被盗导致的用户账户信息被盗。当用户的密码被盗后，盗用者通过其他客户端进行身份验证时，由于无法获取附加密码，因此即使盗取了用户名和密码，也无法完成身份验证，无法成功登录用户账户，获取用户的账户信息。
通过在客户端预先存储附加密码，然后，将所述待验证的用户标识和密码及所述附加密码发送至服务器，用于身份验证，当用户的密码被盗后，盗用者通过其他客户端进行身份验证时，由于无法获取附加密码，因此即使盗取了用户名和密码，也无法完成身份验证，无法成功登录用户账户，获取用户的账户信息，进一步提升了验证安全性。
通过由已登录客户端获取并展示附加密码，或者通过预先注册的信息接收方式获取附加密码，可以保障用户在不同客户端能够正常登陆。同时，通过用二维码形式发送附加密码，待登陆客户端可以通过扫码输入附加密码，使得用户可以快速、便捷、准确地输入附加密码，提高了验证效率。
参见图12，图12为本申请一些实施例提供的服务器的硬件结构图。该终端设备1100可包括处理器1110以及机器可读存储介质1120。其中，处理器1110和机器可读存储介质1120可经由系统总线1130通信。并且，通过读取并执行机器可读存储介质1120中存储的与身份验证逻辑对应的机器可执行指令，处理器1110可执行上文所述的身份验证的方法。
本文提到的机器可读存储介质1120可以是任何电子、磁性、光学或其他物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，所述机器可读存储介质1120可以是RAM(Random Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)，或者类似的存储介质，或者它们的组合。
如图9所示，从功能上划分，所述该服务器中的身份验证逻辑可包括：
第一附加密码获取模块900，用于根据接收到的用户注册请求，获取与所述用户注册请求中携带的用户标识匹配的附加密码；将所述附加密码与所述用户标识相关联地存储；
验证模块910，用于根据接收到的身份验证请求进行身份验证，其中，所述身份验证请求包括待验证的用户标识、密码及客户端上存储的与所述用户标识关联的附加密码；
在一示例中，如图10所示，所述逻辑还包括：第二附加密码获取模块920，所述第二附加密码获取模块920进一步包括：请求接收单元9201、判断单元9202、第一附加密码获取单元9203或第二附加密码获取单元9204、第三附加密码获取单元9205；其中，
所述请求接收单元9201，用于接收附加密码获取请求，所述附加密码获取请求至少包括用户标识；
所述判断单元9202，用于判断所述用户标识是否已经登录；
所述第一附加密码获取单元9203，用于若所述用户标识未登录，则通过所述用户标识预先注册的接收信息方式发送与所述用户标识匹配的附加密码；
所述第二附加密码获取单元9204，用于若验证码验证通过，则获取与所述附加密码获取请求中携带的用户标识匹配的附加密码；
所述第三附加密码获取单元9205，用于若所述用户标识已经登录，则所述服务器发送与所述用户标识匹配的附加密码至发送所述附加密码获取请求的客户端。
在一示例中，如图10所示，所述验证模块910包括以下任意一项：
第一验证单元9101，用于通过所述身份验证请求中的用户标识，获取服务器存储的与所述用户标识匹配的附加密码和注册密码，用于对所述身份验证请求中加密融合后的所述待验证密码进行解密，并将解密得到的待验证密码与所述注册密码进行匹配，以执行身份验证；
第二验证单元9102，用于通过所述身份验证请求中的用户标识，获取服务器存储的与所述用户标识匹配的附加密码和注册密码，用于与所述身份验证请求中包括的附加密码和待验证密码分别进行匹配，以执行身份验证。
本申请实施例公开的服务器，服务器根据接收到的用户注册请求，获取与所述用户注册请求中携带的用户标识匹配的附加密码；所述服务器将所述附加密码与所述用户标识相关联地存储；所述服务器根据接收到的身份验证请求进行身份验证，其中，所述身份验证请求包括待验证的用户标识、密码及客户端上存储的与所述用户标识关联的附加密码。本申请实 施例公开的服务器，通过结合附加密码对用户进行身份验证，并且，将附加密码存储在客户端，有效提高了用户身份验证的安全性，可以有效避免密码被盗导致的用户账户信息被盗。
进一步的，通过根据客户端发送的生成附加密码请求生成附加密码，使得用户在不同设备上可以实现正常的身份验证。而对于盗用密码的不法分子，因其无法通过预先设置的信息接收方式获取验证码，因此无法通过验证码验证，也无法获取附加密码，所以，无法成功进行身份验证，进而可以有效避免密码被盗导致的用户账户信息被盗，保护了用户账户信息的安全。
本说明书中描述的主题及功能操作的实施例可以在以下中实现：数字电子电路、有形体现的计算机软件或固件、包括本说明书中公开的结构及其结构性等同物的计算机硬件、或者它们中的一个或多个的组合。本说明书中描述的主题的实施例可以实现为一个或多个计算机程序，即编码在有形非暂时性程序载体上以被数据处理装置执行或控制数据处理装置的操作的计算机程序指令中的一个或多个模块。可替代地或附加地，程序指令可以被编码在人工生成的传播信号上，例如机器生成的电、光或电磁信号，该信号被生成以将信息编码并传输到合适的接收机装置以由数据处理装置执行。计算机存储介质可以是机器可读存储设备、机器可读存储基板、随机或串行存取存储器设备、或它们中的一个或多个的组合。
本说明书中描述的处理及逻辑流程可以由执行一个或多个计算机程序的一个或多个可编程计算机执行，以通过根据输入数据进行操作并生成输出来执行相应的功能。所述处理及逻辑流程还可以由专用逻辑电路—例如FPGA(现场可编程门阵列)或ASIC(专用集成电路)来执行，并且装置也可以实现为专用逻辑电路。
适合用于执行计算机程序的计算机包括，例如通用和/或专用微处理器，或任何其他类型的中央处理单元。通常，中央处理单元将从只读存储器和/或随机存取存储器接收指令和数据。计算机的基本组件包括用于实施或执行指令的中央处理单元以及用于存储指令和数据的一个或多个存储器设备。通常，计算机还将包括用于存储数据的一个或多个大容量存储设备，例如磁盘、磁光盘或光盘等，或者计算机将可操作地与此大容量存储设备耦接以从其接收数据或向其传送数据，抑或两种情况兼而有之。然而，计算机不是必须具有这样的设备。此外，计算机可以嵌入在另一设备中，例如移动电话、个人数字助理(PDA)、移动音频或视频播放器、游戏操纵台、全球定位系统(GPS)接收机、或例如通用串行总线(USB)闪存驱动器的便携式存储设备，仅举几例。
适合于存储计算机程序指令和数据的计算机可读介质包括所有形式的非易失性存储器、媒介和存储器设备，例如包括半导体存储器设备(例如EPROM、EEPROM和闪存设备)、 磁盘(例如内部硬盘或可移动盘)、磁光盘以及CD ROM和DVD-ROM盘。处理器和存储器可由专用逻辑电路补充或并入专用逻辑电路中。
虽然本说明书包含许多具体实施细节，但是这些不应被解释为限制任何发明的范围或所要求保护的范围，而是主要用于描述特定发明的具体实施例的特征。本说明书内在多个实施例中描述的某些特征也可以在单个实施例中被组合实施。另一方面，在单个实施例中描述的各种特征也可以在多个实施例中分开实施或以任何合适的子组合来实施。此外，虽然特征可以如上所述在某些组合中起作用并且甚至最初如此要求保护，但是来自所要求保护的组合中的一个或多个特征在一些情况下可以从该组合中去除，并且所要求保护的组合可以指向子组合或子组合的变型。
类似地，虽然在附图中以特定顺序描绘了操作，但是这不应被理解为要求这些操作以所示的特定顺序执行或顺次执行、或者要求所有例示的操作被执行，以实现期望的结果。在某些情况下，多任务和并行处理可能是有利的。此外，上述实施例中的各种系统模块和组件的分离不应被理解为在所有实施例中均需要这样的分离，并且应当理解，所描述的程序组件和系统通常可以一起集成在单个软件产品中，或者封装成多个软件产品。
由此，主题的特定实施例已被描述。其他实施例在所附权利要求书的范围以内。在某些情况下，权利要求书中记载的动作可以以不同的顺序执行并且仍实现期望的结果。此外，附图中描绘的处理并非必需所示的特定顺序或顺次顺序，以实现期望的结果。在某些实现中，多任务和并行处理可能是有利的。
需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本发明实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (15)

  1. 一种身份验证方法，包括：
    终端设备上的客户端响应于用户的身份验证操作，获取待验证的用户标识和密码；
    所述客户端根据所述用户标识，获取附加密码；
    所述客户端向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。
  2. 根据权利要求1所述的方法，其中，获取所述附加密码，包括：
    所述客户端读取所述客户端中预先存储的与所述用户标识匹配的附加密码。
  3. 根据权利要求2所述的方法，其中，所述预先存储的附加密码通过以下方式获得：
    响应于所述用户在所述客户端上的注册操作，所述客户端获取待注册的用户标识和密码；
    所述客户端生成与所述用户标识匹配的附加密码；
    所述客户端将所述附加密码与所述用户标识相关联地存储于所述客户端；
    所述客户端将所述用户标识、所述密码以及所述附加密码通过用户注册请求发送至所述服务器，以使得所述服务器将所述附加密码与所述用户标识相关联地存储。
  4. 根据权利要求2所述的方法，其中，所述预先存储的附加密码通过以下方式获得：
    响应于所述用户在所述客户端上的注册操作，所述客户端获取待注册的用户标识和密码；
    所述客户端向所述服务器发送用户注册请求，其中，所述用户注册请求包括所述用户标识和所述密码；
    所述客户端接收所述服务器响应于所述用户注册请求而生成的附加密码；
    所述客户端将所述附加密码与所述用户标识相关联地存储于所述客户端。
  5. 根据权利要求2所述的方法，其特征在于，获取所述附加密码，还包括：
    在所述客户端未存储与所述用户标识匹配的所述附加密码的情况下，所述客户端响应于所述用户的附加密码获取操作，向所述服务器发送附加密码获取请求，其中，所述附加密码获取请求包括所述用户标识；
    所述客户端获取所述用户在所述客户端输入的附加密码，其中，所述附加密码是所述服务器响应于所述附加密码获取请求而通过已登录客户端获取或所述用户标识预先注册的信息接收方式发送至所述用户。
  6. 根据权利要求4所述的方法，其特征在于，当所述附加密码通过二维码发送时，所述客户端通过扫描所述二维码输入所述附加密码。
  7. 根据权利要求1至6任一项所述的方法，其特征在于，向所述服务器发送所述身份验证请求，包括：
    所述客户端通过所述附加密码对所述密码进行加密融合，以获得融合密码；
    所述客户端把所述融合密码和所述用户标识载入所述身份验证请求；
    所述客户端将所述身份验证请求发送至所述服务器。
  8. 根据权利要求1至6任一项所述的方法，其特征在于，向所述服务器发送所述身份验证请求，包括：
    所述客户端将所述用户标识、所述密码及所述附加密码同时载入所述身份验证请求；
    所述客户端将所述身份验证请求发送至所述服务器。
  9. 一种身份验证方法，包括：
    服务器根据接收到的用户注册请求，获取与所述用户注册请求中携带的用户标识匹配的附加密码；
    所述服务器将所述附加密码与所述用户标识相关联地存储；
    所述服务器根据接收到的身份验证请求进行身份验证，其中，所述身份验证请求包括待验证的用户标识、密码及客户端上存储的与所述用户标识关联的附加密码。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    所述服务器接收附加密码获取请求，所述附加密码获取请求至少包括用户标识；
    所述服务器判断所述用户标识是否已经登录；
    若所述用户标识未登录，则所述服务器通过所述用户标识预先注册的接收信息方式发送与所述用户标识匹配的附加密码；
    若所述用户标识已经登录，则所述服务器发送与所述用户标识匹配的附加密码至发送所述附加密码获取请求的客户端。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    若所述用户标识未登录，则所述服务器启动验证码验证；
    若所述验证码验证通过，则所述服务器
    获取与所述附加密码获取请求中携带的用户标识匹配的附加密码，并
    发送所述附加密码至发送所述附加密码获取请求的客户端，用于在所述客户端存储所述附加密码。
  12. 一种终端设备，包括：
    处理器和机器可读存储介质，
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，所述处理器被所述机器可执行指令促使：
    响应于用户的身份验证操作，获取待验证的用户标识和密码；
    根据所述用户标识，获取附加密码；
    向服务器发送身份验证请求，其中，所述身份验证请求包括所述用户标识、所述密码及所述附加密码，以使所述服务器能够响应于所述身份验证请求而基于所述服务器上存储的用户标识、密码和附加密码进行身份验证。
  13. 一种服务器，包括：
    处理器和机器可读存储介质，
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，所述处理器被所述机器可执行指令促使以执行如权利要求9至11任一项所述的身份验证方法。
  14. 一种机器可读存储介质，存储有机器可读指令，在被处理器调用和执行时，所述机器可执行指令促使所述处理器执行如权利要求1至8任一项所述的身份验证方法。
  15. 一种机器可读存储介质，存储有机器可读指令，在被处理器调用和执行时，所述机器可执行指令促使所述处理器执行如权利要求9至11任一项所述的身份验证方法。
PCT/CN2017/119701 2017-08-24 2017-12-29 身份验证 WO2019037373A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CA3068090A CA3068090A1 (en) 2017-08-24 2017-12-29 Identity authentication
EP17922615.4A EP3618381A4 (en) 2017-08-24 2017-12-29 IDENTITY AUTHENTICATION
KR1020197035648A KR102307665B1 (ko) 2017-08-24 2017-12-29 신원 인증
JP2019565469A JP6936340B2 (ja) 2017-08-24 2017-12-29 身元認証
US16/619,931 US20200213293A1 (en) 2017-08-24 2017-12-29 Identity authentication

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710737863.0 2017-08-24
CN201710737863.0A CN107733852B (zh) 2017-08-24 2017-08-24 一种身份验证方法及装置，电子设备

Publications (1)

Publication Number Publication Date
WO2019037373A1 true WO2019037373A1 (zh) 2019-02-28

Family

ID=61204767

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/119701 WO2019037373A1 (zh) 2017-08-24 2017-12-29 身份验证

Country Status (8)

Country Link
US (1) US20200213293A1 (zh)
EP (1) EP3618381A4 (zh)
JP (1) JP6936340B2 (zh)
KR (1) KR102307665B1 (zh)
CN (1) CN107733852B (zh)
CA (1) CA3068090A1 (zh)
TW (1) TWI686075B (zh)
WO (1) WO2019037373A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852681A (zh) * 2021-09-22 2021-12-28 深信服科技股份有限公司 一种网关认证方法、装置及安全网关设备
CN114866251A (zh) * 2022-04-25 2022-08-05 中国银联股份有限公司 一种设备互联安全认证系统、方法、装置、服务器及介质

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108183924A (zh) * 2018-03-01 2018-06-19 深圳市买买提信息科技有限公司 一种登录验证方法及终端设备
CN108183798A (zh) * 2018-03-13 2018-06-19 深圳市欧乐在线技术发展有限公司 应用的实名认证方法、服务器、移动终端及可读存储介质
CN110213597B (zh) * 2018-03-30 2021-09-07 腾讯科技（深圳）有限公司 一种通过浏览器进入直播房间的方法和装置
US10778678B2 (en) 2018-07-18 2020-09-15 Alibaba Group Holding Limited Identity identification and preprocessing
CN111182010B (zh) * 2018-11-09 2023-04-07 杭州海康威视数字技术股份有限公司 一种本地服务提供方法及装置
CN111356091B (zh) * 2018-12-21 2021-08-27 中国移动通信集团终端有限公司 消息发送、接收方法及终端
CN109982413B (zh) * 2019-02-19 2023-04-07 北京三快在线科技有限公司 移动热点的识别方法、装置、电子设备和存储介质
CN111901353A (zh) * 2019-07-18 2020-11-06 创新先进技术有限公司 身份识别预处理方法、身份识别方法，及其设备和系统
CN110691093B (zh) * 2019-10-08 2022-04-08 迈普通信技术股份有限公司 密码找回方法、装置、网络设备及计算机可读存储介质
CN110808966A (zh) * 2019-10-23 2020-02-18 天津华来科技有限公司 身份信息生成方法、装置及存储介质
CN112995577A (zh) * 2019-12-02 2021-06-18 中兴通讯股份有限公司 终端桌面内容的监控方法、平台、终端、系统及存储介质
CN111339270B (zh) * 2020-02-20 2023-04-25 中国农业银行股份有限公司 一种密码校验方法及装置
CN111340449B (zh) * 2020-02-27 2023-05-02 吴雅君 一种人力资源用共享服务系统
CN113472716B (zh) * 2020-03-30 2023-09-19 中移互联网有限公司 系统访问方法、网关设备、服务器、电子设备及存储介质
EP3896588B1 (en) * 2020-04-18 2024-03-06 Deutsche Telekom AG Backlock access for logging into a computing device
CN111565179B (zh) * 2020-04-27 2022-12-06 北京奇艺世纪科技有限公司 身份校验方法、装置、电子设备及存储介质
US11405216B2 (en) * 2020-05-07 2022-08-02 Adp, Inc. System for authenticating verified personal credentials
CN111783075B (zh) * 2020-06-28 2022-09-09 平安普惠企业管理有限公司 基于密钥的权限管理方法、装置、介质及电子设备
CN111787005B (zh) * 2020-06-30 2023-02-17 中国工商银行股份有限公司 一种动态加密的安全登录方法及装置
CN112100611A (zh) * 2020-08-14 2020-12-18 广州江南科友科技股份有限公司 一种密码生成方法、装置、存储介质和计算机设备
CN114221774A (zh) * 2020-09-04 2022-03-22 中兴通讯股份有限公司 鉴权方法、服务器、终端设备及存储介质
CN112784254A (zh) * 2020-12-28 2021-05-11 深圳恒芯安全信息技术有限公司 一种口令管理方法、装置、终端设备及存储介质
US12021861B2 (en) * 2021-01-04 2024-06-25 Bank Of America Corporation Identity verification through multisystem cooperation
CN113536259A (zh) * 2021-07-29 2021-10-22 合肥新青罗数字技术有限公司 企业服务平台的实名认证方法
CN113992982A (zh) * 2021-10-25 2022-01-28 深圳康佳电子科技有限公司 一种节目数据同步配置方法、装置、终端设备及存储介质
CN116911988B (zh) * 2023-04-04 2024-04-05 深圳市奥盛通科技有限公司 交易数据处理方法、系统、计算机设备及存储介质
CN116389168B (zh) * 2023-05-31 2023-08-29 北京芯盾时代科技有限公司 一种身份认证方法和装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868732A (zh) * 2012-08-27 2013-01-09 北京小米科技有限责任公司 一种基于账户密码的登录实现方法、系统及装置
CN103747013A (zh) * 2014-01-24 2014-04-23 沈文策 一种云端登录验证方法及装置
CN104079409A (zh) * 2014-06-10 2014-10-01 百度在线网络技术（北京）有限公司 账号的登录方法及装置
CN104601532A (zh) * 2013-10-31 2015-05-06 腾讯科技（深圳）有限公司 一种登录账户的方法及装置
US20150237038A1 (en) * 2014-02-18 2015-08-20 Secureauth Corporation Fingerprint based authentication for single sign on
CN105407074A (zh) * 2014-09-11 2016-03-16 腾讯科技（深圳）有限公司 身份验证方法、装置及系统

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008015877A (ja) * 2006-07-07 2008-01-24 Fujitsu Ltd 認証システム及びその方法
CN101465735B (zh) * 2008-12-19 2011-06-01 北京大学 网络用户身份验证方法、服务器及客户端
CN102025506A (zh) * 2010-12-20 2011-04-20 中国联合网络通信集团有限公司 用户身份验证方法及装置
CN102184501A (zh) * 2011-03-24 2011-09-14 上海博路信息技术有限公司 一种移动终端的电子优惠券系统
CN102202067B (zh) * 2011-07-15 2016-06-08 席勇良 动态随机密码登录方法
US8490162B1 (en) * 2011-09-29 2013-07-16 Amazon Technologies, Inc. System and method for recognizing malicious credential guessing attacks
KR101420149B1 (ko) * 2012-05-02 2014-07-17 주식회사 시큐브 이중 인증 로그인 시스템 및 방법
US9053304B2 (en) * 2012-07-13 2015-06-09 Securekey Technologies Inc. Methods and systems for using derived credentials to authenticate a device across multiple platforms
CN103384248B (zh) * 2013-07-08 2016-03-02 张忠义 一种可以防止黑客程序再次登陆的方法
US9432358B2 (en) * 2013-10-31 2016-08-30 Tencent Technology (Shenzhen) Company Limited System and method of authenticating user account login request messages
CN106549759A (zh) * 2015-09-16 2017-03-29 阿里巴巴集团控股有限公司 身份认证方法和装置
CN106355106A (zh) * 2016-08-30 2017-01-25 深圳市引导美电子商务有限公司 一种账户信息存储方法及系统
CN106452772B (zh) * 2016-11-16 2019-10-25 华为技术有限公司 终端认证方法和装置
CN106954216B (zh) * 2017-04-28 2020-07-14 北京北信源软件股份有限公司 基于802.1x协议的认证方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868732A (zh) * 2012-08-27 2013-01-09 北京小米科技有限责任公司 一种基于账户密码的登录实现方法、系统及装置
CN104601532A (zh) * 2013-10-31 2015-05-06 腾讯科技（深圳）有限公司 一种登录账户的方法及装置
CN103747013A (zh) * 2014-01-24 2014-04-23 沈文策 一种云端登录验证方法及装置
US20150237038A1 (en) * 2014-02-18 2015-08-20 Secureauth Corporation Fingerprint based authentication for single sign on
CN104079409A (zh) * 2014-06-10 2014-10-01 百度在线网络技术（北京）有限公司 账号的登录方法及装置
CN105407074A (zh) * 2014-09-11 2016-03-16 腾讯科技（深圳）有限公司 身份验证方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3618381A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113852681A (zh) * 2021-09-22 2021-12-28 深信服科技股份有限公司 一种网关认证方法、装置及安全网关设备
CN114866251A (zh) * 2022-04-25 2022-08-05 中国银联股份有限公司 一种设备互联安全认证系统、方法、装置、服务器及介质
CN114866251B (zh) * 2022-04-25 2023-07-07 中国银联股份有限公司 一种设备互联安全认证系统、方法、装置、服务器及介质

Also Published As

Publication number Publication date
TWI686075B (zh) 2020-02-21
CN107733852B (zh) 2019-06-21
CN107733852A (zh) 2018-02-23
KR102307665B1 (ko) 2021-10-01
JP2020523664A (ja) 2020-08-06
JP6936340B2 (ja) 2021-09-15
TW201914256A (zh) 2019-04-01
EP3618381A4 (en) 2020-09-23
CA3068090A1 (en) 2019-02-28
US20200213293A1 (en) 2020-07-02
EP3618381A1 (en) 2020-03-04
KR20200003158A (ko) 2020-01-08

Similar Documents

Publication Publication Date Title
WO2019037373A1 (zh) 身份验证
US20230231718A1 (en) Method of using one device to unlock another device
US11764966B2 (en) Systems and methods for single-step out-of-band authentication
US10826882B2 (en) Network-based key distribution system, method, and apparatus
US20170063827A1 (en) Data obfuscation method and service using unique seeds
WO2017206250A1 (zh) 终端的备份销毁方法和装置
US11038684B2 (en) User authentication using a companion device
US10511438B2 (en) Method, system and apparatus using forward-secure cryptography for passcode verification
US20200233947A1 (en) System and method for facilitating authentication via a short-range wireless token
US20180053018A1 (en) Methods and systems for facilitating secured access to storage devices
US10333707B1 (en) Systems and methods for user authentication
CN103888429A (zh) 虚拟机启动方法、相关设备和系统
CN111901303A (zh) 设备认证方法和装置、存储介质及电子装置
WO2018099407A1 (zh) 账户认证登录方法及装置
US20140250499A1 (en) Password based security method, systems and devices
KR102016976B1 (ko) 싱글 사인 온 서비스 기반의 상호 인증 방법 및 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17922615

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019565469

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20197035648

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017922615

Country of ref document: EP

Effective date: 20191129

ENP Entry into the national phase

Ref document number: 3068090

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE