SailPoint

Overview

ID Dataweb integrates directly with SailPoint Identity Security Cloud to verify users' identities during onboarding, password reset, certification or access reviews. By using either the direct NERM (Non Employee Risk Management) integration or the powerful Atlas workflow capabilities, it is trivial to integrate ID Dataweb's low friction / high security threat detection and mitigation workflows into any use case. Whether stopping employee proxy fraud, ghost student fraud, or business partner fraud, an organization will protect its most valuable resources and information by combining ID Dataweb with SailPoint ISC.

Prerequisites

ID Dataweb

Active ID Dataweb service

Configured verification workflow (linked to credentials)

Client ID and Client Secret tied to that workflow

SailPoint

SailPoint with JML (Joiner-Mover-Leaver) workflow configured

Ability to configure workflow actions

Admin configuration access

Attribute mapping capability

Identity Proofing workflow action (if using NERM)

Configuration Steps

Step1. ID Dataweb Configuration
Configure verification workflow
Generate:
Client ID
Client Secret (linked to workflow)
Inputs
Verification workflow design
Required identity proofing methods
Outputs
Client ID
Client Secret

Step 2. SailPoint Configuration
Add Identity Proofing workflow action (if applicable)
Enter:
Client ID
Client Secret
Configure:
Proofing type label (optional)
Environment (if applicable)
Map user attributes for prefill
Inputs
Client credentials from ID Dataweb
User attribute mappings
Outputs
Configured workflow action
Trigger point for verification

Step 3. Verification Trigger
Verification is triggered as part of:
JML onboarding flow
Or configured workflow action
Trigger depends on SailPoint workflow configuration

Step 4. Callback / Result Handling
ID Dataweb sends results via WorkflowArgs webhook
SailPoint receives:
Verification result
Decision outcome

Testing

Create or trigger user in SailPoint JML

Confirm:

Verification email is generated and sent

User completes verification flow

Validate:

Result returned to SailPoint

Policy decision executed:

APPROVE → provisioning continues

DENY → provisioning halted / exception triggered

Troubleshooting

Identity Proofing action not added to workflow

Workflow not configured to trigger verification

Verification step placed incorrectly in workflow

Resolutions

Confirm Identity Proofing action is included in the SailPoint workflow

Validate the workflow step is triggered during the correct event (e.g., joiner)

Ensure verification occurs before provisioning step

Re-run workflow with test user to confirm execution order

User Attribute Issues

Attributes not mapped

Missing required user fields

Incorrect attribute formatting

Resolutions

Verify required attributes (e.g., name, email, phone) are mapped in SailPoint

Confirm attribute values are populated for the test user

Check formatting matches expected input (e.g., valid phone/email format)

Update mappings and re-run test

User Experience Issues

User does not receive verification email

Verification link not working or expired

Resolutions

Confirm correct email attribute is mapped in SailPoint

Validate email exists for the user

Check spam/junk folders

Re-trigger workflow to generate a new verification link

Ensure verification session has not expired