US 12,113,792 B2
Authenticator centralization and protection including selection of authenticator type based on authentication policy
Andrew Robert Rolfe, Deerfield, IL (US); Alan Dundas, Los Altos Hills, CA (US); and Gregory Slowiak, Cary, IL (US)
Assigned to Prove Identity, Inc., New York, NY (US)
Filed by PROVE IDENTITY, INC., New York, NY (US)
Filed on Nov. 29, 2021, as Appl. No. 17/537,064.
Application 17/537,064 is a continuation of application No. 16/817,157, filed on Mar. 12, 2020, granted, now 11,218,480.
Application 16/817,157 is a continuation of application No. 16/268,243, filed on Feb. 5, 2019, granted, now 10,616,222, issued on Apr. 7, 2020.
Application 16/268,243 is a continuation of application No. 16/115,281, filed on Aug. 28, 2018, granted, now 10,250,602, issued on Apr. 2, 2019.
Application 16/115,281 is a continuation of application No. 15/269,287, filed on Sep. 19, 2016, granted, now 10,084,782, issued on Sep. 25, 2018.
Claims priority of provisional application 62/221,435, filed on Sep. 21, 2015.
Prior Publication US 2022/0086152 A1, Mar. 17, 2022
Int. Cl. H04L 29/06 (2006.01); H04L 9/08 (2006.01); H04L 9/40 (2022.01)
CPC H04L 63/0884 (2013.01) [H04L 63/06 (2013.01); H04L 63/0861 (2013.01); H04L 63/0853 (2013.01); H04L 2463/082 (2013.01)] 17 Claims
OG exemplary drawing
 
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.