# cross-app-access

Cross-App Access (XAA) is an OAuth extension that enables an enterprise identity provider to manage connections between applications and broker cross-domain API access.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## What Are EMA, ID-JAG, and XAA? Scoped Access for AI Agents

DevFeed: [What Are EMA, ID-JAG, and XAA? Scoped Access for AI Agents](<https://devfeed.tech/articles/what-are-ema-id-jag-and-xaa-scoped-access-for-ai-agents-133476.md>)

Original publisher: [Read original article](<https://www.cyera.com/blog/ema-id-jag-xaa-token-exchange>)

Author: Barak Shelef

Published: 2026-11-13T18:05:32Z

Content type: article

Language: en

Sources: [Cyera Blogs](<https://devfeed.tech/sources/cyera-blogs.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [Keycloak](<https://devfeed.tech/topics/keycloak.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [acquisition](<https://devfeed.tech/tags/acquisition.md>), [actions](<https://devfeed.tech/tags/actions.md>), [admin](<https://devfeed.tech/tags/admin.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [adversarial](<https://devfeed.tech/tags/adversarial.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [cyera](<https://devfeed.tech/tags/cyera.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [id](<https://devfeed.tech/tags/id.md>), [identity](<https://devfeed.tech/tags/identity.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [policy](<https://devfeed.tech/tags/policy.md>), [token](<https://devfeed.tech/tags/token.md>), [token-exchange](<https://devfeed.tech/tags/token-exchange.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

The article argues that AI agents need task-scoped, short-lived credentials instead of broad, long-lived OAuth grants: narrow instructions alone cannot bound what an agent may do. XAA is the cross-application brokering pattern, ID-JAG is an active IETF draft for short-lived, audience-bound identity assertions, and EMA is the stable MCP extension applying that approach. Token Exchange narrows credentials at each boundary. Cyera Identity AAM evaluates an agent's intent against policy before requesting a token; on approval, it brokers scoped access and records the decision. Adoption depends on both the identity provider and each MCP server, and support and scope granularity vary. The article advises verifying current vendor support and asking about production availability, per-resource scope enforcement, and EMA delivery dates. Where EMA is unavailable, AAM says it can use other server-supported mechanisms, but recommends validating that behavior in each environment.

### Source excerpt

Cyera Identity's Agentic Access Management supports EMA, ID-JAG, XAA, and OAuth Token Exchange, giving AI agents scoped, policy-evaluated access that expires when the task ends.

## What is Cross App Access (XAA) for MCP?

DevFeed: [What is Cross App Access (XAA) for MCP?](<https://devfeed.tech/articles/what-is-cross-app-access-xaa-for-mcp-122604.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/09/what-is-cross-app-access-xaa-for-mcp/>)

Author: Ritesh Patel

Published: 2026-11-08T20:12:46.132051Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-code](<https://devfeed.tech/tags/ai-code.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [security](<https://devfeed.tech/tags/security.md>), [servers](<https://devfeed.tech/tags/servers.md>), [sso](<https://devfeed.tech/tags/sso.md>), [token](<https://devfeed.tech/tags/token.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

MCP's optional Enterprise-Managed Authorization extension lets an enterprise identity provider (IdP) decide whether a user may use a particular MCP client with a server and scopes, avoiding per-server authorization when both client and server support enterprise SSO. The client exchanges an ID token (or, in the described SAML case, a refresh token) at the IdP for an ID-JAG; it presents that grant to the server's authorization server, which validates it and returns a server-audience-restricted access token. The IdP may require client authentication, MFA, and client registration. Clients discover support through authorization server metadata listing the ID-JAG grant profile. The IdP sees token issuance, not tool traffic, so its policy cannot prevent misuse of tools the agent is authorized to call. The extension is optional; the article's unauthenticated exchange example was not tested against an IdP.

### Source excerpt

Cross App Access (XAA) lets your identity provider decide which MCP clients reach which MCP servers, via a signed ID-JAG exchanged for an access token.

## Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore - Part 2

DevFeed: [Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore - Part 2](<https://devfeed.tech/articles/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-2-121742.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-2/>)

Author: Hammad Ausaf

Published: 2026-11-06T17:09:23Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [okta](<https://devfeed.tech/topics/okta.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [agent observability](<https://devfeed.tech/topics/agent-observability.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-access](<https://devfeed.tech/tags/ai-agent-access.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eks](<https://devfeed.tech/tags/amazon-eks.md>), [app](<https://devfeed.tech/tags/app.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [bind](<https://devfeed.tech/tags/bind.md>), [cloudwatch](<https://devfeed.tech/tags/cloudwatch.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [okta](<https://devfeed.tech/tags/okta.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The article shows how to scale Okta Cross App Access governance from one agent to multiple agents and tools. Amazon Bedrock AgentCore Gateway becomes each agent's front door, redeems the agent's ID-JAG for permitted targets, and applies Cedar policies that bind tools to the agent and delegated scopes; MCP servers still enforce user group permissions. Each agent gets its own Gateway and credential provider, and a second agent on EKS validates its ID-JAG before model calls. AgentCore Observability and CloudWatch collect traces of authorization decisions alongside Okta System Log events. The article also contrasts XAA, where Okta controls future grants and issued tokens expire in about five minutes, with per-user OAuth consent, whose stored grants persisted after account suspension until disconnected. The code is conceptual sample code, not a complete deployable solution.

### Source excerpt

In Part 1 you built one governed agent. Part 2 scales the pattern to an enterprise: Amazon Bedrock AgentCore Gateway becomes the single front door and redeems Okta's grant, Cedar policies bind each tool to the agent, a second agent runs on Amazon EKS, and AgentCore Observability traces every allow and deny beside Okta's log in Amazon CloudWatch.

## Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore - Part 1

DevFeed: [Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore - Part 1](<https://devfeed.tech/articles/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-1-121741.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/govern-ai-agent-access-with-okta-cross-app-access-and-amazon-bedrock-agentcore-part-1/>)

Author: Hammad Ausaf

Published: 2026-11-06T17:09:18Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [okta](<https://devfeed.tech/topics/okta.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [act](<https://devfeed.tech/tags/act.md>), [admin](<https://devfeed.tech/tags/admin.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agent-access](<https://devfeed.tech/tags/ai-agent-access.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [app](<https://devfeed.tech/tags/app.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [bedrock-agentcore](<https://devfeed.tech/tags/bedrock-agentcore.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [identity](<https://devfeed.tech/tags/identity.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [okta](<https://devfeed.tech/tags/okta.md>), [service-accounts](<https://devfeed.tech/tags/service-accounts.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [user](<https://devfeed.tech/tags/user.md>)

### AI overview

Okta Cross App Access governs which agent may act for which user, while Amazon Bedrock AgentCore carries out that decision. The BFF exchanges the user's ID token for a single-use, five-minute ID-JAG; AgentCore runtime accepts only grants issued to the configured agent; AgentCore Identity redeems each grant for a short-lived token naming both user and agent, then caches it for reuse within the request. MCP servers enforce user authority using group and scope claims. In the authors' tests, removing a user blocked new ID-JAG requests in about one second, while previously issued tokens expired within five minutes; Identity added about 0.6 seconds to an approximately 30-second request. The article also reports that plain RFC 8693 exchange carried user identity but not user authority in their Okta configuration. The walkthrough is based on an AWS sample; its snippets are conceptual, not a complete deployable solution, and are intended for non-production use.

### Source excerpt

An AI agent that acts for a user raises an identity question that per-app OAuth and service accounts leave open: which agent may act for which user, and how you stop it. In this first post of two, you build a task agent on Amazon Bedrock AgentCore that governs access through Okta Cross App Access and AgentCore Identity, and enforces each user's authority.

## Bring Your Own IdP to Harness MCP | OAuth Proxy Mode

DevFeed: [Bring Your Own IdP to Harness MCP | OAuth Proxy Mode](<https://devfeed.tech/articles/bring-your-own-idp-to-harness-mcp-oauth-proxy-mode-92574.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/bring-your-own-identity-provider-to-harness-mcp>)

Author: Piyush Patel

Published: 2026-10-21T00:00:00Z

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [OAuth](<https://devfeed.tech/topics/oauth.md>), [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [pkce](<https://devfeed.tech/topics/pkce.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>)

Tags: [aes](<https://devfeed.tech/tags/aes.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-developer](<https://devfeed.tech/tags/ai-developer.md>), [blog](<https://devfeed.tech/tags/blog.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [harness](<https://devfeed.tech/tags/harness.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [idp](<https://devfeed.tech/tags/idp.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-oauth](<https://devfeed.tech/tags/mcp-oauth.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [proxy](<https://devfeed.tech/tags/proxy.md>), [static](<https://devfeed.tech/tags/static.md>), [tokens](<https://devfeed.tech/tags/tokens.md>)

### AI overview

OAuth proxy mode lets a self-hosted Harness MCP server accept a developer's company identity-provider token while calling Harness with that developer's linked HarnessID token. At sign-in, the broker redirects through the company IdP and HarnessID; the server stores HarnessID tokens encrypted, while the IDE receives the company token and a broker-issued refresh token. For each request, the server checks the company token's signature, issuer, audience, and expiry, then uses or refreshes the user's HarnessID token. A failed link or revoked refresh token returns 401 and requires sign-in again; the server does not fall back to shared credentials. The excerpt describes per-leg S256 PKCE, server-held client secrets, AES-256-GCM encrypted token storage, restricted callback URLs, and optional TLS-protected Redis storage across pods. Harness RBAC and audit logs apply to the individual user. Enabling the mode requires contacting Harness support.

### Source excerpt

Learn how Harness MCP OAuth proxy mode enables enterprise developers to use their own identity provider without static tokens or shared credentials. | Blog

## Agent to agent SSO across identity domains: What federation looks like when neither side is human

DevFeed: [Agent to agent SSO across identity domains: What federation looks like when neither side is human](<https://devfeed.tech/articles/agent-to-agent-sso-across-identity-domains-what-federation-looks-like-when-neither-side-is-human-91175.md>)

Original publisher: [Read original article](<https://workos.com/blog/agent-to-agent-sso-federation>)

Author: WorkOS

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [a2a](<https://devfeed.tech/tags/a2a.md>), [about](<https://devfeed.tech/tags/about.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-gateway](<https://devfeed.tech/tags/agent-gateway.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agent-sso](<https://devfeed.tech/tags/agent-sso.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [company](<https://devfeed.tech/tags/company.md>), [cross](<https://devfeed.tech/tags/cross.md>), [identity](<https://devfeed.tech/tags/identity.md>), [launch](<https://devfeed.tech/tags/launch.md>), [like](<https://devfeed.tech/tags/like.md>), [okta](<https://devfeed.tech/tags/okta.md>), [sso](<https://devfeed.tech/tags/sso.md>), [standards](<https://devfeed.tech/tags/standards.md>)

### AI overview

Cross-company agent SSO is shipping, but its standards and end-to-end trust model remain unsettled. Okta's Agent SSO uses ID-JAG so a remote identity provider can exchange an agent's identity for a narrowly scoped token without directly trusting the agent; the IETF draft is still unfinished, and A2A explicitly leaves credential provisioning to separate security standards. The core gap is proving that an entire multi-agent delegation chain was authorized, rather than merely validating each hop. TLS establishes a domain, OAuth authenticates sessions, and delegation claims do not by themselves prove the full chain or bind every message to its sender. The article contrasts Descope's gateway-based, MCP-native authorization with ServiceNow's AI Passport, which checks signed credentials against enterprise configuration and governance context. It notes that Okta's Runtime Agent Gateway was still pre-GA in early October 2026 and that neutral standards work remains underway. Short-lived, scoped, individually accountable agent identities and structured audit trails within each organization are presented as prerequisites for trustworthy federation.

### Source excerpt

What Okta's Agent SSO launch reveals about the unfinished standards behind cross-company agent identity.

## What is Enterprise-Managed Authorization (EMA)?

DevFeed: [What is Enterprise-Managed Authorization (EMA)?](<https://devfeed.tech/articles/what-is-enterprise-managed-authorization-ema-91181.md>)

Original publisher: [Read original article](<https://workos.com/blog/what-is-enterprise-managed-authorization>)

Author: WorkOS

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [WorkOS](<https://devfeed.tech/sources/workos-blog.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [can](<https://devfeed.tech/tags/can.md>), [consent](<https://devfeed.tech/tags/consent.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [managed](<https://devfeed.tech/tags/managed.md>), [screen](<https://devfeed.tech/tags/screen.md>), [what-is](<https://devfeed.tech/tags/what-is.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Enterprise-Managed Authorization (EMA) lets an identity provider (IdP) approve an AI agent's access to an app on an employee's behalf, replacing repeated per-user consent screens for configured connections. The agent signs in through SSO, requests a short-lived ID-JAG from the IdP, and presents it to the app's authorization server, which verifies it and issues a normal OAuth access token. IT can govern access through existing groups and roles; removing a user stops new ID-JAGs, while already-issued access tokens remain valid until expiry. EMA requires the IdP, agent, and app to support the flow and trust one another. The article says support is still narrow, the ID-JAG specification is a draft, and many internal APIs, databases, and CLIs remain outside its coverage. EMA governs app access and scopes, not approval of individual actions.

### Source excerpt

How your identity provider can grant AI agents access to work apps, without a consent screen for every app and every agent.

## ID-JAG, Explained: The New OAuth Grant for Cross-App Access

DevFeed: [ID-JAG, Explained: The New OAuth Grant for Cross-App Access](<https://devfeed.tech/articles/id-jag-explained-the-new-oauth-grant-for-cross-app-access-91174.md>)

Original publisher: [Read original article](<https://auth0.com/blog/what-is-id-jag/>)

Author: Carla Urrea Stabile

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [Auth0 Blog](<https://devfeed.tech/sources/auth0-blog.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [JSON Web Tokens](<https://devfeed.tech/topics/jwt.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [saml](<https://devfeed.tech/topics/saml.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api](<https://devfeed.tech/tags/api.md>), [auth0](<https://devfeed.tech/tags/auth0.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [company](<https://devfeed.tech/tags/company.md>), [consent](<https://devfeed.tech/tags/consent.md>), [console](<https://devfeed.tech/tags/console.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [flow](<https://devfeed.tech/tags/flow.md>), [identity](<https://devfeed.tech/tags/identity.md>), [idp](<https://devfeed.tech/tags/idp.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [resource](<https://devfeed.tech/tags/resource.md>)

### AI overview

An ID-JAG (Identity Assertion JWT Authorization Grant) is a short-lived, signed token an enterprise IdP issues after checking policy to authorize one app to access another app's API on a user's behalf. In the described OIDC flow, the user signs in once; the requesting app exchanges its ID token for an ID-JAG, then presents the grant to the resource app's authorization server to obtain an access token for API calls. This requires an existing trust relationship between that server and the enterprise IdP. The grant itself cannot call the API, and the exchange does not issue a refresh token. The article describes this as a non-interactive alternative to repeated consent prompts, with enterprise policy governing access. ID-JAG builds on OAuth Token Exchange (RFC 8693) and JWT Bearer grant (RFC 7523). The IETF specification is a working draft, and Auth0 Cross App Access is described as Early Access.

### Source excerpt

Learn what an ID-JAG (Identity Assertion JWT Authorization Grant) is, the cross-app access problem it solves, and how the flow works between a requesting app, resource app, and enterprise IdP.

## Vercel Connect adds Enterprise-Managed Authorization

DevFeed: [Vercel Connect adds Enterprise-Managed Authorization](<https://devfeed.tech/articles/vercel-connect-adds-enterprise-managed-authorization-88230.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-connect-adds-enterprise-managed-authorization>)

Author: Hedi Zandi

Published: 2026-10-15T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>)

Tags: [authorization](<https://devfeed.tech/tags/authorization.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [consent](<https://devfeed.tech/tags/consent.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [scopes](<https://devfeed.tech/tags/scopes.md>), [slack](<https://devfeed.tech/tags/slack.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Connect has added public beta support for Enterprise-Managed Authorization. It lets apps and agents access supported services on behalf of signed-in users, with administrators managing access through an identity provider and apps requesting scoped tokens. The release also supports Cross-App Access for MCP authorization through EMA.

### Source excerpt

Vercel Connect now supports Enterprise-Managed Authorization (EMA) in public beta. Your apps and agents can access supported services on behalf of signed-in users without separate consent prompts for each service. Here's how access works: Admin-managed access: Administrators can grant or revoke access to supported services through the identity provider. Corporate sign-in: Users sign into your app with their corporate account through a compatible identity provider such as Okta. Scoped tokens: Your app requests the scopes it needs, and Connect handles token exchange, caching, and renewal. Access is limited to approved scopes and the user's existing service permissions. If your app uses Vercel Passport, you can request a token for Slack's Model Context Protocol (MCP) server with the signed-in user's identity: type: embedded-entry-inline id: 1T9cFkjaRDDmRFQ5bWVmD6 Connect supports Cross-App Access (XAA), including its use for MCP authorization through EMA. Follow the Vercel Connect EMA setup guide to configure your identity provider and services and enable EMA on their Connect connectors. Read more

## Retiring Access Verification for Tech Provider Apps

DevFeed: [Retiring Access Verification for Tech Provider Apps](<https://devfeed.tech/articles/retiring-access-verification-for-tech-provider-apps-84376.md>)

Original publisher: [Read original article](<https://developers.facebook.com/blog/post/2026/10/09/retiring-access-verification-for-tech-provider-apps/>)

Published: 2026-10-09T20:00:01Z

Content type: news

Language: en

Sources: [Facebook Developers](<https://devfeed.tech/sources/facebook-developers.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [integration](<https://devfeed.tech/tags/integration.md>), [permissions](<https://devfeed.tech/tags/permissions.md>)

### AI overview

Meta is retiring Access Verification from the Tech Provider onboarding flow for apps that access clients' business data. Business Verification and App Review requirements remain, as do existing data handling obligations.

### Source excerpt

Access Verification will no longer be required in the Tech Provider onboarding flow. If you build apps that access Meta business data owned by your clients, you no longer submit business details for a separate access review.

## Build a Secure TypeScript MCP Client with Cross App Access (XAA)

DevFeed: [Build a Secure TypeScript MCP Client with Cross App Access (XAA)](<https://devfeed.tech/articles/build-a-secure-typescript-mcp-client-with-cross-app-access-xaa-84283.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/10/09/typescript-mcp-sdk-cross-app-access>)

Author: Akanksha Bhasin

Published: 2026-10-09T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [node](<https://devfeed.tech/tags/node.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [npm](<https://devfeed.tech/tags/npm.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oauth-2-0](<https://devfeed.tech/tags/oauth-2-0.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

A TypeScript tutorial builds an MCP requesting app that uses Cross App Access to obtain delegated access to a protected resource. It walks through the OAuth and token exchange steps, explains ID-JAG claims, and configures the MCP TypeScript SDK's CrossAppAccessProvider, including authentication and scope adjustments for the xaa.dev playground.

### Source excerpt

Enterprise apps rarely work alone. Imagine this scenario: HR wants to ensure that a new employee completes their new hire onboarding, and they want this verification in the company's HR app so it's tied to the employee's personnel file. But the onboarding tasks come from a task-tracking tool with requirements defined by each department, from a different vendor and on a different domain than the HR app. It's on IT to bridge the two. Wiring the two together normally costs the user an OAuth consent screen or costs IT a shared service account. Cross App Access (XAA) removes that step. The company's identity provider vouches for the user across the boundary, under a policy the admin sets in advance. In this tutorial, you'll build that flow end-to-end in TypeScript. You'll build a Model Context Protocol (MCP) requesting app: a web app that signs a user in through an enterprise Identity Provider (IdP), exchanges that identity for a delegation token called an Identity Assertion JWT Authorization Grant (ID-JAG), trades the ID-JAG for an access token, and calls a protected MCP server to fetch real data. You'll use the MCP TypeScript SDK, which added first-class Cross App Access support, and you'll test everything against xaa.dev, the free XAA playground from the Okta Dev Advocacy team. By the end of this post, you can: Explain what XAA is and why AI agents and enterprise apps need it Read an ID-JAG and understand key claims in it Understand each step of the XAA flow through the SDK functions Let the SDK's CrossAppAccessProvider run the whole flow for you Prerequisites Node.js 20 or later npm, which ships with Node.js A free xaa.dev registration (email only) Familiarity with OAuth 2.0 concepts. If Proof Key for Code Exchange (PKCE) is new to you, read Secure Your Express App with OAuth 2.0, OIDC, and PKCE first. The code in this tutorial runs against @modelcontextprotocol/client version 2.0.0-alpha.2, openid-client 6, Express 4, and the xaa.dev playground services. The MCP SDK

## Descope Agentic Identity Hub Demo: Access Control, OAuth, and Audit Logs for MCP Agents

DevFeed: [Descope Agentic Identity Hub Demo: Access Control, OAuth, and Audit Logs for MCP Agents](<https://devfeed.tech/articles/the-agentic-identity-hub-61487.md>)

Original publisher: [Read original article](<https://www.developersdigest.tech/tutorials/ZAfvfUlST10>)

Author: Developers Digest

Published: 2026-09-29T01:04:18Z

Content type: tutorial

Language: en

Sources: [Developers Digest](<https://devfeed.tech/sources/developers-digest.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authentication](<https://devfeed.tech/topics/authentication.md>), [OAuth](<https://devfeed.tech/topics/oauth.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-identity](<https://devfeed.tech/tags/agentic-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [audit](<https://devfeed.tech/tags/audit.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

The video demonstrates Descope's Agentic Identity Hub, covering fine-grained access control, OAuth, and audit logs for MCP AI agents.

### Source excerpt

Descope Agentic Identity Hub Demo: Fine-Grained Access Control, OAuth, and Audit Logs for MCP AI Agents Check out Descope: https://descope.plug.dev/inU8swv The video demonstrates Descope's Agentic I...

## Add Cross App Access to Your OIDC Resource Application

DevFeed: [Add Cross App Access to Your OIDC Resource Application](<https://devfeed.tech/articles/add-cross-app-access-to-your-oidc-resource-application-133756.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/24/xaa-oidc-resource/>)

Author: Sohail Pathan

Published: 2026-08-24T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [resource](<https://devfeed.tech/tags/resource.md>), [sso](<https://devfeed.tech/tags/sso.md>), [using](<https://devfeed.tech/tags/using.md>), [with](<https://devfeed.tech/tags/with.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

An OIDC resource authorization server can support Cross App Access by accepting an IdP-issued, short-lived ID-JAG and exchanging it for its own access token, without changing the existing SSO flow. Bind the token's `iss` to a registered IdP before verifying its signature with that connection's JWKS; then check its type, `aud`, and authenticated client's `client_id`. Resolve users by `iss` + `sub` (also `tenant` for a multi-tenant IdP), using `email` only as a just-in-time provisioning hint. Apply local scope policy and issue an access token without a refresh token; clients can resubmit the ID-JAG until it expires. Publish the JWT bearer grant and `id-jag` profile in authorization server metadata, without listing trusted issuers publicly. The walkthrough uses Okta and xaa.dev to test an already implemented resource server: it requires a reachable issuer and token endpoint, client registration and redemption logic, and an API that accepts the issued token. The resource issuer must match the ID-JAG audience exactly. For SAML connections, the subject instead uses `sub_id` in `saml-nameid` format and is matched by its NameID members; the other redemption rules remain the same.

### Source excerpt

Learn how to secure app-to-app connections using Cross App Access (XAA) with OIDC SSO for OIDC-based resource apps.

## Add Cross App Access to Your OIDC Requesting Application

DevFeed: [Add Cross App Access to Your OIDC Requesting Application](<https://devfeed.tech/articles/add-cross-app-access-to-your-oidc-requesting-application-133755.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/08/21/xaa-oidc-requesting/>)

Author: Sohail Pathan

Published: 2026-08-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [all](<https://devfeed.tech/tags/all.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [sso](<https://devfeed.tech/tags/sso.md>), [using](<https://devfeed.tech/tags/using.md>), [with](<https://devfeed.tech/tags/with.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

For an OIDC application to call a third-party API through Cross App Access (XAA), retain the refresh token from the usual authorization code sign-in with `offline_access`. Exchange it at Okta's `/token` endpoint, using OAuth 2.0 Token Exchange and the app's client credentials, to obtain a short-lived ID-JAG. Redeem that assertion at the resource app's authorization server using the JWT bearer grant and that server's required client authentication and scopes; use the returned access token for the API call. Request a new ID-JAG with the same refresh token when it expires; if the refresh token expires or is revoked and Okta returns `invalid_grant`, the user must sign in again. The walkthrough configures Okta requester and test resource integrations, enables XAA with the resource authorization server's issuer URL, registers the requester at xaa.dev, and verifies the exchange and API call there. The example's Basic authorization header is illustrative; use the scheme the resource application requires.

### Source excerpt

Secure app-to-app connections using Cross App Access (XAA) with OIDC SSO for OIDC-federated enterprise apps.

## How to get your app verified for third-party data access

DevFeed: [How to get your app verified for third-party data access](<https://devfeed.tech/articles/how-to-get-your-app-verified-for-third-party-data-access-80798.md>)

Original publisher: [Read original article](<https://lovable.dev/blog/how-to-get-your-app-verified-for-third-party-data-access>)

Author: Kamaria Wilson

Published: 2026-08-20T08:00:00Z

Content type: tutorial

Language: en

Sources: [Lovable](<https://devfeed.tech/sources/lovable.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [zero trust network access](<https://devfeed.tech/topics/zero-trust-network-access.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [ai](<https://devfeed.tech/tags/ai.md>), [apis](<https://devfeed.tech/tags/apis.md>), [article](<https://devfeed.tech/tags/article.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

A practical guide to preparing a Lovable app that connects to users' third-party data for provider review, using Google OAuth as its example. It explains how to determine whether review is needed, request scopes that match visible features, prepare customer-facing materials and a walkthrough, submit the app, and manage changes and reassessments after approval.

### Source excerpt

How to navigate provider review when your Lovable app connects to users' third-party data, using one builder's Google OAuth verification as the example.

## Okta Cross App Access (XAA / ID-JAG) in Nirmata AIControls: standards-based authorization for AI agents

DevFeed: [Okta Cross App Access (XAA / ID-JAG) in Nirmata AIControls: standards-based authorization for AI agents](<https://devfeed.tech/articles/okta-cross-app-access-xaa-id-jag-in-nirmata-aicontrols-standards-based-authorization-for-ai-agents-17657.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/08/18/okta-cross-app-access-xaa-id-jag/>)

Author: Ritesh Patel

Published: 2026-08-19T00:24:40Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [OAuth 2.0](<https://devfeed.tech/topics/oauth2.md>), [okta](<https://devfeed.tech/topics/okta.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [app](<https://devfeed.tech/tags/app.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [call](<https://devfeed.tech/tags/call.md>), [code](<https://devfeed.tech/tags/code.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [it](<https://devfeed.tech/tags/it.md>), [llm](<https://devfeed.tech/tags/llm.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [need](<https://devfeed.tech/tags/need.md>), [okta](<https://devfeed.tech/tags/okta.md>), [policy](<https://devfeed.tech/tags/policy.md>), [post](<https://devfeed.tech/tags/post.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [standards](<https://devfeed.tech/tags/standards.md>), [this](<https://devfeed.tech/tags/this.md>), [token](<https://devfeed.tech/tags/token.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Okta's Cross App Access uses the ID-JAG draft to let an enterprise administrator authorize an agent's access on a user's behalf, without per-user consent screens. In the described flow, an RFC 8693 token exchange at the enterprise IdP creates a short-lived, single-audience identity assertion; the resource's authorization server exchanges it under RFC 7523 for a scoped access token. Nirmata AIControls performs these exchanges for agents that do not understand ID-JAG, and can also act as the authorization server protecting MCP servers and LLM endpoints. It CEL-policy-checks and budgets delegated calls, then records them in an audit trail attributed to the delegating human. The excerpt presents ID-JAG as an active Internet-Draft and does not provide further implementation details.

### Source excerpt

AIControls now performs the ID-JAG token exchanges on your agents' behalf -- so agents need no protocol code -- and policy-checks, budgets, and attributes every delegated MCP and LLM call to the human it acts for. ID-JAG answers may this agent act for this user? AIControls answers what... The post Okta Cross App Access (XAA / ID-JAG) in Nirmata AIControls: standards-based authorization for AI agents first appeared on Nirmata.

## Enable Your SAML Requesting App for Cross App Access

DevFeed: [Enable Your SAML Requesting App for Cross App Access](<https://devfeed.tech/articles/enable-your-saml-requesting-app-for-cross-app-access-133752.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/17/xaa-saml-requester/>)

Author: Alisa Duncan

Published: 2026-07-17T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [saml](<https://devfeed.tech/topics/saml.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

A SAML app can use Okta Cross App Access (XAA) without migrating to OIDC by exchanging credentials in three stages: after validating the SAML response, exchange its XML assertion for a long-lived refresh token; use that token to obtain a short-lived ID-JAG from Okta for the resource app's issuer, API URL, and scopes; then redeem the ID-JAG at the resource app's authorization server for an access token. The first two exchanges require a private-key JWT client assertion; the final server uses its required client authentication scheme. Persist the refresh token for the session, never retain the SAML assertion, and obtain a new ID-JAG when it expires. If the refresh token expires and Okta returns `invalid_grant`, the user must sign in through SSO again. The guide also walks through configuring Okta's requester and resource SAML apps, enabling XAA, registering an AI agent and resource connection, and checking the flow with xaa.dev. XAA is described as an early access feature.

### Source excerpt

Secure app-to-app connections using Cross App Access (XAA) with SAML SSO for SAML-based enterprise apps.

## Build a Secure C# MCP App with Cross App Access (XAA)

DevFeed: [Build a Secure C# MCP App with Cross App Access (XAA)](<https://devfeed.tech/articles/build-a-secure-c-mcp-app-with-cross-app-access-xaa-15971.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/16/csharp-mcp-cross-app-access>)

Author: Aasawari Sahasrabuddhe

Published: 2026-07-16T05:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [build](<https://devfeed.tech/tags/build.md>), [building](<https://devfeed.tech/tags/building.md>), [but](<https://devfeed.tech/tags/but.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [client](<https://devfeed.tech/tags/client.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [csharp](<https://devfeed.tech/tags/csharp.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [with](<https://devfeed.tech/tags/with.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets an AI agent carry a user's identity to downstream services under enterprise policy without another login. The described flow uses RFC 8693 for the app to exchange an OIDC ID token with the enterprise Identity Provider for a JWT Authorization Grant (JAG), then RFC 7523 for presenting that JAG to the MCP authorization server to obtain a scoped access token. The article excerpt says it will implement the flow with a C# MCP SDK and test it using an XAA playground, but does not include those implementation steps.

### Source excerpt

A few years ago, getting a user signed in to an application or multiple applications with Single Sign-On (SSO) was enough; OpenID Connect (OIDC) handled the login, JWTs carried the claims, and Proof Key for Code Exchange (PKCE) made it secure. Today, with evolving AI, agents act on behalf of users and seek multiple accesses across different resources to execute a task. And that is when you'll hit the gap. The user has an identity, but the downstream service--like a Model Context Protocol (MCP) server, an API, or an agent tool has no way to trust it: the ID Token that proves the user's identity for your app, not for that service. You need a way to take that identity and have it trusted further down the chain, in line with the org's policy, without asking the user to log in again. Cross App Access (XAA) solves exactly that. The user authenticates once. The Identity Provider (IdP) evaluates the enterprise policy and issues a signed Identity Assertion. The downstream service exchanges that assertion for a scoped Bearer token. In this post, we'll explore how Cross App Access (XAA) closes the trust gap, test the flow using an XAA playground, and implement a secure MCP client in just a few lines of C# using our dedicated SDK. Table of Contents What is Cross App Access (XAA)? Implementing XAA with the C# MCP SDK Building the OIDC flow Automate XAA token exchange with C# SDK Connect the MCP client to the server Testing your C# MCP app with xaa.dev Run your C# MCP app with xaa.dev Learn More About Secure AI Agent Development with C# and MCP What is Cross App Access (XAA)? Before we start implementing and building the application, it is important to understand the mechanics of Cross App Access (XAA). At its core, XAA is an open standard that securely enables AI agents to act on behalf of a user and communicate with downstream applications without requiring constant, manual user consent. While the flow is sophisticated, it relies on two standard interactions: RFC 8693 (Token Exc

## Build a Secure C# MCP App with Cross App Access (XAA)

DevFeed: [Build a Secure C# MCP App with Cross App Access (XAA)](<https://devfeed.tech/articles/build-a-secure-c-mcp-app-with-cross-app-access-xaa-133751.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/16/csharp-mcp-cross-app-access/>)

Author: Aasawari Sahasrabuddhe

Published: 2026-07-16T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [api](<https://devfeed.tech/tags/api.md>), [asp-net](<https://devfeed.tech/tags/asp-net.md>), [asp-net-core](<https://devfeed.tech/tags/asp-net-core.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bearer-token](<https://devfeed.tech/tags/bearer-token.md>), [building](<https://devfeed.tech/tags/building.md>), [c-sharp](<https://devfeed.tech/tags/c-sharp.md>), [client](<https://devfeed.tech/tags/client.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [csharp](<https://devfeed.tech/tags/csharp.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [net](<https://devfeed.tech/tags/net.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oidc](<https://devfeed.tech/tags/oidc.md>), [token-exchange](<https://devfeed.tech/tags/token-exchange.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets a C# app use a signed identity assertion to obtain scoped access to an MCP server on a user's behalf, without another login. The article describes two exchanges: RFC 8693 exchanges the user's OIDC ID token for a short-lived JWT Authorization Grant at the enterprise identity provider; RFC 7523 exchanges that grant at the MCP authorization server for a scoped access token. The C# MCP SDK's `IdentityAssertionGrantProvider` wraps both exchanges. The example configures ASP.NET Core OIDC with PKCE, passes the session ID token through `IdTokenCallback`, and uses the resulting bearer token with `HttpClientTransport` to initialize an MCP client and read resources. For testing, register the requester app and ToDo MCP resource at xaa.dev, configure the supplied client credentials and endpoints, then run the sample locally. The excerpt presents xaa.dev as a ready-made test environment.

### Source excerpt

Learn how to build a secure C# MCP client using Cross App Access (XAA) and token exchange so AI agents can securely act on behalf of users.

## Build, Test, and Publish a Cross App Access App in the Okta Integration Network

DevFeed: [Build, Test, and Publish a Cross App Access App in the Okta Integration Network](<https://devfeed.tech/articles/build-test-and-publish-a-cross-app-access-app-in-the-okta-integration-network-133749.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/06/submit-oin-xaa/>)

Author: Gagan Sikri

Published: 2026-07-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [build](<https://devfeed.tech/tags/build.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [free](<https://devfeed.tech/tags/free.md>), [guide](<https://devfeed.tech/tags/guide.md>), [integration](<https://devfeed.tech/tags/integration.md>), [isv](<https://devfeed.tech/tags/isv.md>), [it](<https://devfeed.tech/tags/it.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [network](<https://devfeed.tech/tags/network.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [oin](<https://devfeed.tech/tags/oin.md>), [okta](<https://devfeed.tech/tags/okta.md>), [server](<https://devfeed.tech/tags/server.md>), [sso](<https://devfeed.tech/tags/sso.md>), [test](<https://devfeed.tech/tags/test.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets an app request data from another vendor's API for a signed-in enterprise user without static API keys or a separate consent prompt for each connection. The flow involves a requesting app exchanging an identity assertion for an Identity Assertion Authorization Grant (ID-JAG), a resource app validating it and issuing a scoped access token, and an identity provider such as Okta handling authentication, policy evaluation, and ID-JAG validation. To implement XAA, developers need an Okta Integrator Free Plan org and must identify their app's XAA role (requesting app, resource app, or both) and SSO protocol (OIDC, SAML, or both); MCP clients are requesting apps and MCP servers are resource apps in the described use cases. They then follow the implementation guide matching role and protocol, test with Okta's developer tools, and submit through the OIN Wizard from the same org. An OIN listing is free and must cover both SSO and XAA. Okta's initial review takes about one business week, with publication shortly afterward.

### Source excerpt

Build Cross App Access into your app or MCP server, test it with Okta's developer tools, and publish it free to the Okta Integration Network.

## Enabling Cross App Access for SAML-Based Resource Apps

DevFeed: [Enabling Cross App Access for SAML-Based Resource Apps](<https://devfeed.tech/articles/enabling-cross-app-access-for-saml-based-resource-apps-133748.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/07/03/cross-app-access-saml/>)

Author: Sohail Pathan

Published: 2026-07-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [saml](<https://devfeed.tech/topics/saml.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [resource](<https://devfeed.tech/tags/resource.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sso](<https://devfeed.tech/tags/sso.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

The guide explains how SAML-based resource apps can support Cross App Access without changing their existing SAML federation. The resource authorization server receives an ID-JAG JWT, binds its issuer to a registered SAML connection before verifying the signature, checks its type, audience and client ID, then resolves the user from `sub_id` in `saml-nameid` format. User matching should include the SAML issuer, NameID and `sp_name_qualifier`; NameID alone may not be unique, and it should not be assumed to be an email. After applying local scope policy, the server issues its own access token and should not issue a refresh token: the client can resubmit the ID-JAG until it expires. The guide also requires advertising the JWT bearer grant and ID-JAG profile in authorization server metadata, and provides an Okta and xaa.dev setup and conformance-testing walkthrough.

### Source excerpt

Learn how to secure app-to-app connections using Cross App Access (XAA) with SAML SSO for SAML-based resource apps.

## Okta Developer Connect San Francisco 2026 Recap

DevFeed: [Okta Developer Connect San Francisco 2026 Recap](<https://devfeed.tech/articles/okta-developer-connect-san-francisco-2026-recap-133744.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/06/09/okta-developer-connect-sf-recap/>)

Author: Akanksha Bhasin

Published: 2026-06-09T00:00:00Z

Content type: news

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [okta](<https://devfeed.tech/topics/okta.md>), [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>), [Auth0](<https://devfeed.tech/topics/auth0.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [access-requests](<https://devfeed.tech/tags/access-requests.md>), [actions](<https://devfeed.tech/tags/actions.md>), [age-of-ai](<https://devfeed.tech/tags/age-of-ai.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [connect](<https://devfeed.tech/tags/connect.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [developer](<https://devfeed.tech/tags/developer.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [enterprise-ai-agents](<https://devfeed.tech/tags/enterprise-ai-agents.md>), [identity](<https://devfeed.tech/tags/identity.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [okta](<https://devfeed.tech/tags/okta.md>), [okta-for-ai-agents](<https://devfeed.tech/tags/okta-for-ai-agents.md>), [patterns](<https://devfeed.tech/tags/patterns.md>), [recap](<https://devfeed.tech/tags/recap.md>), [san-francisco](<https://devfeed.tech/tags/san-francisco.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

At Okta Developer Connect San Francisco, Okta announced the general availability of Okta for AI Agents, which the article describes as providing cross-environment agent discovery, short-lived and scoped credentials, secret vaulting, access controls for MCP servers, lifecycle governance, SIEM audit logs, and a kill switch. A Cross App Access session showed how an enterprise identity provider can mediate app-to-app access through policy, identity assertion, and token exchange instead of relying on repeated user consent. For AI applications, the recommended patterns were to preserve the user's identity in the authorization chain, keep long-lived third-party credentials in a Token Vault, support out-of-band approval for sensitive actions, and enforce fine-grained permissions at the data layer. The recap identifies gaps between fast agent deployment and slower governance, static credentials, and RAG permission enforcement as recurring concerns; it presents agents as identities needing ownership, review, scope, and revocation.

### Source excerpt

A recap of Okta Developer Connect San Francisco 2026: Cross App Access, Okta for AI Agents, and identity patterns for securing enterprise AI agents.

## Make Secure App-to-App Connections Using Cross App Access

DevFeed: [Make Secure App-to-App Connections Using Cross App Access](<https://devfeed.tech/articles/make-secure-app-to-app-connections-using-cross-app-access-133741.md>)

Original publisher: [Read original article](<https://developer.okta.com/blog/2026/02/10/xaa-client/>)

Author: Alisa Duncan

Published: 2026-02-10T00:00:00Z

Content type: tutorial

Language: en

Sources: [Okta Developer](<https://devfeed.tech/sources/okta-developer.md>)

Topics: [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [cross-app-access](<https://devfeed.tech/tags/cross-app-access.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [extension](<https://devfeed.tech/tags/extension.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [xaa](<https://devfeed.tech/tags/xaa.md>)

### AI overview

Cross App Access (XAA) lets an enterprise identity provider broker app-to-app authorization, giving admins control over connections and limiting access by user and task. The tutorial implements the flow in a NestJS and TypeScript note-taking app using `openid-client` and xaa.dev: after user sign-in yields an ID token, the app exchanges it with the IdP for an ID-JAG token, then presents that token to the to-do app's authorization server using the JWT bearer grant to obtain an access token for its API. It requires Node.js 22 or higher, Git, an editor and terminal, familiarity with TypeScript and OAuth/OIDC, and client credentials for both apps. xaa.dev supplies a self-contained, IdP-agnostic test environment, so the tutorial does not require a real IdP account or conformant resource app.

### Source excerpt

Secure enterprise integrations with Cross App Access (XAA). Implement this OAuth extension for compliant app-to-app connectivity.

## Enterprise Managed User account emails are no longer automatically verified

DevFeed: [Enterprise Managed User account emails are no longer automatically verified](<https://devfeed.tech/articles/enterprise-managed-user-account-emails-are-no-longer-automatically-verified-73018.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2024-08-01-enterprise-managed-user-accounts-now-require-email-verification>)

Author: Allison

Published: 2024-08-01T20:12:52Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [cross-app-access](<https://devfeed.tech/topics/cross-app-access.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>)

Tags: [account-security](<https://devfeed.tech/tags/account-security.md>), [applications](<https://devfeed.tech/tags/applications.md>), [identity-provider](<https://devfeed.tech/tags/identity-provider.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

GitHub says Enterprise Managed User account emails are no longer automatically verified, a change intended to prevent unauthorized access and accidental data leaks involving third-party apps that relied on email as a primary identifier. Existing accounts generally do not need to verify again unless their email conflicts with one on another GitHub.com account. Some third-party apps may require email reverification or may not handle placeholder addresses correctly.

### Source excerpt

March 20, 2025 update To clarify the exact impact of this change, we've updated the title and the wording we used in this changelog. Previously it was titled "Enterprise Managed...

[Next page](<https://devfeed.tech/topics/cross-app-access.md?cursor=WyIyMDI0LTA4LTAxVDIwOjEyOjUyKzAwOjAwIiwgImY4ZjljOTJhLWE0YzgtNDFmOC1iMGQyLTJhZmRiNWE3ZjdmOSJd>)