Product

ClearVector supports Okta Cross App Access for AI agents

Nov 06, 2026 • 5 min read

ClearVector supports Okta Cross App Access (XAA) for connecting AI agents to ClearVector through the Model Context Protocol (MCP). Okta issues each AI agent a short-lived token through the Okta identity of the person the AI agent acts for, and ClearVector accepts that token for access to the ClearVector identity graph.

AI agents reach the ClearVector MCP server without a shared application programming interface (API) client secret. Your Okta policies decide which AI agents reach ClearVector, on whose behalf, and with what scope.

‍

What does Cross App Access change for AI agents that use ClearVector?

Cross App Access puts AI agent access to ClearVector under the Okta policies that already govern your people. An AI agent reaches ClearVector only with a token Okta issued for a specific person and task, so your security team controls that access from Okta instead of through keys spread across AI agent configurations.

  • Access governed by Okta policy. Your team decides in Okta which AI agents can reach ClearVector and on whose behalf.
  • No shared API client secret. AI agents reach the ClearVector MCP server without a shared API client secret, so your team has no shared ClearVector secret to rotate or track down for those AI agents.
  • Access tied to a person. Okta grants access that expires after 60 minutes and attributes each request to the individual user the AI agent acts for, so every AI agent request to ClearVector traces to that person.
  • Revocation from one place. Your security team revokes an AI agent’s access to ClearVector through Okta, and Okta logs every token Okta issues.
  • Fewer consent prompts. Your team approves fewer Open Authorization (OAuth) consent prompts when AI agents connect to ClearVector.
    ‍
Static API key versus Okta Cross App Access token for AI agents: the key stays valid until rotated, the token is short-lived, revocable, and logged by Okta

‍

What is Okta Cross App Access?

Okta Cross App Access, formally the Identity Assertion Authorization Grant, is an open protocol built as an extension of Open Authorization (OAuth) and incorporated into the Model Context Protocol (MCP) as an authorization extension. Okta issues short-lived tokens scoped to the task, revocable at any point and logged for audit, in place of static API keys.

Cross App Access is included in Okta workforce single sign-on (SSO) plans at no extra cost, and Okta made Agent SSO and XAA generally available in August 2026.

“Organizations shouldn’t have to choose between adopting AI tools and maintaining visibility over enterprise access,” says Aaron Parecki, Senior Director of Identity Standards at Okta. “By connecting apps with the Cross App Access protocol, security teams get more control and users get a better experience without all the OAuth consent prompts.”

‍

Okta Cross App Access flow: an AI agent requests access, Okta issues a short-lived token for one person and task, and the ClearVector MCP server accepts the token

‍

How do you set up Cross App Access for ClearVector?

Cross App Access setup is self-service and takes five steps across ClearVector and Okta. In ClearVector, create a Cross App Access client under Settings > API access. In Okta, create the requesting app for the AI agent, enable Cross App Access on the ClearVector app, and grant the AI agent the scopes ClearVector lists.

  1. In ClearVector, open Settings > API access and select Add a Cross App Access client. Enter a client name that identifies the Okta app or AI agent the client belongs to.
  2. Copy the client ID and client secret. ClearVector shows the secret once and cannot retrieve the secret again.
  3. In Okta, create the requesting app for the AI agent and enter the client ID and client secret.
  4. On the Resource Server tab of the ClearVector app in Okta, enable Cross App Access. Enter https://api.clearvector.com as both the issuer URL and the resource identifier, and enter the audience tenant ID, which is your ClearVector customer ID.
  5. Add a resource connection from the AI agent to the ClearVector app and grant read:summaries, read:narratives, read:entities, and read:connections.

‍

ClearVector Settings, API access page with the Cross App Access section and the Add a Cross App Access client option for AI agents

‍

When is Cross App Access support available?

ClearVector support for Cross App Access is available to all ClearVector customers now. Customers can create a Cross App Access client under Settings > API access and connect AI agents through the ClearVector MCP server.

‍

What does Cross App Access support cover?

Cross App Access support covers AI agents that access ClearVector through the ClearVector MCP server. Human sign-in to ClearVector does not change: people still sign in through the ClearVector app in the Okta Integration Network (OIN), a third-party identity provider you configure, or a ClearVector username and password.

‍

ClearVector Cross App Access client ID and client secret beside the Okta values for issuer URL, resource identifier, and audience tenant ID

‍

Why use Okta and ClearVector together for AI agent access?

Okta knows who logged in. ClearVector knows what they did after. Okta governs which AI agents get access to ClearVector and on whose behalf. ClearVector shows what every identity does inside production after authentication, and stops misuse in one click or API call.

ClearVector provides behavioral identity and runtime response for cloud-native and AI-active environments. A live operating model of how every identity operates, built from the pattern of life ClearVector observes inside production, supplies the production identity intelligence behind that response.

‍

Run an Identity Compromise Assessment: find out if you’re already living with an unknown breach.

‍

Frequently asked questions about Okta Cross App Access and ClearVector

Does Okta Cross App Access cost extra?

Cross App Access is included in Okta workforce single sign-on plans at no extra cost. ClearVector support for Cross App Access is available to all ClearVector customers starting November 2026.

Does Cross App Access change how people sign in to ClearVector?

No. Cross App Access support covers AI agents that access ClearVector through the ClearVector Model Context Protocol (MCP) server. People still sign in through the ClearVector app in the Okta Integration Network, a third-party identity provider you configure, or a ClearVector username and password.

Can a security team revoke an AI agent’s access to ClearVector?

Yes. Okta issues every Cross App Access token, so a security team revokes an AI agent’s access to ClearVector through Okta. Okta logs every token Okta issues, and each token carries the Okta identity of the person the AI agent acts for.

Do AI agents need a shared API client secret with Cross App Access?

AI agents that connect through the ClearVector Model Context Protocol (MCP) server with Cross App Access reach ClearVector without a shared application programming interface (API) client secret. Okta grants access that expires after 60 minutes and attributes that access to the individual user the AI agent acts for.

How does ClearVector work with Okta for AI agent access?

Okta governs which AI agents get access to ClearVector and on whose behalf. ClearVector shows what every identity does inside production after authentication, and stops misuse in one click or API call.

More production insights, tips & news

Blog
Perspectives
Product
Product