Skip to content

Connecting Okta and SailPoint CIEM

Once you have configured your Okta account, you will use the Okta identity and CIEM Okta cloud governance connectors to display the total effective access users have to your cloud systems and resources. To display this data, you must use either the direct source Okta connector or the Okta SaaS connector with the CIEM Azure cloud governance connector.

Okta or Okta SaaS identity governance connector Allows you to manage your Okta users and groups in Identity Security Cloud on virtual appliance (VA) or SaaS systems.

If your organization has licensed SailPoint CIEM, it will also gather data about the AWS access granted to users through their Okta management groups.
CIEM Okta cloud governance connector Works with your Okta identity governance connector to collect cloud resource data and display the total access an identity has to your cloud systems.

You may connect your Okta identity governance and CIEM Okta cloud governance sources in any order.

After you've connected and aggregated your accounts and entitlements, you will mark the entitlements related to cloud access. This will allow you to view the cloud access granted through entitlements and include those entitlements in certification campaigns.

Connecting Okta Identity Governance

You can use CIEM Okta in conjunction with a SaaS or VA connector.

To install the identity governance connector:

  1. Follow the SailPoint Okta SaaS connector guide to configure or edit the Okta SaaS connector (recommended).

    If you are using a VA, you can alternatively configure or edit the direct source Okta connector.

  2. In the Feature Management configuration, select the Manage Cloud Resources checkbox to enable it to gather cloud data.

You must also use the CIEM Okta cloud governance connector to display all access users have to your cloud resources.

Connecting Okta Cloud Governance

The CIEM Okta source pulls daily data about the cloud resources your Okta IaaS users can access.

To create your CIEM Okta source:

  1. Go to Admin > Connections > Create New.

  2. Find and select the CIEM Okta source type.

  3. Enter a source name.

  4. Enter a description for your source.

  5. In the Source Owner field, begin typing the name of an owner. Matches appear after you type two letters.

  6. (Optional) Select a governance group for source management.

  7. Select Continue.

  8. Select Connection Settings.

  9. Enter the URL where your organization's Okta instance is hosted in the Okta URL field. This must match the Okta URL in your identity governance Okta connector.

  10. Enter your Okta API token in the Application Token field. If you are using an API token to authenticate your Okta identity governance source, they must match.
  11. Enter the Application ID of your configured Okta instance. You can enter multiple application IDs separated by commas.
  12. Select Save.
  13. Select Review and Test.
  14. Review the configuration details and select Test Connection. A successful test is required for CIEM to gather data for this source.


    If the test connection fails, you can use the Search query name:“Test_connection Source Failed” for more information.

After a successful test connection, you can set the source scope or move on to marking the entitlement types that grant cloud access.

Setting Source Scope

By default, CIEM reads and automatically discovers changes to your cloud infrastructure, which are displayed in the Cloud Scopes section of your CIEM source configuration. You can choose to exclude scopes to prevent CIEM from including data for those accounts.

To change the scope of your included source data:

  1. In the CIEM Okta source, select Cloud Scopes under Aggregation and Provisioning.
  2. Use the checkboxes to change which accounts are included. Removing a scope disables Auto-Include Scopes.
  3. Select Save.

CIEM will now only read and include data from your selected scopes. When Auto-Include Scopes is disabled, new and deleted accounts in your cloud system will be detected, but they will not be automatically included in your CIEM data until you select them individually or reenable Auto-Include Scopes.


  • You can search for scopes as well as filter by selected and unselected scopes.
  • The Last Refreshed time is when changes to your source inventory were last detected by CIEM. This is separate from aggregation.