# US 2022/0286289 A1 · Username-less and password-less one-time identification and authentication code method and system

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

- Number: US 2022/0286289 A1
- Document ID: US20220286289A1
- Status: Published application
- Kind: A1
- Application number: 17/752,467
- Filed: 2022-05-24
- Published: 2022-09-08
- Earliest claimed: 2018-10-29
- Assignees: Xiid Corporation
- Applicants: Xiid Corporation
- Inventors: Guido PELLIZZER; Federico SIMONETTI
- Web page: https://patentgrep.com/patent/US20220286289A1

## CPC

- 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}
- 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)}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/0838: {using one-time-passwords}
- 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)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method for a user to access resources within a secure network without inputting a username or password is presented and claimed where the method comprises inputting, by the user, login credentials into an authentication service and obtaining from the authentication service at least one secret code; inputting the at least one secret code into an OTCP to initialize the OTCP; generating within the OTCP a one-time code (OTC) utilizing the at least one secret code but not including the user's login credentials or username; supplying, by the user, the OTC to a secure web portal wherein the secure web portal confirms authenticity of the OTC with the authentication service; and the secure web portal supplying access to the user of the secure web portal resources upon receipt of authentication of the user.

## Claims

### Claim 1

A method for a user to authenticate with an authentication service comprising:
generating within a one-time code producer (OTCP) stored on a token, where the OTCP has been previously initialized, a one-time code (OTC) wherein the OTC does not include either of a user's login credentials or the user's username;
receiving at the authentication service the OTC from the OTCP where the OTC is the only authentication information supplied to the authentication service to authenticate the user; and
authenticating the user in the authentication service using the OTC.

### Claim 2 (depends on 1)

The method for a user to authenticate according to claim 1 wherein the OTCP obtains from the authentication service at least one secret code when the OTCP is initialized.

### Claim 3 (depends on 2)

The method for a user to authenticate with an authentication service according to claim 2 wherein the OTC is generated within the OTCP utilizing the at least one secret code and one of an HOTP or a TOTP.

### Claim 4 (depends on 2)

The method for a user to authenticate with an authentication service according to claim 2 wherein the user logs into the authentication service using the user's login credentials only when initializing the OTCP and to obtain the at least one secret code from the authentication service.

### Claim 5 (depends on 2)

The method for a user to authenticate with an authentication service according to claim 2 wherein the at least one secret code includes at least one of a secret userLink code, a secret userSeed code, a secret groupSeed code, a secret groupPSK code and a secret groupShift code.

### Claim 6 (depends on 5)

The method for a user to authenticate with an authentication service according to claim 5 wherein the secret userLink code does not include the user's username but is associated with the user's username within the authentication service.

### Claim 7 (depends on 5)

The method for a user to authenticate with an authentication service according to claim 5 wherein the secret userLink code does not include the user's username but is associated with the user within the authentication service through a GUID of the user.

### Claim 8 (depends on 1)

The method for a user to authenticate with an authentication service according to claim 1 wherein the token is a mobile computing device.

### Claim 9

A system for a user to access resources within a secure network comprising:
an authentication service;
a one-time code producer (OTCP) running on a token, wherein a user initializes the OTCP with the authentication service and the OTCP receives at least one secret code from the authentication service as part of the OTCP initialization process;
the OTCP generates, after initialization and when the user attempts authentication with the authentication service, a one-time authentication code (OTC) utilizing the at least one secret code where the OTC does not include either of the user's login credentials or the user's username;
the OTC is transmitted from the OTCP to the authentication service and the authentication service authenticates the user using only the OTC; and
a secure web portal supplying access to the user for use of resources of the secure web portal upon receiving notification from the authentication service of authentication of the user.

### Claim 10 (depends on 9)

The system according to claim 9 wherein the at least one secret code includes at least one of a secret userLink code, a secret userSeed code, a secret groupSeed code, a secret groupPSK code and a secret groupShift code.

### Claim 11 (depends on 10)

The system according to claim 10 wherein herein the secret userLink code does not include the user's username but is associated with the user's username within the authentication service.
