<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
0D54z0000A4gxiWCQQOkta Classic EngineLifecycle ManagementAnswered2024-04-30T17:43:49.000Z2024-04-16T12:15:21.000Z2024-04-30T17:43:49.000Z
Can I please get the documentation about how the user or group provisioning happens via SCIM in Okta.?

I have tried to integrate our application with Okta and when I am provisioning users from Okta to our application using SCIM. I see 2 behaviors

 

If the user is already present in our application, Okta performs below operations

  • Add user to application membership
  • Verify user exists in external application
  • Push user's profile to external application

 

If the user is NOT present in our application, Okta performs below operations

  • Add user to application membership
  • Push new user to external application
  • Successfully pushed new user account to app

 

 


  • Adding other details below as I couldn't add them on the case.

     

    After lot of research, the only details I could find are below-

    Create Users: Assigns a new account in your downstream application for each user managed by Okta. Okta doesn't create a new account if it detects that the username specified in Okta already exists in your application. The user's Okta username is assigned by default.

    Ref - https://developer.okta.com/docs/guides/scim-provisioning-integration-connect/main/

     

    My question starts from the fact that how does Okta checks that user is already present in the application. (Verify user exists in external application)

    Please share the detailed documentation explain the steps for better understanding of the events I have posted above that I see in Okta for SCIM.

    Expand Post
This question is closed.
Loading
Can I please get the documentation about how the user or group provisioning happens via SCIM in Okta.?