Skip to navigation

JWT Auth plugin

The JWT Auth plugin identifies the caller from a signed JSON Web Token (JWT) that your identity provider issued. The instance names the provider. The provider supplies the signing keys, the issuer and audience checks, and the claim that names the consumer. The plugin also reads claims into an agent identity, which the agent plugins use.

JWT Auth isn’t available when Postman hosts your data plane. For more information, see Choose a deployment model.

Where it runs

ProtocolsHTTP, LLM, and MCP routes
Scope kindsglobal, service, route
PhaseAuthentication, before other request plugins

Configuration

FieldTypeDefaultDescription
providerstringNoneThe identity provider that issues the tokens.
token_sourcesarray of objectsAuthorization header with scheme BearerWhere to read the token, in order. Each entry has type (header or cookie), name, and an optional scheme. A header other than Authorization has no scheme by default.
subject_claimstringsubThe claim for the subject.
principal_claimstringprincipalIdThe claim for the principal.
kind_claimstringuser_typeThe claim that marks the caller as an agent. The values bot, agent, and service mean an agent.
scopes_claimstringscopesThe claim that holds the caller’s scopes, as a space-separated string or a list.
tenant_claimstringteamIdThe claim for the caller’s team.
user_claimstringuserIdThe claim for the user.
session_claimstringjtiThe claim for the session.
consumer_type_claimstringconsumerTypeThe claim for the consumer type. The value autonomous_agent also means an agent.
installation_claimstringinstallationUidThe claim for the installation.

The claim fields fill the agent identity. They don’t change whether the gateway accepts the token. The gateway allows 60 seconds of clock skew by default.

Example

{
"name": "jwt-auth-mcp",
"plugin_id": "jwt-auth",
"scope": { "kind": "route", "name": "linear-mcp" },
"config": {
"provider": "okta-workforce",
"token_sources": [{ "type": "header", "name": "Authorization", "scheme": "Bearer" }]
}
}