Hello All,
We are currently deploying the CyberArk SCIM integration with SailPoint IdentityIQ, and I would appreciate input on the recommended approach for managing privileged accounts (secondary IDs) through SailPoint
Current state: The end user raises a ServiceNow request for secondary ID creation, SailPoint provisions the ID in Active Directory, and the account is then added to CyberArk manually. I am looking to automate the final step via the SCIM integration.
I have outlined two candidate approaches below and would welcome any alternatives.
Option A: Discovery-driven onboarding
**1.** SailPoint AD connector creates the secondary ID per the defined naming convention
**2.** Account is placed in the designated OU
**3.** A CyberArk discovery rule is scoped to that OU
**4.** CyberArk scans, detects, and onboards the account automatically
**5.** SCIM is used to assign the primary user identity to the relevant safe group
Option B: Chained provisioning via the SailPoint PAM module
**1.** SailPoint triggers the AD connector to create the account
**2.** A custom workflow step pauses the pipeline to extract the newly created AD account details
**3.** SailPoint issues an outbound REST API call to the CyberArk account onboarding endpoint
Note: I have previously built full lifecycle automation for this use case at another client, though without the SailPoint integration in scope.
Any guidance on which approach scales better, or on pitfalls with either, would be much appreciated. Thanks in advance.