USER AUTHENTICATION OVER NETWORKS

• US 20170034133A1
• Filed: 07/28/2015
• Published: 02/02/2017
• Est. Priority Date: 07/28/2015
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Korondi, Mark, Kovacs, Daniel, Nagy, Zoltan Arnold
• Granted Patent: US 9,674,158 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/06 for supporting key management in a packet data network cryptographic mechanisms or cryptographic arrangements for key management H04L9/08
• 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/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 9/006 involving public key infrastructure [PKI] trust models network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/0618 Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• 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/3226 using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

Methods are provided for authenticating user authentication data, associated with a user ID, at an authentication system. The authentication system comprises an authentication server connected to a network, and a secure cryptoprocessor operatively coupled to the authentication server. A first token for the user ID is provided in data storage operatively coupled to the authentication server. The first token is produced by the secure cryptoprocessor by encoding the user authentication data associated with the user ID via an encoding process dependent on a secret key of the secure cryptoprocessor. The authentication server receives an authentication request for the user ID from a remote computer via the network. The authentication request comprises a ciphertext encrypting user authentication data under a public key of a first public-private key pair, the private key of which is secret to the secure cryptoprocessor. The authentication server supplies the ciphertext to the secure cryptoprocessor which decrypts the ciphertext using this private key to obtain plaintext user authentication data. The authentication server retrieves the first token for the user ID from the data storage. The authentication system checks for equality of the plaintext user authentication data and the user authentication data encoded in the first token via a cryptographic processing operation in which the authentication data is not exposed outside the secure cryptoprocessor. In response to such equality, the authentication server sends an authentication confirmation message to the remote computer via the network.

Claims

1. A method for authenticating user authentication data, associated with a user ID, at an authentication system comprising an authentication server connected to a network and a secure cryptoprocessor operatively coupled to the authentication server, the method comprising:

providing, in data storage operatively coupled to the authentication server, a first token for said user ID, the first token being produced by the secure cryptoprocessor by encoding the user authentication data associated with the user ID via an encoding process dependent on a secret key of the secure cryptoprocessor;

at the authentication server, receiving an authentication request for the user ID from a remote computer via the network, the authentication request comprising a ciphertext encrypting user authentication data under a public key of a first public-private key pair the private key of which is secret to the secure cryptoprocessor, and supplying the ciphertext to the secure cryptoprocessor;

at the secure cryptoprocessor, decrypting the ciphertext using said private key to obtain plaintext user authentication data;

at the authentication server, retrieving said first token for the user ID from said data storage;

in the authentication system, checking for equality of said plaintext user authentication data and the user authentication data encoded in the first token via a cryptographic processing operation in which the authentication data is not exposed outside the secure cryptoprocessor; and

at the authentication server, in response to said equality, sending an authentication confirmation message to the remote computer via the network.

2. A method as claimed in claim 1 including, in a registration operation for said user ID:

at the authentication server, receiving a registration request for the user ID from the remote computer via the network, the registration request comprising a ciphertext encrypting the user authentication data associated with the user ID under said public key, and supplying the ciphertext to the secure cryptoprocessor;

at the secure cryptoprocessor, decrypting the ciphertext using said private key to obtain the user authentication data associated with the user ID, encoding the user authentication data via said encoding process dependent on said secret key to produce said first token, and supplying the first token to the authentication server; and

at the authentication server, storing the first token for the user ID in said data storage.

3. A method as claimed in claim 1 wherein said ciphertext in the user authentication request encrypts said user authentication data and an authentication nonce, and wherein the method includes:

at the secure cryptoprocessor, in response to said equality, producing an authentication signature comprising the authentication nonce cryptographically signed with a private key, secret to the secure cryptoprocessor, of a second public-private key pair, and supplying the signature to the authentication server;

wherein said authentication confirmation message comprises the authentication signature.

4. A method as claimed in claim 1 including:

at the secure cryptoprocessor, in response to failure of the equality check, producing a failure signature comprising the authentication nonce cryptographically signed with a private key, secret to the secure cryptoprocessor, of a second public-private key pair, and supplying the failure signature to the authentication server; and

at the authentication server, sending an authentication failure message, comprising the failure signature, to the remote computer via the network.

5. A method as claimed in claim 1 wherein said first token is produced by encoding the user authentication data associated with the user ID via a deterministic function using said secret key, and wherein the method includes:

at the secure cryptoprocessor, encoding said plaintext user authentication data via said deterministic function using said secret key to produce a second token, and supplying the second token to the authentication server; and

at the authentication server, comparing the first and second tokens to check for said equality.

6. A method as claimed in claim 1 including, in a registration operation for said user ID:

at the authentication server, receiving a registration request for the user ID from the remote computer via the network, the registration request comprising a ciphertext encrypting the user authentication data associated with the user ID, and a registration nonce, under said public key, and supplying the ciphertext to the secure cryptoprocessor;

