mickeyk.90866 (Customer) asked a question.
SCIM provisioning change username problem
I just paid attention to weird behavior while testing SCIM integration. This is my scenario:
Create user with username u1 and email u1@mydomain.com
Assign the user to my okta app -> the user is provisioned successfully.
Rename the user, change username to be u2 -> the change is provisioned successfully, but during the provisioning okta deactivates and activates the user.
Rename user once again back to u1 -> as a result okta called for GET with paramter "userName eq "up1" (I expect they are looking for "up2"), doesn't find it, creates new user "up1" and disables "up1" user
Hi @mickeyk.90866 (Customer) , Thank you for reaching out to the Okta Community!
It could be that the attribute is considered immutable, but you might also want to review the mappings to make sure it's not perhaps set to "Create" only instead of "Create and Update" as mentioned in the following documentation: https://developer.okta.com/docs/guides/scim-provisioning-integration-connect/main/
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Community members help others by clicking Like or Select as Best on responses. Try it today.