User authentication based on multiple asymmetric cryptography key pairs

• US 10,356,088 B1
• Filed: 06/19/2017
• Issued: 07/16/2019
• Est. Priority Date: 01/25/2017
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Peddada, Prasad, Elgamal, Taher
• Primary Examiner(s): Patel, Haresh N
• Application Number:
  US15/627,031
• Time in Patent Office: 757 Days
• Field of Search: 713171
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3271 using challenge-response
• CPC Class Codes: H04L 9/3297 involving time stamps, e.g. generation of time stamps
• CPC Class Codes: H04W 12/06 Authentication

Abstract

An ID service provisioned on a server interacts with a corresponding ID app installed on a user device such as a smart phone for secure user authentication (login). A user acquires two asymmetric encryption keys pairs. One of the private keys is secured on SIM on the user device, and the other one stored in the ID app on the user device. At login attempt, the ID service generates two random challenge messages, and encrypts each of them with one of the public keys. Decryption of one challenge is conducted by the SIM and decryption of the other is done by the ID app. A token based on the two decrypted challenge results is returned to the ID service. Alternatively, a single challenge can be double-wrapped with the two keys. The verifies the results and enables secure login without requiring a password.

Claims

1. A user authentication method for an information system comprising the steps of:

receiving a login attempt at a server from a remote user device;

based on the login attempt, accessing a first public key and a second public key, both associated with a user, wherein the first and second public keys are each associated with a corresponding private key of an asymmetric cryptographic key pair;

generating first and second new random challenge messages;

encrypting the first challenge message using the first public key;

encrypting the second challenge message using the second public key;

sending the first and second encrypted challenge messages to the remote user device;

receiving a reply message from the remote user device;

verifying the reply message, including determining whether both of the first and second challenge messages were successfully decrypted; and

based on verifying the reply message, permitting login to the server without requiring a password.

2. The method of claim 1 and further comprising:

at the server, accessing a fragment of the private key associated with the first public key;

at the server, partially decrypting the first encrypted challenge message using the fragment to form a partial result; and

sending the partial result to the remote user device for use in completely decrypting the first encrypted challenge message.

3. The method of claim 2 wherein:

one of the asymmetric cryptographic key pairs is generated using ElGamal technology; and

the other one of the asymmetric cryptographic key pairs is generated using RSA technology.

4. The method of claim 3 wherein the asymmetric cryptographic key pair is generated using ElGamal technology.

5. The method of claim 2 wherein the reply message includes a token authenticator based on the first and second challenge messages.

6. The method of claim 2 and further comprising:

at the server, storing a timestamp associated with at least one of the first and second challenge messages;

after receiving the reply message, comparing a current time to the timestamp; and

based on the comparison, denying the requested login in a case that an elapsed time measured from the timestamp to receiving the reply message exceeds a predetermined time to live.

7. The method of claim 2 wherein the reply message includes a token authenticator, and verifying the reply message includes validating the token authenticator.

8. The method of claim 2 wherein the reply message includes a token authenticator value based on a predetermined cryptographic [one-way] hash function of the first and second decryption results.

9. A user authentication method for an information system comprising the steps of:

receiving a login attempt at a server from a remote user device;

based on the login attempt, accessing a first public key and a second public key, both associated with a user, wherein the first and second public keys are each associated with a corresponding private key of an asymmetric cryptographic key pair;

generating a first new random challenge message;

encrypting the first challenge message using the first public key;

wrapping the encrypted first challenge message using the second public key;

sending the double wrapped encrypted challenge message to the remote user device;

receiving a reply message from the remote user device;

verifying the reply message, including determining whether the double wrapped challenge message was successfully decrypted; and

based on verifying the reply message, permitting login to the server without requiring a password.

10. The method of claim 9 and further comprising:

at the server, accessing a fragment of the private key associated with first public key;

at the server, partially decrypting the first encrypted challenge message using the fragment to form a partial result; and

sending the partial result to the remote user device for use in decrypting the challenge message.

11. The method of claim 9 wherein:

one of the asymmetric cryptographic key pairs is generated using ElGamal technology; and

the other one of the asymmetric cryptographic key pairs is generated using RSA technology.

12. The method of claim 11 wherein the asymmetric cryptographic key pair is generated using ElGamal technology.

13. The method of claim 9 wherein the reply message includes a token authenticator based on decrypting the challenge message.