# US 2017/0257358 A1 · Method and System for Authenticated Login Using Static or Dynamic Codes

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

- Number: US 2017/0257358 A1
- Document ID: US20170257358A1
- Status: Published application
- Kind: A1
- Application number: 15/449,902
- Filed: 2017-03-03
- Published: 2017-09-07
- Earliest claimed: 2016-03-04
- Assignees: ShoCard, Inc.
- Applicants: ShoCard, Inc.
- Inventors: Armin Ebrahimi; Gaurav Khot; Vladimir Reshetnikov; Robert Gadbois
- Web page: https://patentgrep.com/patent/US20170257358A1

## CPC

- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- G06F 21/31: User authentication
- G06F 21/645: {using a third party}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3247: {involving digital signatures}
- H04L 9/3271: {using challenge-response}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- 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)}
- 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/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Method of authentication including sending a login web page to a first device of a user including a scannable code having an envelope ID and a login challenge. The envelope ID generated by an identity manager is associated with a first envelope of data including a session ID. A confirmation login request is received from a second device associated with the user, and includes a second envelope of data comprising the session ID, a user ID, and a seal of the user ID registering the user ID with the identity manager. The confirmation login request to the login challenge is verified using the session ID, and the user is verified using the user ID and seal. User login is authorized upon successful verification of the login challenge and user, and a communication session having the session ID is established between the web server and the first device.

## Claims

### Claim 1

A method of authentication, comprising:
at a web server, sending a login web page to a first device associated with a user, wherein the login web page includes a scannable code comprising an envelope ID and a login challenge, wherein the envelope ID is associated with a first envelope of data comprising a session ID, wherein the envelope ID is generated by an identity manager at a request of the web server;
receiving a confirmation login request responding to the login challenge from a second device associated with the user, wherein the confirmation login request includes a second envelope of data comprising the session ID, a user ID, and a seal of the user ID registering the user ID;
verifying the confirmation login request to the login challenge using the session ID from the confirmation login request;
verifying the user ID based on the seal;
authorizing user login upon successful verification of the login challenge and user ID; and
establishing a communication session having the session ID between the web server and the first device.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving a request for the login web page from the first device at the web server;
generating the session ID in response to the request for the login web page;
generating the first envelope of data;
sending the first envelope of data to the identity manager over a network, wherein the identity manager generates the envelope ID corresponding to the first envelope of data;
receiving the envelope ID from the identity manager;
generating the scannable code including the envelope ID and the login challenge; and
generating the login web page including the scannable code.

### Claim 3 (depends on 1)

The method of claim 1, wherein the scannable code is scanned by a second device of the user to obtain the envelope ID, wherein the second device retrieves the first envelope from the identity manager using the envelope ID, wherein the second device accesses the Session ID from the first envelope.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
generating a digital signature by signing the data within the first envelope with a private key of the web server; and
including the digital signature of the data and a public key of the web server within the first envelope of data so that the first envelope of data can be trusted.

### Claim 5 (depends on 1)

The method of claim 1, wherein the receiving a response comprises:
decrypting the second envelope of data using a private key of the web server, wherein the second envelope of data is encrypted using a public key of the web server.

### Claim 6 (depends on 1)

The method of claim 1, wherein the verifying the confirmation login request further comprises:
verifying the session ID in the confirmation login request is valid; and
confirming that the session ID has not timed-out.

### Claim 7 (depends on 6)

The method of claim 6, wherein the verifying the session ID further comprises:
determining that the session ID in the confirmation login request is valid when it matches the session ID in the first envelope of data.

### Claim 8 (depends on 1)

The method of claim 1, wherein the verifying the user ID further comprises:
extracting a transaction number from the seal of the user ID;
accessing transaction data from a blockchain using the transaction number, wherein the transaction data comprises a public key of the user and a first signature of a first hash of the user ID, wherein the signature is signed by a private key of the user;
generating a second hash of the user ID by hashing the user ID from the second envelope of data;
signing the second hash using the public key of the user to generate a second signature; and
confirming the user when the first signature matches the second signature.

### Claim 9 (depends on 8)

The method of claim 8, wherein the verifying the user ID further comprises:
certifying the user using the user ID and a certification seal included in the second envelope of data.

### Claim 10 (depends on 1)

The method of claim 1, wherein the scannable code comprises one of a QR code, bar code, and PDF417 code.

### Claim 11 (depends on 1)

The method of claim 1, wherein the user ID comprises a public key of the user.

### Claim 12

