<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
0D54z00009ecrW4CAIOkta Classic EngineIntegrationsAnswered2023-09-14T20:36:13.000Z2023-09-12T18:28:20.000Z2023-09-14T20:36:13.000Z

AdminT.03275 (Customer) asked a question.

In Okta SCIM Provisioning, can the User object by queried by externalId instead of filter=username?

I am talking about when querying the service provider for existence. Here https://developer.okta.com/docs/reference/scim/scim-20/*create-users It says, "Okta checks that the User object exists on the SCIM server through a GET method request with the 

filter=userName

Can the default, filter=username, be updated to filter by externalId?


  • Hello @AdminT.03275 (Customer)​ Thank you for reacting out to our Community!

     

    This should be achieved when you change the username format of the application. From the Sign On tab you can change that to match the required attribute desired.

     

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Follow us at OktaSupport 

    Expand Post
    • AdminT.03275 (Customer)

       

      @paul.stiniguta1.508386743840768E12 (Okta, Inc.)​ I do not want to change the application username format, I'm looking to update the filter so that Okta checks the user object through a GET method request with the filter=externalId (instead of the default filter=userName). Is this possible?

  • AdminT.03275 (Customer)

    @paul.stiniguta1.508386743840768E12 (Okta, Inc.)​ to be clear, we're talking about the SCIM lookup in the SP for existence. From the Okta documentation:

     

    Okta checks that the User object exists on the SCIM server through a GET method request with the 

    filter=userName

     parameter (or any other filter parameter that was configured with the SCIM integration). This check is performed using the 

    eq

     (equal) operator and is the only one necessary to successfully provision users with Okta.

     

    This has nothing to do with SAML/Sign-On and the username format.

    Expand Post
  • Hello @AdminT.03275 (Customer)​  You can change this from the Provisioning tab -> To Oktaa and there you can edit the change the user creation & matching. It would be "The following attribute match" where you can change it to ExternalID

     

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    Follow us at OktaSupport 

    Expand Post
This question is closed.
Loading
In Okta SCIM Provisioning, can the User object by queried by externalId instead of filter=username?