EimearB.44085 (Customer) asked a question.
SCIM Provisioning: "Locality" mapping PUT request not updating target application
Has anyone seen this occurring recently and know how to resolve it?
SCIM Provisioning:
I've city mapped to locality in target application
My city value = "Boston" and sends over to the target application perfectly on the POST request (user creation)
When my city value changes in OKTA to "Cork", it sends a PUT request to target application but for some reason the PUT contains both the old and new city field and the target app does not get updated
Image is not available
Would love some advice on how to solve this!
Hi @EimearB.44085 (Customer) , Thank you for reaching out to the Okta Community!
Custom SCIM provisioning issues are typically the purview of our colleagues from the dedicated Developer forum devforum.okta.com , so I would recommend posting this there.
In the meantime, I found an older post that might offer some insight:
https://support.okta.com/help/s/question/0D54z0000AIHzmCCQT/scim-update-users-manager-attributes-values-not-reflected-in-the-put-request-payload?language=en_US
Regards.
--
Help others in the community by liking or hitting Select as Best if this response helped you.
Collect them all. Learn a new skill and earn a new Okta Learning badge.
Just released: More Okta Community badges just added
Hi @EimearB.44085 (Customer) is this consistent across the board?
Were the mapping changed by any chance from type work and primary true?
There could be multiple values that are mapped somehow, with type work and primary true.
If this is not the case, I recommend you reaching out to support.
Also you can try looking at the application documentation on how it is handling multiple addresses
Just looking at your screen shots, it looks like one of your locality attributes is "primary" the other is "work". I am guessing that when you sent the change in locality, it assumed it would be the primary and therefore moved Boston to "work". There is probably another attribute in there that defines which locality it is updating (work or primary).
Its hard to know without knowing which app you are provisioning to unless this is a custom SCIM server. if its a custom server you can parse this accordingly