If you are using the PingFederate authentication API and want to avoid using HTTP cookies, modify your application to collect the device profile and send it to the authentication API.
Adding device profiling to an authentication API-based application using the PingOne Risk (Signals) SDK and integration kit 1.3.1
Use the following instructions to add device profiling to a web application using the PingOne Risk (Signals) SDK. For more information about the authentication API, see Authentication API in the PingFederate documentation or PingOne Risk Native SDKs in the PingOne Native SDK documentation.
PingOne Risk Integration Kit version 1.3.1 must be deployed before any changes can be made on the HTML side. SDK version 5.2.1 or later requires adapter version 1.3.1 or later.
Adding device profiling to an authentication API-based application using the PingOne Risk (Signals) SDK and integration kit 1.3 or earlier
Use the following instructions to add device profiling to a web application using the PingOne Risk (Signals) SDK. For more information about the authentication API, see Authentication API in the PingFederate documentation or PingOne Risk Native SDKs in the PingOne Native SDK documentation.
Adding device profiling to an Authentication API-based application using Fingerprint JS
Use the following instructions to add device profiling to a web application using Fingerprint JS. For more information about the authentication API, see Authentication API in the PingFederate documentation.
The PingOne Risk (Signals) SDK is the preferred way to get device profiling and is recommended for use in the PingOne Risk Integration Kit 1.3 and later.