IP Library Granted Patent US 10,496,810
Granted Patent B2
US 10,496,810 · App. 15/715,815 · Granted Dec 3, 2019

Methods and systems of performing preemptive generation of second factor authentication

Inventors: Justin Lewis (Marina Del Ray, CA); Thomas Price (San Francisco, CA)
Assignee: Google LLC
G06F21/41G06F21/40H04L63/0815H04L63/0884H04L63/108H04L2463/082
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,496,810
App. No.
15/715,815
Granted
Dec 3, 2019
Kind
B2
Abstract

A method includes prompting, by a first application installed on a client electronic device, a user to install a second application on the client electronic device, and prompting, by the first application, the user to authorize preemptive sign-in to the second application. In response to receiving an indication from the user to install the second application and receiving an indication from the user to authorize preemptive sign-in to the second application, the second application is installed, and a two-factor authentication code that authorizes the user to sign into the second application is generated. The method includes sending a message to the second application, launching the second application, and automatically signing the user into the second application without requiring the user to provide the two-factor authentication code or any other form of second-factor authentication.

Claims (57)

1. A method comprising:

prompting, by a first application installed on a client electronic device, a user to install a second application on the client electronic device;

prompting, by the first application, the user to authorize the first application to generate a two-factor authentication code for sign-in to the second application;

in response to receiving an indication from the user to install the second application and receiving an indication from the user to authorize the first application to generate a two-factor authentication code:

installing, on the client electronic device, the second application, and

generating, by the first application, the two-factor authentication code;

sending, by the first application, a message to the second application installed on the client electronic device, wherein the message comprises the two-factor authentication code;

launching the second application installed on the client electronic device; and

automatically signing the user into the second application using the two-factor authentication code without prompting, by the second application, the user to provide the two-factor authentication code.

2. The method of claim 1 , wherein generating the two-factor authentication code comprises using a private key associated with the first application to generate the two-factor authentication code.

3. The method of claim 1 , wherein sending the message to the second application comprises embedding the two-factor authentication code in the message.

4. The method of claim 3 , wherein embedding the two-factor authentication code in the message comprises embedding the two-factor authentication code in a marketing tag of the message.

5. The method of claim 1 , further comprising encrypting, by the first application, at least a portion of the message using a private key associated with the first application.

6. The method of claim 5 , further comprising:

sending, by the second application, the at least a portion of the message to a sign-in server; and

receiving, by the second application, an indication from the sign-in server that the two-factor authentication code is valid.

7. The method of claim 1 , wherein automatically signing the user into the second application comprises automatically signing the user into the second application in the absence of an Internet connection.

8. The method of claim 1 , further comprising obtaining one or more access credentials associated with the user to access the second application, wherein the one or more access credentials do not comprise the two-factor authentication code.

9. The method of claim 1 , wherein the two-factor authentication code further comprises dynamic data associated with a clock or a counter of the client electronic device.

10. A method comprising:

receiving, by one or more servers from a first application on a client electronic device, a two-factor authentication code for a user to sign-in to a second application on the client electronic device;

receiving, by the one or more servers from the second application, a message indicating that the user confirms sign-in to the second application;

determining, by the one or more servers, that the two-factor authentication code received from the first application is valid; and

sending, by the one or more servers to the second application, one or more instructions not to prompt the user for the two-factor authentication code.

11. The method of claim 10 , wherein the two-factor authentication code is associated with one or more of:

a time period during which the two-factor authentication code is valid;

a number of uses for which the two-factor authentication code is valid; or

an identifier of the second application for which the two-factor authentication code is valid.

12. A system comprising:

a client electronic device, wherein a first application is installed on the client electronic device;

a computer-readable storage medium comprising one or more programming instructions that, when executed, cause the client electronic device to:

prompt a user to install a second application on the client electronic device,

prompt the user to authorize the first application to generate a two-factor authentication code for sign-in to the second application,

in response to receiving an indication from the user to install the second application and receiving an indication from the user to authorize the first application to generate the two-factor authentication code:

install the second application, and

generate the two-factor authentication code via the first application,

send a message via the first application to the second application, wherein the message comprises the two-factor authentication code,

launch the second application, and

automatically sign the user into the second application using the two-factor authentication code without prompting, by the second application, the user to provide the two-factor authentication code.

13. The system of claim 12 , wherein the one or more programming instructions that, when executed, cause the first application to generate the two-factor authentication code comprise one or more programming instructions that, when executed, cause the first application to use a private key associated with the first application to generate the two-factor authentication code.

14. The system of claim 12 , wherein the one or more programming instructions that, when executed, cause the first application to send the message to the second application comprise one or more programming instructions that, when executed, cause the first application to embed the two-factor authentication code in the message.

15. The system of claim 14 , wherein the one or more programming instructions that, when executed, cause the first application to embed the two-factor authentication code in the message comprise one or more programming instructions that, when executed, cause the first application to embed the two-factor authentication code in a marketing tag of the message.

16. The system of claim 12 , wherein the computer-readable storage medium further comprises one or more programming instructions that, when executed, cause the first application to encrypt at least a portion of the message using a private key associated with the first application.

17. The system of claim 16 , wherein the computer-readable storage medium further comprises one or more programming instructions that, when executed, cause the second application is configured to:

send the at least a portion of the message to a sign-in server; and

receive an indication from the sign-in server that the two-factor authentication code is valid.

18. The system of claim 12 , wherein the two-factor authentication code further comprises dynamic data associated with a clock or a counter of the client electronic device.

19. A system comprising:

one or more servers, the one or more servers configured to:

receive from a first application on a client electronic device, a two-factor authentication code for a user to sign-in to a second application:

receive, from the second application, a message indicating that the user confirms sign-in to the second application;

determine that the two-factor authentication code received from the first application is valid; and

send, to the second application, one or more instructions not to prompt the user for the two-factor authentication code.

20. The system of claim 19 , wherein the two-factor authentication code is associated with one or more of:

a time period during which the two-factor authentication code is valid;

a number of uses for which the two-factor authentication code is valid; or

an identifier of the second application for which the two-factor authentication code is valid.

Assignments (2)
CHANGE OF NAME Recorded May 11, 2018
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 046137/0126 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2017
From: LEWIS, JUSTIN; PRICE, THOMAS
To: GOOGLE INC.
Reel/Frame 043703/0451 →
Continuity (1)
Related Publication 20190095606A1 · Mar 28, 2019
Cited By (3)
US 12,250,207 US 12,621,291 US 12,683,793