Configure Okta as Claims Provider in SharePoint (On-Premises)
Before you begin
Complete Add SharePoint (On-Premises) in Okta.
- Ensure that the user account that has permissions to modify the SharePoint farm.
Ensure you have SharePoint Management Shell or SharePoint PowerShell snap-in to run PowerShell commands on your SharePoint Server. Add the required snap-in to an existing PowerShell prompt by entering the following the command:Add-PSSnapIn Microsoft.Sharepoint.Powershell
Start this procedure
This procedure includes the following tasks:
You can configure four attributes (Username, First Name, Last Name, and Email) for SharePoint. It allows wildcard matches for any preﬁx match of First Name, Last Name, and Email in the Okta user proﬁle attributes, as well as in the App user proﬁle attributes.
To configure mappings, go to Directory > Profile Editor > SharePoint (On-Premise) > Mappings.
- If you are setting the search scope level as OKTA and the identiﬁer claim as userName, then do not customize mappings for app user’s username.
- If you are setting the search scope level as APP, then do not customize mappings for an app user’s ﬁrstName/lastName/email nor leave those ﬁelds empty.
After you complete the installation procedure, Okta should appear in the Trusted Identity Provider list on the SharePoint Central Administration console.
- Go to SharePoint Central Administration > Security > Specify Authentication Providers > Default zone > Trusted Identity Provider list.
Confirm that you can see Okta in the list.
Make sure you disable the Okta Identity Provider whenever you install, uninstall, or update the Okta People Picker. See Uninstall Okta People Picker and Okta authentication.