ACQUISITION OF A DEVICE FINGERPRINT FROM AN INSTANCE OF A CLIENT APPLICATION

• US 20170310667A1
• Filed: 04/28/2015
• Published: 10/26/2017
• Est. Priority Date: 04/28/2015
• Status: Active Grant

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Correa, Victor Albuquerque, Marchezi, Humberto Cardoso, Bender, Roberto, Carrion, Joao
• Granted Patent: US 10,992,669 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/35 communicating wirelessly
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04W 12/065 Continuous authentication

Abstract

Examples disclosed herein relate to acquisition of a device fingerprint from an instance of a client application. Examples include association of a target device fingerprint, based on device context information, with a target user account in a remote service, and acquisition of an application device fingerprint from an unpaired instance of a client application.

Claims

1. An article comprising at least one non-transitory machine-readable storage medium comprising instructions executable by a processing resource of a remote service to:

acquire, from a web browser on a client computing device, login information for a target user account of the remote service;

acquire, from the web browser, device context information for the client computing device;

associate a target device fingerprint, based on the acquired device context information, with the target user account in the remote service;

acquire, from an unpaired instance of a client application, an application device fingerprint determined by the instance of the client application based on device context information for a computing device including the instance of the client application; and

in response to a determination that the application device fingerprint matches the target device fingerprint, pair the instance of the client application with the target user account based on the acquired application device fingerprint and without user input.

2. The article of claim 1, wherein the device context information acquired from the web browser is device context information that would be accessible to an instance of the client application when included on the client computing device.

3. The article of claim 1, wherein the instructions to pair comprise instructions to:

provide, to the instance of the client application, at least one piece of information associated with the target user account in the remote service to pair the instance of the client application with the target user account.

4. The article of claim 1, wherein the instructions to pair comprise instructions to:

pair the instance of the client application with the target user account without user input of any login information to the instance of the client application.

5. The article of claim 1, wherein the instructions to pair comprise instructions to:

in response to a determination that the application device fingerprint does not match any of a plurality of device fingerprints associated with user accounts of the remote service, provide, to the instance of the client application, information to cause the instance of the client application to display a prompt for input of login information for the remote service via the client computing device.

6. The article of claim 1, wherein the instructions to pair comprise instructions to:

compare the application device fingerprint to device fingerprints associated with respective user accounts of the remote service, and

wherein the instance of the client application is an instance of a client application for the remote service.

7. A system to at least partially implement a remote service, the system comprising:

a login engine to log in a target user account of the remote service based on login information acquired from a web browser on a client computing device;

an Information engine to acquire, from the web browser, device context information for the client computing device;

an associate engine to associate a target device fingerprint, based on the acquired device context information, with the logged in target user account in the remote service;

an acquire engine to acquire, from an unpaired instance of a client application, an application device fingerprint determined by the instance of the client application based on device context information for a computing device including the instance of the client application;

a determine engine to determine whether the application device fingerprint matches any of a plurality of device fingerprints associated with respective user accounts of the remote service; and

a pair engine to, in response to a determination that the application device fingerprint matches the target device fingerprint, pair the instance of the client application with the target user account based on the acquired application device fingerprint and without user input.

8. The system of claim 7, wherein the device context information acquired from the web browser is device context information accessible to both the web browser of the client computing device and an instance of the client application when included on the client computing device.

9. The system of claim 7, further comprising:

a web page engine to provide, to the web browser, at least one web page to cause the web browser to collect, and provide to the remote service, device context information for the client computing device, in response to selection, via the web browser, of a link associated with downloading an instance of the client application for the remote service.

10. The system of claim 9, wherein, the web page engine is further to:

in response to successful generation of the target device fingerprint, cause the web page to initiate downloading of the instance of the client application by the client computing device.

11. The system of claim 7, wherein the pair engine is further to, in response to the determination that the application device fingerprint matches the target device fingerprint:

provide, to the instance of the client application, at least one piece of information associated with the target user account in the remote service to pair the instance of the client application with the target user account without user input of any login information to the instance of the client application via the client computing device.

12. The system of claim 7, wherein the pair engine is further to:

in response to a determination that the application device fingerprint does not match any of a plurality of device fingerprints associated with user accounts of the remote service, provide, to the instance of the client application, information to cause the instance of the client application to display a prompt to receive input of login information for the remote service via the client computing device.

13. A method comprising:

providing a web browser access to a target user account of a remote service based on account login information acquired from a web browser of a client computing device;

in response to selection of a link associated with downloading an instance of a client application via the web browser, providing to the web browser at least one web page to cause the web browser to collect, and provide to the remote service, device context information for the client computing device;

generating, with a processing resource of the remote service, a target device fingerprint based on the device context information for the client computing device provided to the remote service by the web browser;

associating the target device fingerprint with the logged in target user account in an account repository of the remote service;

acquiring, from an unpaired instance of the client application, an application device fingerprint determined by the instance of the client application based on device context information for a computing device including the instance of the client application; and

determining whether to pair the instance of the client application with the target user account, without user input, based on whether the application device fingerprint matches the target device fingerprint.

14. The method of claim 13, further comprising:

in response to a determination that the application device fingerprint matches the target device fingerprint, providing, to the instance of the client application, at least one piece of information associated with the target user account in the remote service to pair the instance of the client application with the target user account without user input of any login information to the instance of the client application via the client computing device.

15. The method of claim 13, further comprising:

in response to a determination that the application device fingerprint does not match any of a plurality of device fingerprints associated with user accounts of the remote service, providing, to the instance of the client application, information to cause the instance of the client application to display a prompt to receive input of login information for the remote service via the client computing device.