Identity / Enterprise Managed Auth
Enterprise Managed Auth
Use your IDP as the authority for AI access: agents reach Speakeasy with an identity assertion from your IDP, and Speakeasy reaches your services as each person, with no per-service connect step.
Enterprise Managed Auth makes the identity provider (IDP) the authority for which agents reach which MCP servers, and as whom. A person signs in to the IDP once. After that, every token the agent and the platform need is a short-lived token that the IDP issues from that sign-in, scoped to one server and one person. No agent holds a standing API key, and no person connects each service by hand.
The platform implements the MCP Enterprise Managed Authorization (EMA) extension. Some identity providers call the same protocol Cross App Access (XAA).
This guide is Okta-first. Reach out to the Speakeasy team for support with other IDPs.
Why Enterprise Managed Auth
Section titled “Why Enterprise Managed Auth”Without Enterprise Managed Auth, each person signs in to every system their agent reaches: once to reach Speakeasy, then again the first time the agent uses Linear, Notion, or Slack. Each of those sign-ins leaves a separate grant that is reviewed and revoked in a separate place.
With Enterprise Managed Auth, the person signs in to Okta once. The agent uses that sign-in to get its Speakeasy token, and Speakeasy uses it to get each service’s token, without opening a browser.
- One policy point. Okta decides which people and agents reach which servers, using the same assignments, MFA, and conditional access policies as the rest of the organization.
- Short-lived, scoped tokens. Each token is addressed to one server and expires on its own. Nothing long-lived is copied into an agent’s configuration.
- One place to revoke. Unassigning a person or removing a resource connection in Okta stops new tokens for every server that depends on it.
- Open standards. The flow uses OAuth token exchange and the JWT bearer grant, so any authorization server that implements EMA can verify the tokens.
The diagrams follow one person using Claude with Linear, Notion, and Slack. With With EMA selected, select Speakeasy sets up sessions to see what happens inside it.
You stop and sign in four times before Claude can use Linear, Notion, and Slack. Each service asks the first time Claude calls one of its tools.
How a token is issued
Section titled “How a token is issued”Every Enterprise Managed Auth exchange follows the same four steps, whether the agent asks for a Speakeasy token or the platform asks for a service token.
- Sign in. The person signs in to Okta through OpenID Connect (OIDC). Okta returns an ID token.
- Exchange. The requester sends the ID token to Okta and names the server it wants to reach. Okta checks that the person is assigned and that the requester has a resource connection for that server. If both hold, Okta returns an Identity Assertion JWT Authorization Grant (ID-JAG): a short-lived, signed token addressed to that server’s authorization server.
- Redeem. The requester presents the ID-JAG to the server’s authorization server. The authorization server checks the signature against Okta’s published keys and returns an access token.
- Call. The requester calls the MCP server with the access token, acting as the person.
Two directions
Section titled “Two directions”The platform plays a different role in each direction. For agents, it is the authorization server that accepts ID-JAGs. For services, it is the requester that asks Okta for them. Set up either direction, or both.
Connect your agents to Speakeasy
InboundTrust Okta as an issuer. Agents present an Okta identity assertion (ID-JAG) to the platform and reach MCP servers as the person they act for, with no browser sign-in.
Learn moreConnect Speakeasy to your services
OutboundRegister the Speakeasy AI agent in Okta. The platform exchanges each person's Okta identity for a token at Linear, Notion, and other services, with no per-service connect step.
Learn more| Agents to Speakeasy | Speakeasy to services | |
|---|---|---|
| Who asks Okta | The agent | The platform, as the Speakeasy AI agent |
| Who accepts the ID-JAG | The MCP server’s authorization server in the platform | The service’s own authorization server |
| Dashboard setup | A sign-in issuer that trusts Okta | The Okta sign-in, then Turn on per server |
| Okta setup | Speakeasy as a Cross App Access resource for the agent | A resource connection per service on the Speakeasy AI agent |
| What the service must do | Nothing | Support Enterprise Managed Authorization and trust your Okta org |
Both directions share the Okta connection and the same rule for people: each person must already be a member, provisioned through directory sync. Nobody is created at sign-in.
Connect Okta
Section titled “Connect Okta”Both directions start with the Okta connection, a read-only API service app that lets the platform read your Okta apps and their assignments. Connect Okta covers the prerequisites, the supported scope, and the steps in Okta and in the dashboard.
Where policy applies
Section titled “Where policy applies”- At issuance. Okta evaluates assignments and resource connections when it issues an ID-JAG. An ID-JAG works once and expires within minutes.
- After issuance. The access token the authorization server returns stays valid until it expires. For agents reaching Speakeasy, that is one hour, and the platform still checks that the person holds
mcp:connecton the server. - On revocation. Deactivating a person in Okta, unassigning them, or removing a resource connection makes Okta refuse the next exchange. Tokens already issued keep working until they expire.
| Term | Meaning |
|---|---|
| Enterprise Managed Authorization (EMA) | The MCP authorization extension that lets an identity provider issue tokens for MCP servers on a person’s behalf |
| Cross App Access (XAA) | The name Okta uses for the same protocol |
| ID token | The OIDC token Okta returns when a person signs in. It proves who the person is, not what they can reach |
| Identity Assertion JWT Authorization Grant (ID-JAG) | The short-lived JWT Okta issues for one person, one requester, and one server. Its aud is that server’s authorization server |
| Token exchange | The OAuth grant (urn:ietf:params:oauth:grant-type:token-exchange) that trades an ID token for an ID-JAG at Okta |
| JWT bearer grant | The OAuth grant (urn:ietf:params:oauth:grant-type:jwt-bearer) that trades an ID-JAG for an access token at an authorization server |
| Resource connection | The Okta setting that allows one agent to request ID-JAGs for one resource |
| Sign-in issuer | The platform setting that decides how people sign in to an MCP server. An organization-level issuer can trust Okta |
Limitations
Section titled “Limitations”- Okta is the only supported identity provider.
- Enterprise Managed Auth acts for people. For agents acting on their own, see Agent identity.
- Revocation in Okta stops new exchanges. Tokens already issued stay valid until they expire.
Related
Section titled “Related”- Authorization servers, where Okta and each service’s authorization server are configured
- User sessions, for sign-in issuers, the consent screen, and token lifetimes
- Upstream credentials, for the per-user and shared credential modes Enterprise Managed Auth complements
- IDP and SSO, for employee sign-in and directory sync