Fingerprint Connector
Fingerprint (previously FingerprintJS) is a device detection platform that provides valuable information about the device. Fingerprint's key feature is its ability to generate a unique ID, often called a "device fingerprint", and permanently associate it with each device. Once the service identifies the device, it can provide crucial geoinformation, bot detection, VPN detection, and more. This connector provides the ability to automate threat detection in an authentication process with Descope and scare off unwelcome visitors to a platform.
Setting Up The Fingerprint Connector
To integrate the Fingerprint connector, follow the steps below:
Navigate to Connector
- Navigate to the Descope Connectors page.
- Search or find the Fingerprint connector and select it.
Connector Setup
Set up the necessary inputs:
- Connector name: Assign a custom name for your connector, especially useful when using multiple connectors originating from the same template.
- (Optional) Connector description: A brief description of your connector's purpose.
Proceed by providing the connector Public API Key
and Secret API Key
, which are copied from Fingerprint's configuration page, the details for these keys can be found here:
- Login to
https://fingerprint.com/
. - Go to "App Settings".
- Go to the API Keys tab.
CloudFlare Integration
When a Descope flow uses the Fingerprint connector, it calls Fingerprint to establish or get a unique device ID. Toggle CloudFlare integration to configure Fingerprint's API calls to match your domain.
Integration with CloudFlare needs to be ready on Fingerprint read more.
- Cloudflare integration Script URL: The Cloudflare integration Script URL (format example -
https://api.company.com/fXj8gt3x8VulJBnb/w78aRZnnDZ3Aqw0v
). - Cloudflare integration Endpoint URL: The Cloudflare integration Endpoint URL (format example -
https://api.company.com/fXj8gt3x8VclJBna/x96Emn69oZwcd7I4
).
Note
Make sure that the URLs are accessible.
Test & Save
The "Test" button allows you to test the configuration, ensuring it was successfully configured before using it in a flow. Note that it may take up to a minute for a new private key created in Fingerprint to work. Until then, you may face a failure response.
- Conclude the setup process by selecting
Create
.
Implementing the Fingerprint Connector
Select or Create a Flow
Access your Dashboard and go to flows. You can choose an existing flow or generate a new one.
Integration
Click on the blue plus sign inside the flow builder and choose "Connector". You should be able to see the new connector actions as shown below:
Warning
Since fingerprinting is completed within the browser, the connector steps need to be added after at least one "screen" component has been displayed to the user.
Examples
Integrating one of the connector actions inside a flow can be used in various scenarios. Here is an example of a flow that utilizes the result as follows:
The flow checks whether the user returned from a non-VPN origin and continues logging him in.
This example uses the context key - connectors.fingerprint_getEvent.products.data.vpn.data.result
To read about the possible results from Fingerprint click here.