Skip to main content
Cortex connects to many third-party vendors whose system interfaces frequently change. As a result, integration behavior or configuration steps may shift without notice. If you encounter unexpected issues, check with your system administrator or refer to the vendor’s documentation for the most current information. Additionally, integration sync times vary and are subject to scheduling overrides and timing variance.

​
Overview

Okta is an identity and access management (IAM) platform. Integrate Cortex with Okta to drive insights into authentication and ownership. After configuring the integration, you can set Okta teams and team members as owners of entities. For information on configuring Okta SSO or Okta SCIM for logging in to Cortex, see the Okta SSO documentation and Okta SCIM documentation.

​
How to configure Okta with Cortex

​
Prerequisites

Before getting started:
  • An Okta administrator, with at least the View groups permissions, must create an Okta API token.
    • Grant the following scopes for the API token:
      • okta.groups.read
      • okta.profileMappings.read
      • okta.users.read
  • Obtain your Okta domain.
    • This can be found in the prefix of your Okta URL. For example, https://domain.okta.com.

​
Configure the integration in Cortex

  1. In Cortex, navigate to the Okta settings page:
    • Click Integrations from the main nav. Search for and select Okta.
  2. Click Add configuration.
  3. Configure the Okta integration form:
    • Domain: Enter your Okta domain.
    • API token: Enter your Okta API token.
    • Group types: Specify which group types to include.
  4. Click Save.

​
How to connect Cortex entities to Okta

​
Import teams from Okta

See the Create teams documentation for instructions on importing entities.

​
Syncing ownership from Okta

The YAML examples on this page show only the x-cortex-* block. When you add one to an entity descriptor, nest it inside the info section. Blocks at the root level of the file are ignored without an error. For a full example, see Defining entities with YAML.
To assign an Okta group as an owner, add it to the entity descriptor:
The group name is case-sensitive and should be exactly the same as in Okta. Cortex syncs Okta teams every day at 3 p.m. UTC. Cortex uses identity mappings to connect group members to Cortex users when they exist, and falls back to each member’s email address from Okta otherwise. To compare ownership sources, see the Ownership sources reference.

​
Using the Okta integration

​
Scorecards and CQL

With the Okta integration, you can create Scorecard rules and write CQL queries based on Okta teams. See more examples in the CQL Explorer in Cortex.
A special built-in type that supports a null check or a count check, used to enforce ownership of entities.Definition: ownership: Ownership | NullExampleAn initial level in a security Scorecard might include a rule to ensure an entity has at least one team as an owner:
List of owners, including team members and individual users, for each entityDefinition: ownership.allOwners()ExampleThe Scorecard might include a rule to ensure that entity owners all have an email set:
List of teams for each entityDefinition: ownership.teams(): List<Team>ExampleThe Scorecard might include a rule to ensure that an entity owners all have a description and are not archived:

​
View integration logs

This feature is available in Cortex cloud.
While viewing an integration’s settings page, select the Error logs tab to view errors from the last 7 days. You can filter the logs list by configuration and by operation (for example, you could filter to view errors surfaced only via Scorecards).
The 'Logs' tab on an integration's settings page shows error information over the past 7 days.
Click into a row to get more information, including time stamp, status code, full error, and request path.

​
Background sync

Cortex conducts an ownership sync for Okta teams every day at 3 p.m. UTC.

​
Troubleshooting and FAQ

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

​
Still need help?

The following options are available to get assistance from the Cortex Customer Engineering team:
  • Email: help@cortex.io, or open a support ticket in the in app Resource Center
  • Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a :ticket: reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
Last modified on October 21, 2026