<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008KgGsFSAVOkta Classic EngineOkta Integration NetworkAnswered2018-09-13T18:53:05.000Z2018-09-07T17:30:40.000Z2018-09-13T18:53:05.000Z
Why does OKTA do a POST on deactivated user?

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


lebbq likes this.
This question is closed.
Loading
Why does OKTA do a POST on deactivated user?