I have configured attr sync in my web service application.
The issue is my update account needs all attributes the same as create to be passed.
But what i am seeing is when attr sync is triggered it only sends the attributes that changes in the prov plan although my update plan includes everything.
This is an expected behavior, you will have attributes that are modified only in Plan. If your API call expects all the attributes then
Before Provisioning (BP) Rule: Add the missing attributes to the plan
WebService Before Operation (WSBO) Rule:
→ Create Update operation that will aggregate Single user
→ Create 2nd Update operation that actually performs update operation
In WSBO Rule, you need to check the request body:
→ if firstname attribute is not there in body then take value from firstname1
→ add firstname attribute to the body
→ remove firstname1 from the body
→ repeat same logic for other attributes
I would go with 2nd approach as BP Rule needs to be deployed in cloud by SailPoint.