Protocol And Method For Client-Server Mutual Authentication Using Event-Based OTP

• US 20100031051A1
• Filed: 02/08/2008
• Published: 02/04/2010
• Est. Priority Date: 06/05/2007
• Status: Active Grant

• Current Assignee: IQVIA, Inc. (IQVIA Holdings, Inc.)
• Original Assignee: Diversinet Corporation
• Inventors: TESLENKO, Konstantin, MACHANI, Salah E.
• Granted Patent: US 8,130,961 B2
• Time in Patent Office: Days
• US Class Current: 713/181
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• 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/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/0838 using one-time-passwords
• CPC Class Codes: H04L 9/0863 involving passwords or one-time passwords network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067
• CPC Class Codes: H04L 9/3228 One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853
• CPC Class Codes: H04L 9/3242 involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC

Abstract

The invention comprises a method of authenticating and encrypting a client-server communication, comprising the steps of: a) generating a first one-time password (OTP1) and a second one-time password (OTP2) from a cryptographic token; b) generating an encryption key (K_ENC) and a MAC key (K_MAC) based on OTP2; c) preparing and protecting the client data using K_ENC and K_MAC; d) sending a request message from the client to the server, the request message containing the protected client data, a cryptographic token identifier (TID) and OTP1; e) validating OTP1 at the server, and generating OTP2 at the server upon successful validation; f) deriving K_ENC and K_MAC from OTP2 at the server; g) processing the request message and generating result data h) encrypting the result data using K_ENC and creating a digest using K_MAC; i) sending the encrypted result data to the client; and i) decrypting the result data at the client using K_ENC and verifying the authenticity of the result data using K_MAC.

Claims

1. A method of authenticating and encrypting a client-server communication, comprising the steps of:

a) generating a first one-time password (OTP1) and a second one-time password (OTP2) from a cryptographic token;

b) generating an encryption key (K_ENC) and a MAC (Message Authentication Code) key (K_MAC) based on OTP2;

c) preparing and protecting client data using K_ENC and K_MAC

d) sending a request message from the client to the server, the request message containing the protected client data, a cryptographic identifier token (TID) and OTP1;

e) validating OTP1 at the server, and generating OTP2 at the server upon successful validation;

f) deriving K_ENC and K_MAC from OTP2 at the server;

g) processing the request message and generating result data;

h) encrypting the result data using K_ENC and creating a digest using K_MAC;

i) sending the encrypted result data to the client; and

j) decrypting the result data at the client using K_ENC and verifying the authenticity of the result data using K_MAC.

2. The method of claim 1, wherein said request message further includes client request data encrypted with K_ENC and the method includes an additional step of decrypting the client request data at the server using K_ENC.

3. The method of claim 2, wherein said request message further includes MAC data encrypted with K_MAC and the method includes an additional step of authenticating the client request data using K_MAC.

4. The method of claim 1, wherein the step of validating OTP1 takes place internally at the server.

5. The method of claim 1, wherein the step of validating OTP1 takes place at a validation service external to the server.

6. The method of claim 1, wherein K_ENC and K_MAC are derived using PKDF2 (Password-Based Key Derivation Function).

7. The method of claim 1, wherein K_MAC is derived using a SHA-1 (Secure Hash Algorithm) MAC algorithm.

8. The method of claim 1, wherein OTP1 and OTP2 are derived using a HMAC-based (Hashed Message Authentication Code) OTP (One-Time Password) algorithm.

9. A data authentication and encryption protocol, comprising:

a) a pair of one-time passwords, OTP1 and OTP2, where OTP1 is used for user validation and OTP2 is used for key generation;

b) an encryption key, K_ENC, derived from OTP2, used to encrypt data; and

c) a MAC key, K_MAC, derived from OTP2, used to authenticate encrypted data,

wherein OTP1, OTP2, K_ENC and K_MAC are derived such that the protocol does not require a public-key infrastructure.

10. The protocol of claim 9, wherein K_ENC and K_MAC are derived using PKDF2 (Password-Based Key Derivation Function).