Hello!
I created a source with the SCIM 2.0 SaaS connector and then got the source data with API v3/sources/{{source-ID}}.
We notice that many attributes have the same value
type, connector, connectorAttributes.spConnectorSpecId, connectorId, connectorImplementationId all have the same id as value.
connectorName, connectorAttributes.connectorName, connectorAttributes.templateApplication all have as value "SCIM 2.0 SaaS".
Which attribute does what exactly? Are all these attributes being used by IdentityNow?
2 Likes
There are a lot of reasons that fields might be redundant in IDN, but I don’t think it’s something to worry about. I don’t have documentation available for specific fields that are returned outside of what is available here: get-source | SailPoint Developer Community Since SaaS connectivity is simpler in terms of implementation, some fields might not be necessary to differentiate it, but are still required to create the connector so they are filled with the same values. Some fields like the connectorName and connectorAttributes.connectorName are most likely the exact same value in the database but are redundant in the API
Hi Philip,
Thank you for your response,
If we create such a source in our development environment and are at some point satisfied with it, we want to get the object configuration through GET v3/sources/{{source-ID}}, change the variables that needs to be changed (like URL, name, description, cluster->id, connectorId) in order to put it in our acceptance/production environment and then upload the source through POST v3/sources. In order to prevent odd behavior. We would need to know which attributes to change/remove in order to ensure that it still works in the new environment, and if we need to change and id, we would need to know which id to turn it into. Hence the question.
3 Likes