and more in a single search tool across platforms. Read the announcement here. |
03/21/2024 02:45 PM
We have a requirement to sync attributes to a SCIM endpoint using PATCH with replace / add operation for existing users.
If one or more existing attributes of a user changes, then UPDATEACCOUNT JSON must only have those attributes to sync with the target using the "replace" operation instead of all the user attributes. If a user attribute does not exist on the taget but needs to be included on specific users, then only that attribute must be pushed to the target using the "add" operation. How can the UPDATE account JSON be made conditional?
Note - A REST connector is being used in Saviynt to connect to the target.
03/21/2024 06:40 PM
You can store current values in accounts customproperty and if customproperty values are not matching with new value then update. but you can't skip updating existing values.
What is harm in reupdating same attributes ?
03/21/2024 08:00 PM
In any API integration approach with SCIM endpoints, the intent is to keep the payload as light as possible. Therefore, it is a good practice to not send all the attributes if most of them have not changed. From your response, I gather that it is a product limitation that the payload cannot be made dynamic.
03/24/2024 08:21 PM
Please submit idea ticket for same.