In this article, we will learn how to use the Device Fingerprint API guide to identify the user’s device or browser and provide a customized experience.
Device Fingerprint API guide (also known as canvas fingerprinting, browser fingerprinting, machine fingerprinting or device recognition) is a method used to identify devices and/or browsers based on their unique configuration. Unlike web cookies that are stored on the client side, fingerprints must be collected server-side to maintain security and accuracy.
Device Fingerprint API Guide: Implementation & Benefits
Fingerprinting is a key part of many fraud prevention systems and provides a useful means of improving the user experience, reducing friction, and increasing conversions. However, as the landscape continues to evolve due to increased privacy measures and technology advancements, it will be important to supplement fingerprinting with additional techniques such as behavioral profiling and feature aggregation in order to improve accuracy and maximize the benefits of this approach.
During the identification process, Oracle Adaptive Access Manager gathers attributes about the user’s device to construct the fingerprint. These attributes include the following:
The fingerprinting data is then communicated to the application using a secure cookie. The cookie is a one-time token that is replaced the next time the user fingerprints their device. The cookie is also encrypted and can only be read by the application that created it.
The final step is to determine a recommended action to take against the device or browser identified by the fingerprinting data. This could be to ALLOW the device or browser profile, BLOCK the profile if it is known to be bad or unauthenticated, or REQUIRE additional one-time passcodes (OTPs) for multi-factor authentication.…