# US 12,216,757 B2 · Systems and methods for password managers

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

- Number: US 12,216,757 B2
- Document ID: US12216757B2
- Status: Granted
- Kind: B2
- Application number: 18/425,019
- Filed: 2024-01-29
- Published: 2024-07-18
- Granted: 2025-02-04
- Earliest claimed: 2020-01-27
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Rajko Ilincic; Jeffrey Rule
- Web page: https://patentgrep.com/patent/US12216757B2

## CPC

- G06F 21/45: Structures or tools for the administration of authentication
- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- 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 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/101: {Access control lists [ACL]}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An authentication system comprises a browser extension and a password manager application. The browser extension can be configured for execution on a first user device. The browser extension can be configured to display a response code and receive a login credential from a server. The response code can comprise a unique session identifier identifying the browser extension and a user browsing session. The password manager application can be configured for execution on a second user device. The second user device can have a scanner configured to scan the response code. The password manager application can be configured to extract the unique session identifier, parse the unique session identifier into session identifier content, send a portion of the session identifier content to the server, receive an approval from a user of the second user device, and send a notification to the server.

## Claims

### Claim 1

A system, comprising a first user device including a browser extension and a second user device including a password manager application, wherein:
the browser extension is configured to:
display a code comprising metadata, the metadata including a unique session identifier, a security question, a device identifier, and a browser type identifier; and
receive login credentials from a server; and
the password manager application is configured to:
receive the code;
establish a handshake with the server based on the metadata;
parse the unique session identifier into session identifier content;
send the security question and a portion of the session identifier content to the server; and
receive an approval from the server.

### Claim 2 (depends on 1)

The system of claim 1, wherein the browser extension is further configured to encrypt the received login credentials with a private key.

### Claim 3 (depends on 1)

The system of claim 1, wherein the password manager application is further configured to extract the unique session identifier and the security question.

### Claim 4 (depends on 1)

The system of claim 1, wherein the password manager application is further configured to receive a security question answer from the server, and send a notification to the server, wherein the notification includes the unique session identifier and the login credentials.

### Claim 5 (depends on 1)

The system of claim 1, wherein the unique session identifier identifies the browser extension and a user browsing session, and the browser extension is further configured to perform the login using the credentials.

### Claim 6 (depends on 1)

The system of claim 1, wherein the approval comprises a personal identification number (PIN) or a biometric.

### Claim 7 (depends on 1)

The system of claim 1, wherein the code comprises a bar code or a quick response code.

### Claim 8

A method, comprising:
receiving a secure login option for a login associated with a website, wherein the website is displayed on a first user device;
generating a unique session identifier and sending the unique session identifier to a server;
displaying a code on the first user device, wherein the code includes metadata comprising the unique session identifier, a security question, a device identifier, a browser type identifier, and a time zone identifier;
establishing a handshake with the server based on the metadata;
receiving credentials for the login associated with the unique session identifier from the server; and
performing the login using the credentials.

### Claim 9 (depends on 8)

The method of claim 8, wherein the login is secured through a password manager application on a second user device.

### Claim 10 (depends on 9)

The method of claim 9, wherein the code is scannable by the second user device.

### Claim 11 (depends on 8)

The method of claim 8, further comprising encrypting the credentials using a private key.

### Claim 12 (depends on 8)

The method of claim 8, further comprising transmitting the metadata to the server to establish the handshake.

### Claim 13 (depends on 8)

The method of claim 8, further comprising receiving a security question answer from the server, wherein the security question answer is associated with a password manager application.

### Claim 14 (depends on 8)

The method of claim 8, wherein the unique session identifier identifies a browser extension and a user browsing session.

### Claim 15 (depends on 14)

The method of claim 14, wherein the second user device includes a scanner configured to scan the code.

### Claim 16 (depends on 8)

The method of claim 8, further comprising receiving a whitelist from the server, wherein the secure login option is available for the website because it is a member of the whitelist.

### Claim 17 (depends on 8)

The method of claim 8, wherein the metadata includes at least one selected from the group of an IP address and a time stamp.

### Claim 18

A non-transitory computer-accessible medium having stored thereon computer-executable instructions that, when executed by a computer arrangement, cause the computer arrangement to perform procedures comprising:
receiving a secure login option for a login associated with a website, wherein the website is displayed on a first user device;
generating a unique session identifier and sending the unique session identifier to a server;
displaying a code on the first user device, wherein the code includes metadata comprising the unique session identifier, a security question, a device identifier, a browser type identifier, and a time zone identifier;
establishing a handshake with the server based on the metadata;
receiving credentials for the login associated with the unique session identifier from the server; and
performing the login using the credentials.

### Claim 19 (depends on 18)

The non-transitory computer-accessible medium of claim 18, the procedures further comprise receiving an approval, wherein the approval comprises a two-factor authentication.

### Claim 20 (depends on 18)

The non-transitory computer-accessible medium of claim 18, the procedures further comprise receiving a security question answer and sending a notification to a server, wherein the notification includes the unique session identifier and the login credentials.

### Claim 21 (depends on 8)

The method of claim 8, wherein establishing a handshake with the server is performed on a second user device.
