Currently, I have SailPoint IIQ integrated with CyberArk PAM (SCIM Connector), and I have successfully performed aggregation. User data has already been retrieved.
Now, I would like to create user accounts and enable/disable CyberArk users through SailPoint. How can I do this?
Are you managing your CyberArk users locally. You can use the Post method available using the endpoint <Base_URL>/scim/v2/Users to create users and there is also a put method that allows updating users. More details available from CyberArk below.
If existing CyberArk connector blocking for some reason, Go for Webservice type connector. you will get Create Operations. Or else Custom Business process you can create and attach to Joiner process if it is a part of the Birth right…
@benutop55 as you have configured it as SCIM connector (or for Webservices Connector), please test out the APIs via Postman. This’ll tell you how APi works and what is request and response format.
Now, as you already have sCIM, it should internally make POST call to /scim/Users api to create account in CyberArk. You will need a Provisoning Plan which you can generate programmatically or you can take available existing routes via Manage Accounts, Manage Users Access (while submitted entitlement or roles), etc. This’ll trigger a create provisioning to Cyberark. Give it a try and see if it works.
Note: Found a fix?Help the community by marking the comment as solution. Feel free to react(,, etc.)with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
The most likely cause of the error as it is missing userType: Vault and the enterprise extension organization field. Please share your exact Postman request body, to suggest. can you share full request body and headers??
Your request body is wrapped inside a "userData": {} object: The CyberArk SCIM server does NOT accept a userData wrapper. It expects the fields at the root level following the SCIM 2.0 standard schema. That’s exactly why line 725 throws user data is required — the deserializer finds no valid SCIMUserResource object at the root, so it treats the body as empty.
Disabling external ad user doesn’t work seems to be a different issue, can you open a different thread for the same?? and please explain the use case as well