Okta Single Sign-On Provider for SharePoint On-Premises

SharePoint can use Okta as a trusted single sign-on (SSO) provider. Configure your Okta application and retrieve the application parameters so that the Coveo Claims security provider can authenticate users in SharePoint via Okta (see Microsoft SharePoint Connector).

Requirements

• CES 7.0.9272+ (March 2018)

• SharePoint 2016, 2013, or 2010

• You must add a trusted origin to the Okta application you use with your SharePoint instance:

  1. Log in to your Okta Developer account.

  2. Click Admin.

  3. Click Security, and then, in the drop-down menu, select API.

  4. Click the Trusted Origins tab.

  5. In the Trusted Origins tab, click Add Origin.

  6. In the Add Origin panel that appears:

     1. Under Name, enter a name.

        Example: Coveo Enterprise Search RedirectURI

     2. Under Origin URL, enter https://localhost.

     3. Select the Redirect checkbox.

     4. Click Save.

Retrieve your application parameters

Before you create a SharePoint security provider and source, you must retrieve two application parameters from Okta, as these parameters are required in the security provider and source configuration (see Creating a SharePoint Security Provider and Configuring and Indexing a Microsoft SharePoint Source).

1. Log in to your Okta Developer account.

2. Click Admin.

3. Click Applications, and then, in the drop-down menu, select Applications.

4. Click the SharePoint (On-Premise) application linked to the SharePoint instance you want to make searchable.

5. Click Sign On.

6. Under Settings > Sign On Methods, click View Setup Instructions.

7. In the new page that appears, under Setup a new authentication provider > Create the Okta Trusted Token issuer using PowerShell Script, take note of the $realm and $signInURL values, which should respectively be formatted as follows:

   Example:

   • urn:okta:sharepoint:myid

   • https://YOURINSTANCE.OKTA_OR_OKTAPREVIEW.com/app/sharepoint_onpremise/sso/wsfed/passive

   These values are required when creating your SharePoint security provider and SharePoint source (see Creating a SharePoint Security Provider and Configuring and Indexing a Microsoft SharePoint Source).