A method for authentication, comprising:
on a second device associated with a user, scanning a first scannable code on a login web page of a web server displayed on a first device associated with the user, wherein the scannable code comprises an envelope ID and a login challenge, wherein the envelope ID is associated with a first envelope of data generated by the web server and comprising a session ID, wherein the envelope ID is generated by an identity manager at the request of the web server, wherein the envelope ID is used to request the first envelope of data from the identity manager;
generating a challenge envelope of data comprising a shared-string generated by the second device, a first digital signature of a hash of the shared-string using a private key of the user, and a user ID;
sending the challenge envelope of data to the web server over a network;
on the second device, scanning a second scannable code on an updated login web page displayed on the first device, wherein the second scannable code comprises a challenge response including the shared-string and a second digital signature of a hash of the shared-string using a private key of the web server;
verifying the second digital signature using a public key of the web server;
at the second device, generating a confirmation login request responding to the login challenge, wherein the confirmation login request includes a second envelope of data comprising the shared-string, the session ID, the user ID, and a seal of the user ID registering the user ID with the identity manager; and
sending the confirmation login request to the web server via the identity manager for authentication and login of the user with the web server.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
encrypting the challenge envelope of data using the public key of the web server;

### Claim 14 (depends on 12)

The method of claim 12, wherein the web server verifies the confirmation login request using the session ID from the confirmation login request, wherein the web server verifies the user using the user ID and seal, wherein the web server authorizes user login upon successful verification of the login challenge and user, and wherein a communication session having the session ID is established between the web server and the first device.

### Claim 15 (depends on 12)

The method of claim 12, further comprising:
sending a request to the identity manager for the first envelope of data, wherein the request includes the envelope ID; and
receiving the first envelope of data from the identity manager.

### Claim 16 (depends on 12)

The method of claim 12, further comprising:
decrypting the challenge response including the shared-string and a second digital signature using a private key of the user, wherein the challenge response is encrypted using the public key of the user by the web server.

### Claim 17 (depends on 12)

The method of claim 12, wherein the first scannable code comprises one of a QR code, bar code, and pdf 417 code.

### Claim 18

A method for authentication, comprising:
at a web server, receiving from a device of a user a user envelope of data that includes user data and a first signature of a hash of the user data signed by a private key of the user, wherein the user data comprises a user ID, newly created biometric data, newly presented original biometric data associated with the newly created biometric data, registration seal associated with the original biometric data comprising a first transaction number of a first blockchain, and a certifying seal associated with the original biometric data comprising a second transaction number of a second blockchain;
verifying the first signature using the public key of the user; and
verifying the certification of the original biometric data using the certifying seal and the newly presented original biometric data.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
at the device, capturing the newly created biometric data.

### Claim 20 (depends on 18)

The method of claim 18, wherein the biometric data comprises one of a digital fingerprint of the user, audio file of the user, digital image of a face of the user, and digital video of a face of the user.

### Claim 21 (depends on 18)

The method of claim 18, further comprising;
verifying the registration of the original biometric data using the registration seal and the newly presented original biometric data.

### Claim 22 (depends on 18)

The method of claim 18, further comprising:
comparing the newly created biometric data and the newly presented original biometric data; and
authenticating the user when the newly created biometric data and the newly presented original biometric data match.

### Claim 23 (depends on 22)

The method of claim 22, further comprising:
at the web server, sending a login web page to another device associated with the user, wherein the login web page includes a scannable code comprising an envelope ID and a login challenge, wherein the envelope ID is associated with a first envelope of data comprising a session ID, wherein the envelope ID is generated by an identity manager at the request of the web server;
receiving a confirmation login request responding to the login challenge from the device associated with the user, wherein the confirmation login request includes a second envelope of data comprising the session ID, the user ID, newly created biometric data, and a seal of the user ID registering the user ID with the identity manager;
verifying the confirmation login request to the login challenge using the session ID from the confirmation login request;
verifying the user using the user ID and seal;
authenticating the user using the newly created biometric data;
authorizing user login upon successful verification of the login challenge and user and successful authentication of the user; and
establishing a communication session having the session ID between the web server and the another device of the user.

### Claim 24 (depends on 23)

The method of claim 23, further comprising:
receiving a request for the login web page from the another device at the web server generating the session ID in response to the request for the login web page;
generating the first envelope of data;
sending the first envelope of data to the identity manager over a network, wherein the identity manager generates the envelope ID corresponding to the first envelope of data;
receiving the envelope ID from the identity manager;
generating the scannable code including the envelope ID and the login challenge; and
generating the login web page including the scannable code.

### Claim 25 (depends on 22)

The method of claim 22, further comprising:
controlling access to the user to a product or service based on the authentication of the user.

### Claim 26 (depends on 25)

The method of claim 25, further comprising:
controlling access based on an authorized period of time for access.

### Claim 27 (depends on 18)

The method of claim 18, further comprising:
decrypting the user data using a private key of the web server, wherein the user data is encrypted using the public key of the web server.

### Claim 28 (depends on 18)

The method of claim 18, wherein the user ID comprises a public key of the user.
