Abstract: A method for facilitating application authentication bypass based on proximate with time using device authentication is disclosed. The method includes receiving a request from a user to access an application on a user device, the request including an application authentication request; accessing the user device via a device application programming interface; retrieving, via the device application programming interface, device authentication data, the device authentication data including a timeline of successful device authentications; determining whether the device authentication data is within a predetermined threshold; authenticating the request by using the device authentication data when the device authentication data is within the predetermined threshold; and permitting access to the application based on a result of the authenticating.

Abstract: A method for extended authentication sessions on an electronic device may include an authentication service computer program executed by an authentication service electronic device: receiving a customer identifier for a customer and a unique identifier for a mobile electronic device; authenticating the customer based on the customer identifier and the unique identifier for the mobile electronic device; setting a device cookie that is specific to the mobile electronic device on the mobile electronic device; and providing the device cookie and a client secret to an OAuth services backend, wherein the OAuth services backend validates the customer identifier and client secret and generates a first token and a second token, the first token having an expiration that is shorter than that of the second token. The mobile electronic device is configured to receive and store the first token and the second token.

Abstract: Password-less authentication and login onto an application are disclosed. A processor extracts Digital Driver's License (DDL) data from a user's computing device; extracts the DDL data of the user from an external database (i.e., DMV); validates the DDL data by comparing with the DDL data from the external database; creates, in response to validating, a DDL secret private key; allows successful registration of the computing device to utilize DDL data for login; and stores the DDL secret private key onto an internal database and a secured environment of the computing device. At login request by the user, when the processor determines that the computing device is successfully registered, it validates the DDL secret private key by comparing with data from the internal database; creates a new DDL secret private key and updates the internal database and the secured environment with the new DDL secret private key for subsequent login.