Skip to main content




Okta is an ownership platform. You can use Okta to drive insights into values such as:

  • Authentication
  • Ownership

For SSO, read our Okta SSO Guide.


You'll first need to create an API token. Given Okta ties tokens to administrators, your administrator's role will need at the minimum View groups permissions.

  1. Fetch your Okta domain by logging into Okta, and get the prefix in the url. For example, our URL is https://**{cortex}**, where cortex is the prefix.
  2. Create an API token by logging into Okta. You must have administrator privileges for the Okta account in order to generate a token.

Once you've created an API Token, add it under Settings → Okta.

Automatic user deprovisioning

Once Okta has been set up and the OpenID Connector has been configured, you will be able to enable automatic user deprovisioning. This is based on a sync job that runs once a day at 10 AM UTC. You’ll be able to see a list of users removed in audit logs.


If you do not see the Settings page you're looking for, you likely don't have the proper permissions and need to contact your admin.


Cortex can pull team memberships from Okta groups.

Entity descriptor

You can define the following block in your Cortex entity descriptor to add your Okta group as an owner.
- type: group
name: Engineering # group name in Okta
provider: OKTA
description: This is a description for this owner # optional

The group name is case-sensitive and should be exactly the same as in Okta.


  1. I've added an API token but the login is still using Google.
    1. To set up Okta for SSO, use the Okta SSO Guide.