IP Library Granted Patent US 12,113,792
Granted Patent B2
US 12,113,792 · App. 17/537,064 · Granted Oct 8, 2024

Authenticator centralization and protection including selection of authenticator type based on authentication policy

Inventors: Andrew Robert Rolfe (Deerfield, IL); Alan Dundas (Los Altos Hills, CA); Gregory Slowiak (Cary, IL)
Assignee: Prove Identity, Inc.
H04L63/0884H04L63/06H04L63/0861H04L63/0853H04L2463/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 12,113,792
App. No.
17/537,064
Granted
Oct 8, 2024
Kind
B2
Abstract

Provided is a method for authenticating a user communicating with an enterprise via a network. The method includes receiving, via the network, authenticators for a user from a first user device associated with the user, and storing the received authenticators. A first authenticator from the stored authenticators is selected to be used for authenticating the user based on an authentication policy received from the enterprise. An authentication request is transmitted to a user device requesting the first authenticator and the user is authentication by comparing the received authenticator with the stored first authenticator.

Claims (55)

1. An authentication server to authenticate a user in communication with an enterprise server, comprising:

a memory of the authentication server to store a first plurality of user credentials received from a user device associated with the user, wherein the first plurality of user credentials:

comprise one or more biometric-type parameters, one or more possession-type parameters, or one or more knowledge base-type parameters, or any combination there of, and

do not comprise an identification of the user; and

a processor of the authentication server coupled to the memory of the authentication server to:

receive, by the authentication server from the enterprise server, a request to authenticate the user, wherein the request:

does not identify the user, and

does not include an identification of which at least one of the first plurality of user credentials is to be used to authenticate the user;

obtain, by the authentication server from the user device, an authentication parameter, wherein:

the authentication parameter is based, at least in part, on an enterprise policy of the enterprise server,

the authentication parameter is derived, at least in part, from a device ID,

the device ID is bound to hardware of the user device, and

the device ID comprises a parameter that uniquely identifies the user device; and

responsive to selecting, by the authentication server, for comparison a one or more of the first plurality of user credentials based, at least in part, on the enterprise policy, authenticate, by the authentication server, the user, at least in part, via a comparison of the obtained authentication parameter with the one or more of the first plurality of user credentials.

2. The authentication server of claim 1 , wherein the device ID is not clone-able.

3. The authentication server of claim 1 , wherein the device ID is immutable.

4. The authentication server of claim 1 , wherein the device ID is obtained from a card inserted into the user device.

5. The authentication server of claim 1 , wherein the processor is additionally to generate a relationship identifier to associate the user device with an account identifier stored on, or at least accessible to, the enterprise server.

6. The authentication server of claim 1 , wherein the processor is additionally to wirelessly transmit a one-time code to the user device, the one-time code to link the user device to the enterprise server.

7. The authentication server of claim 1 , wherein the processor is additionally to determine the one or more of the first plurality of user credentials from the first plurality of user credentials to be used to authenticate the user based on the enterprise policy to establish a type of user credential to be used to authenticate the user.

8. The authentication server of claim 7 , wherein the processor is additionally to transmit the request to the user device, for the authentication parameter.

9. The authentication server of claim 7 , wherein the enterprise policy is to establish the type of user credential to be used to authenticate the user.

10. A method for an authentication server to authenticate a user, comprising:

storing, in at least one memory of the authentication server, a first plurality of user credentials obtained by the authentication server from a user device associated with the user, wherein the first plurality of user credentials;

comprise one or more biometric-type parameters, one or more possession-type parameters, or one or more knowledge base-type parameters, or any combination thereof, and

do not comprise an identification of the user;

utilizing a processor coupled to the at least one memory:

receiving, by the authentication server from an enterprise server, a request to authenticate the user, wherein the request:

does not identify the user, and

does not include an identification of which at least one of the first plurality of user credentials is to be used to authenticate the user;

obtaining, by the authentication server from the user device, an authentication parameter, wherein:

the authentication parameter is based, at least in part, on an enterprise policy on the enterprise server,

the authentication parameter is derived, at least in part, from a device ID,

the device ID is bound to hardware of the user device, and

the device ID comprises a parameter that uniquely identifies the user device; and

responsive to selecting, by the authentication server, for comparison a one or more of the first plurality of user credentials based, at least in part, on the enterprise policy, authenticating, by the authentication server, the user, at least in part, via a comparison of the obtained authentication parameter with the one or more of the first plurality of user credentials.

11. The method of claim 10 , wherein the device ID is not cloneable.

12. The method of claim 10 , wherein the device ID is immutable.

13. The method of claim 10 , wherein the device ID is obtained from a card inserted into the user device.

14. An article comprising:

a non-transitory storage medium, having instructions encoded thereon, which, when executed by an authentication server having at least one processor coupled to at least one memory device, are to:

store, via the at least one memory device, a first plurality of user credentials received from a user device associated with a user, wherein the first plurality of user credentials:

comprise one or more biometric-type parameters, one or more possession-type parameters, or one or more knowledge base-type parameters, or any combination thereof, and

do not comprise identity related information of the user;

receive, by the authentication server from the enterprise server, a request to authenticate the user, wherein the request:

does not identify the user, and

does not include an identification of which at least one of the first plurality of user credentials is to be used to authenticate the user;

obtain, by the authentication server from the user device, an authentication parameter, wherein:

the authentication parameter is based, at least in part, on an enterprise policy on the enterprises server,

the authentication parameter is derived, at least in part, from a device ID,

the device ID is bound to hardware of the user device, and the device ID comprises a parameter that uniquely identifies the user device; and to

responsive to selecting, by the authentication server, for comparison a one or more of the first plurality of user credentials based, at least in part, on the enterprise policy, authenticate, by the authentication server, the user at least in part via a comparison of the obtained authentication parameter with the one or more of the first plurality of user credentials.

15. The article of claim 14 , wherein the device ID is not cloneable.

16. The article of claim 14 , wherein the device ID is immutable.

17. The article of claim 14 , wherein the device ID is to be obtained from a card for insertion into the user device.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2022
From: ROLFE, ANDREW ROBERT; DUNDAS, ALAN; SLOWIAK, GREGORY
To: AUTHENTIFY, INC.
Reel/Frame 061338/0549 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2022
From: AUTHENTIFY, INC.
To: EARLY WARNING SERVICES, LLC
Reel/Frame 061338/0562 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 6, 2022
From: EARLY WARNING SERVICES, LLC
To: PAYFONE, INC.
Reel/Frame 061338/0638 →
CHANGE OF NAME Recorded Oct 6, 2022
From: PAYFONE, INC.
To: PROVE IDENTITY, INC.
Reel/Frame 061621/0483 →
Continuity (6)
Continuation 16817157 · Mar 12, 2020
Continuation 16268243 · Feb 5, 2019
Continuation 16115281 · Aug 28, 2018
Continuation 15269287 · Sep 19, 2016
Provisional Application 62221435 · Sep 21, 2015
Related Publication 20220086152A1 · Mar 17, 2022