at the secure cryptoprocessor, decrypting the ciphertext using said private key to obtain the user authentication data associated with the user ID and the registration nonce, encrypting the user authentication data and the registration nonce under said public key to produce said first token, and supplying the first token to the authentication server; and

at the authentication server, storing the first token for the user ID in said data storage.

7. A method as claimed in claim 6 including, in said registration operation:

at the secure cryptoprocessor, producing a registration signature comprising the registration nonce cryptographically signed with a private key, secret to the secure cryptoprocessor, of a second public-private key pair, and supplying the registration signature to the authentication server; and

at the authentication server, sending a registration confirmation message, comprising the registration signature, to the remote computer via the network.

8. A method as claimed in claim 6 including:

at the authentication server, in response to said authentication request, supplying the first token to the secure cryptoprocessor; and

at the secure cryptoprocessor, decrypting the first token using said private key to obtain the user authentication data associated with the user ID and comparing that user authentication data with said plaintext user authentication data to check for said equality.

9. A method as claimed in claim 1 wherein said first token is produced by encoding the user authentication data associated with the user ID via a deterministic function using said secret key to produce a preliminary token, and encrypting the preliminary token under said public key to produce the first token, and wherein the method includes:

at the authentication server, supplying the first token to the secure cryptoprocessor;

at the secure cryptoprocessor, decrypting the first token using said private key to obtain the preliminary token, encoding said plaintext user authentication data via said deterministic function using said secret key to produce a second token, and

comparing the second token and the preliminary token to check for said equality.

10. A method as claimed in claim 9 including, in a registration operation for said user ID:

at the authentication server, receiving a registration request for the user ID from the remote computer via the network, the registration request comprising a ciphertext encrypting the user authentication data associated with the user ID, and a registration nonce, under said public key, and supplying the ciphertext to the secure cryptoprocessor;

at the secure cryptoprocessor, decrypting the ciphertext using said private key to obtain the user authentication data associated with the user ID and the registration nonce, encoding the user authentication data associated with the user ID via said deterministic function using said secret key to produce said preliminary token, encrypting the preliminary token and the registration nonce under said public key to produce the first token, and supplying the first token to the authentication server; and

at the authentication server, storing the first token for the user ID in said data storage.

11. A method as claimed in claim 10 including, in said registration operation:

at the secure cryptoprocessor, producing a registration signature comprising the registration nonce cryptographically signed with a private key, secret to the secure cryptoprocessor, of a second public-private key pair, and supplying the registration signature to the authentication server; and

at the authentication server, sending a registration confirmation message, comprising the registration signature, to the remote computer via the network.

12. A method as claimed in claim 1 wherein said user authentication data associated with the user ID comprises the user ID and user password data.

13. A system for authenticating user authentication data associated with a user ID, the system comprising an authentication server connectable to a network, a secure cryptoprocessor operatively coupled to the authentication server, and data storage, operatively coupled to the authentication server, for storing for said user ID a first token produced by the secure cryptoprocessor by encoding the user authentication data associated with the user ID via an encoding process dependent on a secret key of the secure cryptoprocessor, wherein:

the authentication server is adapted, in response to receipt of an authentication request for the user ID from a remote computer via the network, the authentication request comprising a ciphertext encrypting user authentication data under a public key of a first public-private key pair the private key of which is secret to the secure cryptoprocessor, to supply the ciphertext to the secure cryptoprocessor and to retrieve said first token for the user ID from the data storage;

the secure cryptoprocessor is adapted to decrypt the ciphertext using said private key to obtain plaintext user authentication data;

the system is adapted to check for equality of said plaintext user authentication data and the user authentication data encoded in the first token via a cryptographic processing operation in which the authentication data is not exposed outside the secure cryptoprocessor; and

the authentication server is adapted, in response to said equality, to send an authentication confirmation message to the remote computer via the network.

14. A system as claimed in claim 13 wherein said first token comprises an encoding of the user authentication data associated with the user ID via a deterministic function using said secret key, and wherein:

the secure cryptoprocessor is adapted to encode said plaintext user authentication data via said deterministic function using said secret key to produce a second cryptographic token, and to supply the second token to the authentication server; and

the authentication server is adapted to compare the first and second tokens to check for said equality.

15. A system as claimed in claim 13 wherein:

the authentication server is adapted, in a registration operation for said user ID wherein the authentication server receives a registration request for the user ID from the remote computer via the network, the registration request comprising a ciphertext encrypting the user authentication data associated with the user ID, and a registration nonce, under said public key, to supply the ciphertext to the secure cryptoprocessor;

the secure cryptoprocessor is adapted, in response to receipt of the ciphertext in said registration operation, to decrypt the ciphertext using said private key to obtain the user authentication data associated with the user ID and the registration nonce, to encrypt the user authentication data and the registration nonce under said public key to produce said first token, and to supply the first token to the authentication server;

