To produce a risk assessment for a sign-on event, FraudForce requires information about the user's device. You can collect this information using the iovation IdP Adapter or by attaching the scripts to another adapter in your sign-on flow.
Captured by the iovation IdP Adapter
The iovation IdP Adapter inserts a page into the sign-on flow that shows a spinner animation while the device profiling process runs. The page typically appears after the first-factor authentication page, as determined by your authentication policy.
This method adds a short wait time to the sign-on process.
Captured by a previous adapter
Scripts are added to a page that is presented by another adapter in your authentication policy. This page must appear earlier in the sign-on flow than the iovation IdP Adapter, such as the first-factor authentication page.
This method reduces wait times by allowing the iovation JavaScript to prepare the device profile blackbox while a user types in their credentials.
The iovation IdP Adapter is still responsible for sending data back to the iovation API, so the script uses HTTP cookies to pass the device profile blackbox from the first-factor authentication page to the iovation IdP Adapter.
- The page appears before the iovation IdP Adapter in the sign-on flow.
- The page is hosted in the same domain as your PingFederate server. This is allows HTTP cookies to be used to pass the blackbox to the iovation IdP Adapter. You may be able to work around this requirement by consolidating your domains with a reverse proxy server.
- You have access to add JavaScript to the page HTML code.
For instructions, see Adding device profiling to an authentication page after you finish Deploying the integration files.