Okta (OIDC)
This guide walks you through configuring Okta OIDC SSO using a temporary super admin API token. Glean uses the token to create the OIDC app in your Okta instance and assign it to all users automatically.
If your organization prefers to create the OIDC app manually without providing an API token, see Okta OIDC SSO tokenless setup.
Prerequisites
Before you begin, ensure you have:
- An active Okta administrator account with super admin privileges and permissions to create API tokens.
- Access to your Glean admin account with Admin or Setup Admin roles.
Glean restricts SSO authentication to domains that have been pre-approved. Ensure that you have notified Glean of all domains that will be used for user authentication (e.g., company.com, company.co.jp, subsidiary.co) or SSO will fail.
Create a temporary API token in Okta
The API token allows Glean to create the SSO app on your behalf. The token is only used during setup and should be deleted afterward.
-
Sign in to Okta as a super admin. Copy your Okta domain URL from the address bar and paste it into the Okta Domain URL field in Glean. For example,
https://YourOktaSubdomain-admin.okta.com. -
In the left navigation panel, under Admin Console, go to Security > API > Tokens and click Create Token.
-
In the Create token window, under What do you want your token to be named field, name the token Glean.
-
Select Any IP under API calls made with this token must originate from.
-
Click Create token.
-
Copy the Token Value. Save it for later.
Enter your Okta details in the Glean admin console
-
In the console, go to Users & permissions > Single sign-on (SSO).
-
Select Okta SSO.
-
In the Okta domain URL field, enter your Okta subdomain.
- Example admin URL:
https://yourcompany-admin.okta.com
- Example admin URL:
-
In the API token field, paste the temporary API token you created in Okta.
-
Optionally, choose to assign a bookmark app for all users.
-
Click Save. Glean uses the temporary API token to create the required Okta apps for setup.
-
Return to Okta and revoke or delete the temporary API token.