<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
0D54z00006rrTHOCA2Okta Classic EngineOkta Integration NetworkAnswered2024-04-16T12:30:31.000Z2021-03-10T15:50:51.000Z2021-03-14T09:01:04.000Z

jvz0a (jvz0a) asked a question.

Okta SCIM provisioning issue (state mismatch)

We created a SCIM app on .NET for user provisioning and testing our SCIM API integration. We have noticed the following scenario:

 

  • Create 100 users.
  • Create a group "myGroup", assign 100 users to it.
  • In the SCIM app, assign "myGroup" to the SCIM app. (all requests are POST requests and successfully completed).
  • Then, unassigned "myGroup" from the SCIM app. (all requests are successfully completed).

Request behaviors are:

  1. Search User
  2. Update User
  3. Search User
  4. Disable User (isActive : false)
  • Then, assign "myGroup" to the app. (state mismatch).

9 Users have the following request behavior:

  1. Search User
  2. Update User
  3. Search User
  4. Enable User (isActive : true)

91 Users have the following request behavior: (No search and update for other users)

  1. Add User.

 

Now, assign this group again and only 9 users updated, and the rest of the 91 were no updated.

 

 


  • Hi Abdul,

     

    In this case, the best course of action would be to open a support case since the described issue required further troubleshooting, something that can not be performed via the community ticket.

     

    Thank You,

     

    Alexandru Moraru

    Technical Support Engineer

    Okta Global Customer Care.

    Expand Post
This question is closed.
Loading
Okta SCIM provisioning issue (state mismatch)