- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
02-23-2024 04:51 AM
We are setting up the CyberArk Identity SCIM for integration with SailPoint IdentityNow (IDN). There is an error from IDN when it aggregates users, because there is no sub-attributes under customDataAttributes on CustomData schema (urn:scim:schemas:extension:custom:2.0).
I tried to tackle this error by adding an additional attribute for Users on CyberArk Identity and assign value to that custom attribute to some users. However, there is no change on CustomData schema after adding a custom attribute (checked from /Schemas endpoint), but the value custom attribute is shown in the users (checked from /Users endpoint). As IDN checks the sub-attributes of the schema via /Schemas endpoint, the error still persists.
I am wondering whether this behaviour is expected or if there is any bug on CyberArk Identity's SCIM.
This is how the CustomData schema looks like, before and after adding an additional attribute (from /Schemas endpoint):
{
"name": "CustomData",
"description": "Custom Data for User",
"attributes": [
{
"name": "customDataAttributes",
"type": "complex",
"multiValued": false,
"description": "Custom Attributes created in Identity.",
"required": false,
"mutability": "readWrite",
"returned": "default",
"uniqueness": "none"
}
],
"id": "urn:scim:schemas:extension:custom:2.0",
"meta": {
"resourceType": "Schema",
"created": "2024-02-23T12:54:22.856424Z",
"lastModified": "2024-02-23T12:54:22.856424Z",
"location": "https://<censored>.id.cyberark.cloud/Scim/v2/Schemas/urn:scim:schemas:extension:custom:2.0"
}
}And this is the user entry looks like after adding an additional attribute value (from /Users endpoint):
{
"name": {
"formatted": "<censored>"
},
"displayName": "<censored>",
"active": true,
"emails": [
{
"type": "work",
"primary": true,
"value": "<censored>"
}
],
"groups": [
{
"display": "CS Admin",
"value": "<censored>",
"$ref": "https://<censored>.id.cyberark.cloud/Scim/v2/Groups/<censored>"
}
],
"userName": "<censored>",
"schemas": [
"urn:ietf:params:scim:schemas:core:2.0:User",
"urn:scim:schemas:extension:custom:2.0"
],
"id": "<censored>",
"meta": {
"resourceType": "User",
"created": "2024-02-23T12:45:52.8825145Z",
"lastModified": "2024-02-23T12:45:52.8825145Z",
"location": "https://<censored>.id.cyberark.cloud/Scim/v2/Users/<censored>"
},
"urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
"organization": "Acme"
},
"urn:scim:schemas:extension:custom:2.0": {
"Job_Title": "Developer"
}
}Thank you
02-29-2024 06:41 AM
Samuel,
This looks like a bug. Definitely submit this to Support so we can start working on it.
John
02-29-2024 05:24 AM
@Samuel Natalius, since you haven't gotten a response from the community on your question, I would suggest submitting a Support ticket.
02-29-2024 06:41 AM
Samuel,
This looks like a bug. Definitely submit this to Support so we can start working on it.
John
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