the authentication server is adapted, in response to receipt of the first token in said registration operation, to store the first token for the user ID in said data storage;

the authentication server is adapted, in response to said authentication request, to supply the first token to the secure cryptoprocessor; and

the secure cryptoprocessor is adapted, in response to receipt of the first token, to decrypt the first token using said private key to obtain the user authentication data associated with the user ID and to compare that user authentication data with said plaintext user authentication data to check for said equality.

16. A system as claimed in claim 13 wherein said first token comprises an encryption under said public key of a preliminary token produced by encoding the user authentication data associated with the user ID via a deterministic function using said secret key, and wherein:

the authentication server is adapted, in response to said authentication request, to supply the first token to the secure cryptoprocessor;

the secure cryptoprocessor is adapted, in response to receipt of the first token, to decrypt the first token using said private key to obtain the preliminary token, to encode said plaintext user authentication data via said deterministic function using said secret key to produce a second token, and to compare the second token and the preliminary token to check for said equality.

17. A computer program product for authenticating user authentication data, associated with a user ID, in an authentication system comprising an authentication server connectable to a network, a secure cryptoprocessor operatively coupled to the authentication server, and data storage, operatively coupled to the authentication server, for storing for said user ID a first token produced by the secure cryptoprocessor by encoding the user authentication data associated with the user ID via an encoding process dependent on a secret key of the secure cryptoprocessor, said computer program product comprising a computer readable storage medium having embodied therein:

first program instructions executable by the authentication server after receipt by the server of an authentication request for the user ID from a remote computer via the network, the authentication request comprising a ciphertext encrypting user authentication data under a public key of a first public-private key pair the private key of which is secret to the secure cryptoprocessor, to cause the server to supply the ciphertext to the secure cryptoprocessor and to retrieve said first token for the user ID from the data storage;

second program instructions executable by the secure cryptoprocessor to cause the cryptoprocessor to decrypt the ciphertext using said private key to obtain plaintext user authentication data;

third program instructions executable by at least one of the server and cryptoprocessor of said system to cause the system to check for equality of said plaintext user authentication data and the user authentication data encoded in the first token via a cryptographic processing operation in which the authentication data is not exposed outside the secure cryptoprocessor; and

fourth program instructions executable by the authentication server, in response to said equality, to cause the server to send an authentication confirmation message to said remote computer via the network.

18. A computer program product as claimed in claim 17 wherein said first token comprises an encoding of the user authentication data associated with the user ID via a deterministic function using said secret key, and wherein said third program instructions comprise:

fifth program instructions executable by the secure cryptoprocessor to cause the cryptoprocessor to encode said plaintext user authentication data via said deterministic function using said secret key to produce a second cryptographic token, and to supply the second token to the authentication server; and

sixth program instructions executable by the authentication server to cause the server to compare the first and second tokens to check for said equality.

19. A computer program product as claimed in claim 17 including:

seventh program instructions executable by the authentication server in a registration operation for said user ID wherein the server receives a registration request for the user ID from the remote computer via the network, the registration request comprising a ciphertext encrypting the user authentication data associated with the user ID, and a registration nonce, under said public key, to cause the server to supply the ciphertext to the secure cryptoprocessor;

eighth program instructions executable by the secure cryptoprocessor to cause the cryptoprocessor, in response to receipt of the ciphertext in said registration operation, to decrypt the ciphertext using said private key to obtain the user authentication data associated with the user ID and the registration nonce, to encrypt the user authentication data and the registration nonce under said public key to produce said first token, and to supply the first token to the authentication server; and

ninth program instructions executable by the authentication server, to cause the server, in response to receipt of the first token in said registration operation, to store the first token for the user ID in said data storage;

wherein said third program instructions comprise tenth program instructions executable by the authentication server, to cause the server, in response to said authentication request, to supply the first token to the secure cryptoprocessor, and eleventh program instructions executable by the secure cryptoprocessor to cause the cryptoprocessor, in response to receipt of the first token, to decrypt the first token using said private key to obtain the user authentication data associated with the user ID and to compare that user authentication data with said plaintext user authentication data to check for said equality.

20. A computer program product as claimed in claim 17 wherein said first token comprises an encryption under said public key of a preliminary token produced by encoding the user authentication data associated with the user ID via a deterministic function using said secret key, and wherein said third program instructions comprise:

twelfth program instructions executable by the authentication server, to cause the server, in response to said authentication request, to supply the first token to the secure cryptoprocessor; and

thirteenth program instructions executable by the secure cryptoprocessor to cause the cryptoprocessor, in response to receipt of the first token, to decrypt the first token using said private key to obtain the preliminary token, to encode said plaintext user authentication data via said deterministic function using said secret key to produce a second token, and to compare the second token and the preliminary token to check for said equality.