Skip to main content
MichelB
BeyondTrust Employee
BeyondTrust Employee
September 9, 2026

SailPoint IIQ: Pathfinder SCIM setup guide

  • September 9, 2026
  • 0 replies
  • 33 views

Context

 

While standalone BeyondTrust products including Password Safe, Endpoint Privilege Management (EPM) for Windows & Mac, and Privileged Remote Access (PRA) have a SCIM API, PathFinder provides a unified or global SCIM API that supports provisioning Users and Groups that can be consume by each individual products within PathFinder.

 

This guide is a complement to Documentation: SCIM provisioning  and covers SailPoint IdentityIQ or IIQ .

 

The first step is to create a SCIM token as the SCIM service account, and note the Org ID in the upper right corner.  The User must be Administrator in individual BT modules.

 

Create a new Application with Type = SCIM 2.0.

 

Replace {organization-id} in Url https://api.beyondtrust.io/api/{organization-id}/platform/auth/scim/v2 and provide the token. Test Connection should be successful.

 

Discover Schema attributes for account.  Click Preview to test.

 

group:  Discover Schema Attributes. Use Preview to test.

 

 

 

 

Provisioning Policy:  Create account form.

 

Script values are:

  • script:  identity.getAttribute("email");
  • script:  identity.getAttribute("email");
  • script:  identity.getAttribute("firstname");
  • script:  identity.getAttribute("lastname");
  • Value:  true

All String except Boolean for active.

 

Account Correlation: Use email for email and/or userName.

 

Create Account and Group Aggregation Tasks.

 

Change skipGrpUpdate to false using either /debug or via Application.

 

Note:  skipGrpUpdate is not visible in IIQ 8.1 Application panel, but may be visible in newer versions.

 

IMPORTANT:  With skipGrpUpdate set to default of true, IIQ attempts to PATCH /Users/{user_id} to user User groups, but this is silently ignored.  With false, it correctly sends a PATCH to /Groups/{group_id} to update members.

 

Testing

 

 

Task Results:  After running the Aggregation tasks, you should see 2 rows with Success.

 

 

Application:  Accounts and groups should be visible.

 

Entitlement Catalog:  Groups should be Requestable by default.

 

 

Manage User Access:  Requesting a Group for a user without an account.

 

The Request should show no error and Execution Status should be Verifying (waiting for aggregation).

 

The attributes should be included in Provisioning Plan.

 

At this point the user should be added to Pathfinder with the SCIM Group membership.