<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
0D51Y00006OD4XKSA1Okta Classic EngineOkta Integration NetworkAnswered2024-03-25T21:49:51.000Z2019-06-27T01:09:04.000Z2019-07-01T18:13:18.000Z
  • Hi Steve, I've asked my product colleagues for guidance here. In the meantime, wondering if anyone else in the Okta Community has solved this before and can help out?

  • Hi Steve,

     

    Installing Okta SharePoint People Picker solution on a site level, it will replace the search indexer having it point to Okta when querying users by any of the configured claims. 

     

    In order to apply to the on-prem version of Sharepoint , these are the commands that need to be applied for every site : 

     

    $webApplication = Get-SPWebApplication

     $ webApplication.Properties["UserSearchScope"] = "OKTA"

     

    OR

     

    $ webApplication.Properties["UserSearchScope"] = "APP"

    $ webApplication.Properties["UserSearchScopeAppId"] = "{AppID}" //app instance id in Okta org

     

     $webApplication.Update();

     

     

     

     

     

    If you're referring strictly to the online version of Sharepoint (Microsoft Suite) then the entire configuration will go through a provisioning API. If you have additional questions in regards to the deployment, I strongly suggest opening up a support ticket to further discuss the details.

     

     

     

     

     

    Thank you,

     

    Marius Fulga

     

    Tier 2 Support Engineer

     

    Expand Post
This question is closed.
Loading
How do you manage the SharePoint Online ADFS Claim token when migrate to Okta Claims Token