Connecting Okta
Last Modified: 2026-11-19

Connecting Okta

You can connect RSA Agent ID to Okta through the Okta Management API. It imports users, groups, applications, and API service integrations, along with identity, application, and activity information, to support discovery, ownership resolution, and dormancy analysis for AI agents, automation frameworks, and third-party integrations in your Okta organization.

Unlike other connectors, the Okta connector authenticates with a private key (Private key JWT) instead of a client secret. RSA Agent ID generates the key pair; the private key stays in RSA Agent ID and you register the public key in Okta.

Before you begin 

Ensure you have the following:

Type

Requirement

Purpose

Okta accountAn Okta administrator account that can create applications, grant API scopes, and assign administrator rolesTo create the API Services app and grant it access
Okta applicationAn API Services app integration that uses a private key for client authenticationTo let RSA Agent ID authenticate to Okta without a shared secret
Connection detailsYour Okta domain and the app's Client IDTo identify the Okta organization and application in the connector form

Required Permissions

Grant the following Okta API scopes to the API Services app. Okta scopes are granted separately from administrator roles; both are required.

ScopeRequired
okta.apps.readAlways
okta.appGrants.readAlways
okta.users.readAlways
okta.groups.readAlways
okta.roles.readAlways
okta.apiTokens.readAlways
okta.logs.readAlways
okta.oauthIntegrations.readAlways
okta.clients.readAlways
okta.aiAgents.readOnly if you use Okta for AI Agents

The app also needs administrator roles. Assign the following roles to the API Services app:

  • Read-only Administrator

  • A custom role with the permissions okta.iam.read, okta.users.read, okta.groups.read, and okta.apps.read, over all IAM resources, users, groups, and applications

If your organization uses Okta for AI Agents, also add the okta.aiAgents.read permission to the custom role, with all AI agents in its resource set, so that every AI agent is read.

Note:  Do not assign the Super Administrator role to the app. It gives the app full control of the Okta organization, and the connector only reads data. Without it, Okta API scope grants and API service integrations are read from the System Log, so grants and integrations that are more than 90 days old (and, for integrations, unused since) are not visible. If you assign Super Administrator anyway, also grant okta.governance.resourceOwner.read so that the owners of AI agents are read.

Okta-side Setup (Okta Admin Console)

Procedure 

  1. Sign in to the Okta Admin Console and go to Applications > Applications > Create App Integration.
  2. Select API Services, click Next, enter a name (for example agent-discovery-api-app), and click Save.
  3. Copy the Client ID and note your Okta domain (for example acme.okta.com). Use the organization's own domain (okta.com, oktapreview.com, or okta-emea.com), not a custom domain or the -admin domain.
  4. Leave the app open. Complete Agent ID Setup through the Generate key step. Then return here and, under Client Credentials, choose Public key / Private key and add the public key (JSON Web Key) that RSA Agent ID generated.
  5. On the Okta API Scopes tab, grant each scope listed in Required Permissions.
  6. On the Admin roles tab, assign the Read-only Administrator role and the custom role. Do not assign Super Administrator.

Agent ID Setup

Procedure 

  1. On the Connectors page, click Add source.
  2. In the Add a source dialog, locate Okta and click Connect on the Okta card.
  3. Enter a Connection name (for example, Production Okta org), the Okta domain, and the Client ID. Do not include https:// or a path in the domain.
  4. Click Generate key at the bottom of the form. This saves the connector as pending; it starts scanning once you confirm the key is added.

    Copy the public key (JWK) or click Download .json before you leave the page. It is shown only once.

  5. In Okta, add the public key to the API Services app, grant the scopes, and assign the administrator roles, as described in Okta-side Setup.
  6. In RSA Agent ID, click Confirm to verify the connection.

    When verification succeeds, the status shows Connected and the scopes that Okta reports as granted are listed. Review any notes shown about missing scopes. Then save the connector.

The private key stays in RSA Agent ID and is never displayed or exported. The public key cannot be replaced after it is generated. If it is lost, or you need a new key, remove the connector and add it again. The Okta domain and Client ID cannot be changed after the connector is created.

If the connection test reports that a scope is not granted, the related data is missing or less complete in the scan results. Grant the missing scope in Okta and run the verification again.

Troubleshooting

  • Test Connection fails.

    Verify the Okta domain (no https://, custom domain, or -admin domain) and the Client ID, and confirm that the public key from RSA Agent ID is added to the Okta app and is active. A lost key cannot be recovered; remove the connector and add it again.

  • Some data is missing after a scan.

    A scope was not granted or a role was not assigned. Compare the app's Okta API Scopes and Admin roles tabs with this topic, and then rescan.

  • No AI agents are listed from Okta.

    If you use Okta for AI Agents, grant the okta.aiAgents.read scope, add the okta.aiAgents.read permission to the custom role with all AI agents in its resource set, and rescan.

  • A warning says Super Administrator is granted to the app.

    Remove the Super Administrator role in the Okta Admin Console and keep the read-only administrator roles.

  • Connector worked, then stopped.

    The key may have been deactivated or deleted in Okta, or the app was deactivated. Reactivate the app or key in Okta. If the key was deleted, remove the connector and add it again to generate a new key.