How To Setup Device Fingerprinting JavaScript Pixel
The fingerprinting process begins by creating a pixel image that’s unique to each device. The pixel is then hashed, and the result is a unique digital signature for each device. This unique fingerprint is used to identify the device for future events. The fingerprint is then submitted to InAuth using a submission ID from the Conversations API.
A setup device fingerprinting JavaScript pixel is comprised of many attributes, but the most important are the operating system, screen resolution and color depth, installed fonts, and hardware properties (like the number of CPU cores). Castle collects these characteristics through our mobile SDKs for web and native mobile apps.
How to Setup Device Fingerprinting JavaScript Pixel
Once these characteristics are collected, they’re combined into a device fingerprint and sent to the OAAM server during login. Oracle Adaptive Access Manager uses this fingerprint to evaluate the probability that a user is the same one that’s already been identified.
Aside from the device fingerprint, OAAM utilizes dozens of other attributes for robust security, including the user’s location and browser. Combined, these factors help to provide the most accurate and secure method of recognizing and authenticating users.