# US 2016/0262013 A1 · Soft token system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0262013 A1
- Document ID: US20160262013A1
- Status: Published application
- Kind: A1
- Application number: 15/154,977
- Filed: 2016-05-14
- Published: 2016-09-08
- Earliest claimed: 2013-03-15
- Assignees: Fortinet, Inc.
- Applicants: Fortinet, Inc.
- Inventors: David A. Redberg; Jun Li
- Web page: https://patentgrep.com/patent/US20160262013A1

## CPC

- H04W 8/245: {from a network towards a terminal}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 63/0272: {Virtual private networks}
- 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)}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/067: {using one-time keys (cryptographic mechanisms or cryptographic arrangements for generation of one-time passwords H04L9/0863)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0838: {using one-time-passwords}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L 63/10: {for controlling access to devices or network resources}
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W 12/06: Authentication
- H04L 2209/80: Wireless
- H04W 12/71: Hardware identity
- H04W 88/02: Terminal devices
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for a secure soft token solution applicable to multiple platforms and usage scenarios are provided. According to one embodiment, a user of a mobile device is prompted to input an activation code previously provided to the user by an authentication server, which authenticates credentials provided by users of a secure network resource that is accessible via an IP-based network. A unique device ID of the mobile device is obtained via an API of an operating system of the mobile device. A seed is requested from a provisioning server. The seed is received in encrypted form based on a combination of a secret key, the unique device ID and a hardcoded-pre-shared key. The seed is bound to the mobile device by encrypting the seed based on the unique device ID. When a token is requested by the user it is generated based on the bound seed

## Claims

### Claim 1

A method comprising:
prompting, by a soft token application installed on a mobile device, a user of the mobile device to input an activation code previously provided to the user by an authentication server, wherein the authentication server authenticates credentials provided by users of a secure network resource that is accessible via an Internet Protocol (IP)-based network;
programmatically obtaining, by the soft token application, a unique device ID of the mobile device via an Application Programming Interface (API) of an operating system of the mobile device, wherein the unique device ID uniquely identifies the mobile device;
requesting, by the soft token application via the IP-based network, a token seed from a provisioning server associated with the soft token application by sending a request containing (i) a cryptographic hash of the unique device ID or the unique device ID and (ii) the activation code to the provisioning server, wherein the token seed is for use in connection with generating a token for obtaining access to the secure network resource;
receiving, by the soft token application, the token seed in encrypted form, wherein an encryption key used to generate the encrypted form is based on a combination of a secret key, the unique device ID and a hardcoded-pre-shared key;
binding in a persistent manner, by the soft token application, the token seed to the mobile device by encrypting the token seed based on the unique device ID; and
when the token is requested by the user, generating, by the soft token application, the token based on the bound token seed.

### Claim 2 (depends on 1)

The method of claim 1, wherein said generating, by the soft token application, the token based on the bound token seed comprises:
programmatically obtaining, by the soft token application, the unique device ID via the API;
obtaining the token seed from the bound token seed by decrypting, by the soft token application, the bound token seed based on the unique device ID; and
invoking, by the soft token application, a token generation function with the token seed as an input to the token generation function.

### Claim 3 (depends on 1)

The method of claim 1, further comprising providing, by the provisioning server, automated download assistance of a proper version of the soft token application.

### Claim 4 (depends on 1)

The method of claim 1, wherein the mobile device comprises a smartphone and wherein the unique device ID comprises a Unique Device Identifier (UDID), an International Mobile Equipment Identity (IMEI) or a Mobile Equipment Identifier (MEI).

### Claim 5 (depends on 1)

The method of claim 1, wherein the activation code is received by the mobile device from the authentication server via a first out-of-band channel.

### Claim 6 (depends on 5)

The method of claim 5, wherein the first out-of-band channel comprises electronic mail (email).

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
receiving, by the user from the provisioning server via a second out-of-band channel, the secret key;
prior to said requesting, by the soft token application via an IP-based network, a token seed from a provisioning server, prompting the user, by the soft token application, for the secret key.

### Claim 8 (depends on 7)

The method of claim 7, wherein the second out-of-band channel comprises Short Message Service (SMS).

### Claim 9 (depends on 1)

The method of claim 1, wherein the token comprises a One-Time Password (OTP).

### Claim 10 (depends on 9)

The method of claim 9, wherein the OTP comprises a time-based OTP.

### Claim 11

A non-transitory computer-readable storage medium embodying a set of instructions representing a soft token application, which when executed by one or more processors of a mobile device, cause the one or more processors to perform a method comprising:
prompting a user of the mobile device to input an activation code previously provided to the user by an authentication server, wherein the authentication server authenticates credentials provided by users of a secure network resource that is accessible via an Internet Protocol (IP)-based network;
programmatically obtaining a unique device ID of the mobile device via an Application Programming Interface (API) of an operating system of the mobile device, wherein the unique device ID uniquely identifies the mobile device;
requesting via the IP-based network a token seed from a provisioning server associated with the soft token application by sending a request containing (i) a cryptographic hash of the unique device ID or the unique device ID and (ii) the activation code to the provisioning server, wherein the token seed is for use in connection with generating a token for obtaining access to the secure network resource;
receiving the token seed in encrypted form, wherein an encryption key used to generate the encrypted form is based on a combination of a secret key, the unique device ID and a hardcoded-pre-shared key;
binding in a persistent manner the token seed to the mobile device by encrypting the token seed based on the unique device ID; and
when the token is requested by the user, generating, by the soft token application, the token based on the bound token seed.

### Claim 12 (depends on 11)

The non-transitory computer-readable storage medium of claim 11, wherein said generating the token based on the bound token seed comprises:
programmatically obtaining, by the soft token application, the unique device ID via the API;
obtaining the token seed from the bound token seed by decrypting, by the soft token application, the bound token seed based on the unique device ID; and
invoking, by the soft token application, a token generation function with the token seed as an input to the token generation function.

### Claim 13 (depends on 12)

The non-transitory computer-readable storage medium of claim 12, wherein the mobile device comprises a smartphone and wherein the unique device ID comprises a Unique Device Identifier (UDID), an International Mobile Equipment Identity (IMEI) or a Mobile Equipment Identifier (MEI).

### Claim 14 (depends on 11)

The non-transitory computer-readable storage medium of claim 11, wherein the activation code is received by the mobile device from the authentication server via a first out-of-band channel.

### Claim 15 (depends on 14)

The non-transitory computer-readable storage medium of claim 14, wherein the first out-of-band channel comprises electronic mail (email).

### Claim 16 (depends on 14)

The non-transitory computer-readable storage medium of claim 14, wherein the method further comprises:
receiving, by the user from the provisioning server via a second out-of-band channel, the secret key;
prior to said requesting, by the soft token application via an IP-based network, a token seed from a provisioning server, prompting the user, by the soft token application, for the secret key.

### Claim 17 (depends on 16)

The non-transitory computer-readable storage medium of claim 16, wherein the second out-of-band channel comprises Short Message Service (SMS).

### Claim 18 (depends on 11)

The non-transitory computer-readable storage medium of claim 11, wherein the token comprises a One-Time Password (OTP).

### Claim 19 (depends on 18)

The non-transitory computer-readable storage medium of claim 18, wherein the OTP comprises a time-based OTP.
