Secure and efficient authentication using plug-in hardware compatible with desktops, laptops and/or smart mobile communication devices such as iPhones

• US 8,769,784 B2
• Filed: 12/21/2011
• Issued: 07/08/2014
• Est. Priority Date: 11/02/2009
• Status: Active Grant

• Current Assignee: Payfone Incorporated
• Original Assignee: Authentify, Inc. (Early Warning Services, LLC)
• Inventors: Ganesan, Ravi, Rolfe, Andrew Robert, Tapling, Peter George
• Primary Examiner(s): Hoffman, Brandon
• Assistant Examiner(s): Woldemariam, Nega
• Application Number:
  US13/332,912
• Publication Number:
  US 20120124651A1
• Time in Patent Office: 930 Days
• Field of Search: None
• US Class Current: 26/4
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 21/42 using separate channels for security data
• CPC Class Codes: G06F 21/51 at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
• CPC Class Codes: G06F 21/566 Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/80 Wireless network architectures or network communication protocols for wireless network security H04W12/00
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/0838 using one-time-passwords
• 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/18 using different networks or channels, e.g. using out of band channels cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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/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: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

A portable apparatus is removably and communicatively connectable to a network device to communicate authentication or authorization credentials of a user in connection with the user logging into or entering into a transaction with a network site. The apparatus includes a communications port to connect and disconnect the apparatus to and from the network device and to establish a communication link with the network device when connected thereto. A processor receives a secure message from the network security server via the port. The message has a PIN for authenticating the user to the network site, and is readable only by the apparatus. The processor either transfers, via the port, the received PIN to an application associated with the network site that is executing on the network device or causes the apparatus to display the received PIN for manual transfer to the application associated with the network site.

Claims

1. A method of authenticating a user of a network device (ND) having a portable hardware device (PHD) removably and communicatively connected thereto, comprising:

receiving, by a first application executing on the ND, a request for authentication of the user in connection with either (i) the user logging into a network site or (ii) the user entering into a transaction with the network site;

receiving, via the ND, by a second application executing on the PHD from a network security server, after receipt of the request for authentication by the first application, a secure message including a personal identification number (PIN) and readable only by the second application, for authenticating the user to the network site;

transferring the received PIN to the first application; and

directing, by the first application, transmission from the ND to the network site of the transferred PIN, to authenticate the user or authorize the transaction to the network site;

wherein the PIN corresponds to a secret shared only by the security server and the network site, and not by the user, and is not associated with any particular user.

2. The method according to claim 1, wherein received PIN is manually transferred by the user to the first application.

3. The method according to claim 2, further comprising:

directing, by the first application, a presentation to the user by the ND of a web page associated with the network site having the request for authentication; and

directing, by the second application, a presentation to the user by the PHD of the received PIN;

wherein the received PIN is manually transferred to the first application by the user inputting the PIN presented by the PHD into the web page presented by the ND.

4. The method according to claim 1, wherein received PIN is automatically transferred to the first application.

5. The method according to claim 4, further comprising:

storing, by the second application, the received PIN in a public data store within ND;

wherein received PIN is transferred to the first application by the first application retrieving the stored PIN from the public data store.

6. The method according to claim 1, further comprising:

receiving, by the second application, a request of the user to login to the security server;

directing, by the second application, transmission of the request and a user identifier from PHD to the security server via the ND;

receiving, by a third application executing on the ND from the security server, a message including another PIN, in response to the transmitted request;

directing, by the third application, display by the ND of the other PIN;

receiving, by the second application, a user input including the displayed other PIN;

directing, by the second application, transmission, from the PHD to the security server via the ND, of the input other PIN;

receiving, by the second application from the security server via the ND, a session cookie and active session information indicating a period of time during which the session between the second application and the security server will remain active, in response to transmission of the other PIN; and

storing, by the second application, (i) the session cookie in a private data store on the PHD accessible only to the second application and (ii) the active session information in a public data store accessible to the first application.

7. The method according to claim 1, further comprising:

receiving via the ND, by the second application from the network security server, a seed; and

storing the received seed so that, after the PHD is disconnected from the ND, the seed is at least one of (i) presentable to the user at the PHD for entry by the user into a seeding interface of a token on the PHD or (ii) enterable into the seeding interface of the token without user intervention.

8. The method according to claim 7, wherein the received seed is an intermediate seed for processing by the token to generate the final seed.

9. The method according to claim 1, wherein if the received request for authentication is in connection with the user entering into a transaction with the network site, further comprising:

receiving via the ND, by the second application from the network security server, information associated with the transaction; and

directing, by the second application, a presentation to the user by the PHD of the transaction information.

10. A portable apparatus removably and communicatively connectable to a network device for communicating authentication credentials for a user in connection with either (i) the user logging into a network site or (ii) the user entering into a transaction with the network site, comprising:

a communications port configured to connect and disconnect the apparatus to and from the ND and to establish a communication link between the apparatus and the ND when connected; and

a processor disposed configured to (1) receive, from a network security server via the port, a secure message, readable only by the processor and not by the ND, including a personal identification number (PIN) for authenticating the user to the network site, and (2) either (i) transfer, via the port, the received PIN to an application associated the network site and executing on the ND or (ii) cause the apparatus to display the received PIN to the user for manual transfer of the PIN to the application associated the network site;

wherein the PIN corresponds to a secret shared only by the security server and the network site, and not by the user, and is not associated with any particular user.

11. The apparatus according to claim 10, wherein the ND is a mobile communications device.

12. The apparatus according to claim 11, wherein the mobile communications device is a smart phone.

13. The apparatus according to claim 10, wherein the port is a USB port, a headphone jack, or a bluetooth connection.

14. The apparatus according to claim 10, further comprising:

a data store;

wherein the processor is further configured to (1) receive a request of the user to login to the security server, (2) direct transmission from the port of the request and a user identifier to the security server via the ND, (3) receive a user input including another PIN, and (4) direct transmission from the port to the security server via the ND, of the input other PIN;

wherein the port is further configured to receive from the security server via the ND, a session cookie and active session information indicating a period of time during which the session with the security server will remain active, in response to transmission of the other PIN; and

wherein the data store stores the session cookie so as to be accessible only to the processor.

15. The apparatus according to claim 10, further comprising:

a data store;

wherein the port is further configured to receive from the security server via the ND, a seed; and

wherein the processor is further configured to (i) direct storage of the received seed in the data store and (ii), after the apparatus is disconnected from the ND, at least one of (i) display the stored seed to the user at the apparatus for entry by the user into a seeding interface of a token or (ii) enter the stored seed into the seeding interface of the token without user intervention.

16. The apparatus according to claim 15, wherein the received seed is an intermediate seed for processing by the token to generate the final seed.

17. The apparatus according to claim 10, wherein if the user is entering into a transaction with the network site, the processor is further configured to:

receive, from a network security server via the port, a secure message, readable only by the processor and not by the ND, including information associated with the transaction; and

cause the apparatus to display the received transaction information to the user.