Hi everyone,
Had a question about SCIM 2.0 connectors + I would like to mention a bug I think I found.
First lets get the bug out of the way.
If there is an error on the target system, in our case it was a type error. Instead of propertySet the value was name propertSet (missing the last letter). Initially discovering the schema set the account attribute and the field under schemaPropertyMappings source json object to propertSet. This in turn didn’t allow IdentityNow to send the field if we named it propertySet in the provision policy. Tried changing the account schema to the correct name but it didn’t work so we contacted target system and they fixed it on their end. The problem was that IDN, after re discovering the schema, it did update the account schema but not the schemaPropertyMappings object. We had to do a replace to fix it. So unless we miss something the schemaPropertyMappings object isn’t updated retroactively when you discover schema.
Now for the question. We need to add a date to the create provision policy but again the attribute doesn’t exist on the target system SCIM schema so we were wondering if we can do the same trick, add the attribute manually in the schemaPropertyMappings + the account schema so we can use it. Requesting the target system devs to do it might be time consuming. Is it safe to do it like this or will an update to the connector probably break the source json? Can we get some insight on how the update to connectors is pushed by Sailpoint? Are only the libraries changes while the jsons remain mostly the same? Maybe I am oversimplifying it just for the question sake.
Thanks