
00u8whnwe3e8ZsJ9k0h1.4804667264207979E12 (Customer) asked a question.
For SCIM 2.0, When you change the username of a assigned user to an application in OKTA, what happens is:
1. Okta sends a PATCH user to deactive the user
2. Okta sends a GET user with a filter of the new username
3. Okta sends a POST with the new user name
In step 3, why is OKTA doing a POST instead of a PUT? The user ID stays the same, so this is not a create but rather an update

Hello Alana,
My name is TeDeryl, with Okta Support. Although the user ID stays the same, we are changing the username for that user in that app. This would be considered an update on the Okta side. This is by design with Okta API. Details on this can also be reviewed here: https://developer.okta.com/docs/api/resources/apps#apps-api
Hi TeDeryl - my question is why is Okta doing a Create (POST) and not an Update (PUT/PATCH) ?
Since you said changing the username for that user is considered an update on the Okta side, we should be receiving a PUT/PATCH, but we are not.