ConnectorsSetup GuidesFraud

AbuseIPDB Connector

Descope's Abuse IPDB connector helps you establish a reputation-based score on a user's originating IP address, thus aiding in the detection of fraudulent or hacker-associated connections to your system. The connector offers you a result varying from 0 to 100, where 0 means safe , and 100 very likely to take part in such activity.

Note

The rate limit for the AbuseIPDB connector relies on the AbuseIPDB platform and its licensing, and it is up to the customer to consider the pricing.

Setting Up The AbuseIPDB Connector

To integrate the AbuseIPDB connector, follow the steps below:

1. Navigate to Connector

  • Visit your Descope dashboard.
  • Follow: Dashboard -> Connectors.
  • Choose “AbuseIPDB”.

2. Connector Setup

Ready your AbuseIPDB private API access token for integration.

abuseipdb key generation

abuseipdb connector setup

Proceed with 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.
  • API Key: The AbuseIPDB API access token generated for the Descope service.

3. Test & Save

  • Validate your configuration by clicking the Test button and observing the Test Results section.
  • Conclude the setup process by selecting Create.

Implementing the AbuseIPDB Connector in Your Flow

1. Select or Create a Flow

  • Access your Dashboard -> Flows.
  • Opt for an existing flow or generate a new one.

2. Integration

Click on the blue plus sign inside the flow builder and choose "Connector". You should be able to see the new connector action as shown below:

abuseipdb connector flow component

Integrating that connector action inside a flow can be used in various scenarios. Here is an example of a flow that utilizes the result as follows:

abuseipdb connector flow component

abuseipdb connector flow condition

The flow checks whether the IP Reputation came back above 50 (This integer can be altered at your wish) and, if so, asks the user for a second-factor authentication.

Was this helpful?

On this page