Fingerprint Response node
The Fingerprint Response node is used in the zero-trust model to fetch the fingerprint and server-side confidence score.
Compatibility
Product | Compatible? |
---|---|
Advanced Identity Cloud |
Yes |
PingAM (self-managed) |
Yes |
Ping Identity Platform (self-managed) |
Yes |
[1]
Inputs
Attribute name | Description | Source |
---|---|---|
deviceRequestId |
Mandatory variable to identify the authentication request. |
Value is stored in the shared state by the Fingerprint Profiler node. |
Configuration
The configurable properties for this node are:
Property | Usage |
---|---|
Secret API Key |
Secret API key configured on the Fingerprint site. |
Events API URL |
Path to an events API. The default is https://eu.api.fpjs.io/events/. Other options include:
|
Shared State VisitorID |
Name of the shared state variable to store the fingerprint. This should be the same as in the Fingerprint Profile node. |
Get full response payload |
Disabled by default. Enable if you want to store the full fingerprint API response in shared state. |
Shared State Response |
Name of the variable to store the fingerprint API response. Used only when |
Outputs
This node adds the following in the shared store:
Attribute | Description |
---|---|
deviceFingerPrint |
Unique signature of the browser (fingerprint). The name of this variable is configured using the Shared State VisitorID property. |
deviceConfidenceScore |
Confidence level for the verified fingerprint. |
payload (optional) |
This optional attribute contains the full API response from the Fingerprint site. The name of this variable is configured using the Share State Response configuration property. |
If an error occurs, error messages with the keys [Marketplace]Exception
and
[Marketplace]StackTrace
are output to the shared state.
Outcomes
Success
-
The response node completed successfully.
Error
-
There was a problem with the node. Check all the settings and the error messages in shared state.
fingerprint-1.0.13.jar
file to the web-container/webapps/openam/WEB-INF/lib
directory where AM is deployed, and then restart the web container to pick up the new nodes.