Which IIQ version are you inquiring about?
8.3P4
Share all details about your problem, including any error messages you may have received.
I’m trying to integrate PingONE with SailPoint IIQ through SCIM2. I’ve run into a few issues that I’m hoping someone can help with.
- When setting up the application, Discover Schema does not discover all schema items (e.g. type, department) which are part of the schema.
- When getting the schemas via Postman all attributes are listed but I did notice that the extra items were located in urn:pingidentity:schemas:2.0:DirectMappedUser as opposed to urn:ietf:params:scim:schemas:core:2.0:User. There are also other items in urn:ietf:params:scim:schemas:core:2.0:User that are not discovered but I’m not using them.
- Even after adding in the extra schema attributes, not all attributes are aggregated in on an aggregation.
- I filled in all the attributes in PingOne for a specific user. When aggregating, only some of the attributes were aggregated in when I look on the application tab of the identity cube under the PingOne app.
I did try the discover with non-compliant server checked. The results from that were many more schema attributes, but many that are not part of the configured schema and still not all of the ones that are part of the configured schema. Doing an aggregation from this setup did not give me all attributes in the identity either. I reverted to the backup of the application.
We will be provisioning from SailPoint to PingOne, but I think some of the issues I’m having with that may be resolved if the above is working properly.
Thanks for any help and insight you can provide.