Systems and methods for authenticating a user based on a computing device
View Patent ↗A system and/or method may be provided to silently authenticate a user. An example method of silently authenticating a user includes receiving a set of device characteristics from a user device and identifying, based on the set of device characteristics, the user device. The method also includes determining whether to trust the user device and determining whether the user device is associated with a user that was previously authenticated. The method further includes in response to determining to trust the user device and that the user device is associated with the user that was previously authenticated, authenticating the user based on the previous authentication.
1. An authentication system, comprising:
a non-transitory memory; and
one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising:
receiving, from a software development kit (SDK) that is operating as a component of a first mobile application that is executing on a user device and that is also provided as a component of a second mobile application that is available on the user device:
user credentials; and
a plurality of device characteristics that describe at least one operational feature specific to the user device and at least one contextual feature specific to the user device;
authenticating access to the first mobile application executing on the user device using the user credentials;
determining, in response to authenticating access to the first mobile application, that the plurality of device characteristics that were received from the SDK operating as the component of the first mobile application match a plurality of previously stored device characteristics that are stored in a database and that were previously received from the SDK that is provided as the component of one of the first mobile application and the second mobile application;
associating, in response to both authenticating access to the first mobile application and determining that the plurality of device characteristics that were received from the SDK operating as the component of the first mobile application match a plurality of previously stored device characteristics, a previously authenticated user with the user device in the database;
receiving, from the SDK that is operating as the component of the second mobile application executing on the user device, the plurality of device characteristics from the user device that describe the at least one operational feature specific to the user device and the at least one contextual feature specific to the user device; and
authenticating, without receiving user credentials associated with the second mobile application, access to the second mobile application based on:
the plurality of device characteristics that were received from the SDK operating as the component of the second mobile application matching the plurality of previously stored device characteristics in the database; and
the user device being associated with a previously authenticated user.
2. The system of claim 1 , wherein the operations further comprise:
providing, to the user device in response to authenticating access to the first mobile application, an authentication token, wherein the SDK that is operating as the component of the second mobile application provides the authentication token along with the plurality of device characteristics, and the authenticated access to the second mobile application is also based on the authentication token.
3. The system of claim 1 , wherein the SDK provided as the component of one of the first mobile application and the second mobile application is configured to extract the plurality of previously stored device characteristics from the user device in response to the installation of the one of the first mobile application and the second mobile application on the user device, and provide the plurality of previously stored device characteristics for storage in the database.
4. The system of claim 1 , wherein the SDK provided as the component of the first mobile application and the second mobile application is executable on the user device by one or more entities corresponding to the first mobile application or the second mobile application.
5. The system of claim 1 , wherein the operations further comprise:
extracting, using the SDK provided as the component of the first mobile application and in response to selection of the first mobile application, the plurality of previously stored device characteristics from the user device, wherein the SDK provided as the component of the first mobile application is configured to provide the plurality of previously stored device characteristics for storage in the database.
6. The system of claim 1 , wherein the operations further comprise:
extracting, using the SDK provided as the component of the second mobile application and in response to selection of the second mobile application, the plurality of previously stored device characteristics from the user device, wherein the SDK provided as the component of the second mobile application is configured to provide the plurality of previously stored device characteristics for storage in the database.
7. The system of claim 1 , wherein the user device is a mobile device.
8. The system of claim 1 , wherein the at least one operational feature the plurality of previously stored device characteristics includes an operating system identifier and a Media Access Control (MAC) address utilized by the user device, and the at least one contextual feature in the plurality of device characteristics includes a location of the user device.
9. A method of silently authenticating a user, comprising:
receiving, by a system provider device from a software development kit (SDK) that is operating as a component of a first mobile application that is executing on a user device, and that is also provided as a component of a second mobile application that is available on the user device:
user credentials; and
a plurality of device characteristics that describe at least one operational feature specific to the user device and at least one contextual feature specific to the user device;
authenticating, by the system provider device, access to the first mobile application executing on the user device using the user credentials;
determining, by the system provider device in response to authenticating access to the first mobile application, that the plurality of device characteristics that were received from the SDK operating as the component of the first mobile application match a plurality of previously stored device characteristics that are stored in a database and that were previously received from the SDK that is provided as the component of one of the first mobile application and the second mobile application; and
associating, by the system provider device in response to both authenticating access to the first mobile application and determining that the plurality of device characteristics that were received from the SDK operating as the component of the first mobile application match a plurality of previously stored device characteristics, a previously authenticated user with the user device in the database;
receiving, by the system provider device from the SDK that is operating as the component of the second mobile application executing on the user device, the plurality of device characteristics from the user device that describe the at least one operational feature specific to the user device and the at least one contextual feature specific to the user device; and
authenticating without receiving user credentials associated with the second mobile application, access to the second mobile application based on:
the plurality of device characteristics that were received from the SDK operating as the component of the second mobile application matching the plurality of previously stored device characteristics in the database; and
the user device being associated with a previously authenticated user.
10. The method of claim 9 , further including:
receiving, by the system provider device, the plurality of previously stored device characteristics from the SDK provided as the component of one of the first mobile application and the second mobile application in response to the installation of the one of the first mobile application and the second mobile application on the user device.
11. The method of claim 9 , further including:
receiving, by the system provider device, the plurality of previously stored device characteristics from the SDK provided as the component of the first mobile application in response to the selection of the first mobile application on the user device.
12. The method of claim 9 , further including:
receiving, by the system provider device, the plurality of previously stored device characteristics from the SDK provided as the component of the second mobile application in response to the selection of the second mobile application on the user device.
13. The method of claim 9 , wherein the at least one operational feature in the plurality of previously stored device characteristics include an operating system identifier and a Media Access Control (MAC) address utilized by the user device, and the at least one contextual feature in the plurality of device characteristics includes a location of the user device.
14. The method of claim 9 , further including:
providing, by the system provider device in response to authenticating access to the first mobile application,
wherein the SDK that is operating as the component of the second mobile application provides the authentication token along with the plurality of device characteristics, and the authenticated access to the second mobile application is also based on the authentication token.
15. A non-transitory machine-readable medium comprising a plurality of machine-readable instructions executable to cause a machine to perform operations comprising:
receiving, from a software development kit (SDK) that is operating as a component of a first mobile application that is executing on a user device and that is also provided as a component of a second mobile applications that is available on the user device;
user credentials; and
a plurality of device characteristics that describe at least one operational feature specific to the user device and at least one contextual feature specific to the user device;
authenticating access to the first mobile application executing on the user device using the user credentials;
determining, in response to authenticating access to the first mobile application, that the plurality of device characteristics that were received from the SDK operating as the component of the first mobile application match a plurality of previously stored device characteristics that are stored in a database and that were previously received from the SDK that is provided as the component of one of the first mobile application and the second mobile application;
associating, in response to both authenticating access to the first mobile application and determining that the plurality of device characteristics that were received from the SDK operating as the component of the first mobile application match a plurality of previously stored device characteristics, a previously authenticated user with the user device in the database;
receiving, from the SDK that is operating as the component of the second mobile application executing on the user device, the plurality of device characteristics from the user device that describe the at least one operational feature specific to the user device and the at least one contextual feature specific to the user device; and
authenticating, without receiving user credentials associated with the second mobile application, access to the second mobile application based on:
the plurality set of device characteristics that were received from the SDK operating as the component of the second mobile application matching the plurality of previously stored device characteristics in the database; and
the user device being associated with a previously authenticated user.
16. The non-transitory machine-readable medium of claim 15 , wherein the at least one operational feature in the plurality of previously stored device characteristics includes an operating system identifier and a Media Access Control (MAC) address utilized by the user device, and the at least one contextual feature in the plurality of device characteristics includes a last known location of the user device.
17. The non-transitory machine-readable medium of claim 15 , wherein the operations further include:
receiving a request from the user device to opt into silent authentication, wherein silent authentication enables the user to be authenticated access to the second mobile application based only on:
the plurality of device characteristics that were received from the SDK operating as the component of the second mobile application matching the plurality of previously stored device characteristics in the database; and
the user device being associated with a previously authenticated user.
18. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:
wherein the SDK provided as the component of the first mobile application and the second mobile application is executable on the user device by one or more entities corresponding to the first mobile application or the second mobile application.
19. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:
extracting, using the SDK provided as the component of the first mobile application and in response to selection of the second mobile application, the plurality of previously stored device characteristics from the user device, wherein the SDK provided as the component of the first mobile application is configured to provide the plurality of previously stored device characteristics for storage in the database.
20. The non-transitory machine-readable medium of claim 15 , the operations further comprise:
extracting, using the SDK provided as the component of the second mobile application and in response to a selection of the second mobile application, the plurality of previously stored device characteristics from the user device, wherein the SDK provided as the component of the second mobile application is configured to provide the plurality of previously stored device characteristics for storage in the database.