Non-standard SCIM fields are not accessed by Sailpoint IIQ

IdentityIQ (IIQ) IIQ Discussion and Questions
, , , ,
1

Which IIQ version are you inquiring about?

8.4

Please share any images or screenshots, if relevant.

Screenshot 2025-05-20 at 17.54.26
Screenshot 2025-05-20 at 17.54.261143×292 27.9 KB

Share all details about your problem, including any error messages you may have received.

Hey all, I’m onboarding an application with SCIM 2.0 connector. The SCIM server is implemented in my company, as it’s an homegrown application we develop. Its schemas differ from the SCIM’s standard, and the configuration in IIQ is set accordingly.
When discovering the schema everything works well, and all fields are indeed discovered. But when aggregation task runs (or when I view sample data using “Preview”), those custom fields (e.g. “employeeId”) are empty.
My goal is to configure correlation using one of those custom fields, but since it’s empty I can’t do that.
I do see that the SCIM server functions well and returns all of the data, it’s something inside IIQ that “drops” it.
Would appreciate any help.
Thanks!

2

Hi @YanivW

Based on the details provided I prefer doing below things

  1. Verify SCIM Response Format : Use a tool like Postman or curl to inspect the raw SCIM response. Look for the exact nesting of employeeId . For example:
{
  "schemas": ["urn:ietf:params:scim:schemas:core:2.0:User", "urn:custom:params:scim:schemas:extension:CustomUser:2.0"],
  "id": "123",
  "userName": "jdoe",
  "urn:custom:params:scim:schemas:extension:CustomUser:2.0": {
    "employeeId": "E12345"
  }
}
  1. Update Attribute Path in IIQ: In the application schema configuration, set the attribute path for employeeId to:
[urn:custom:params:scim:schemas:extension:CustomUser:2.0].employeeId

Try different syntaxes if needed:

  • urn:custom:params:scim:schemas:extension:CustomUser:2.0.employeeId
  • "urn:custom:params:scim:schemas:extension:CustomUser:2.0".employeeId