| MCP authorization spec, revision 2026-07-28 |
Protected Resource Metadata, resource indicators, audience validation, no token passthrough. Current revision as of 2026-09-26. |
| draft-ietf-oauth-spiffe-client-auth |
JWT-SVID as OAuth client assertion. Checked against -02: assertion type urn:ietf:params:oauth:client-assertion-type:jwt-spiffe, metadata value spiffe_jwt, issuer as sole SVID audience. |
| RFC 8707: Resource Indicators for OAuth 2.0 |
resource parameter, audience-bound tokens |
| RFC 9728: OAuth 2.0 Protected Resource Metadata |
/.well-known/oauth-protected-resource on the MCP server |
| RFC 9068: JWT Profile for OAuth 2.0 Access Tokens |
Access token format, typ at+jwt |
| RFC 8414: OAuth 2.0 Authorization Server Metadata |
/.well-known/oauth-authorization-server on authz |
| RFC 6749: The OAuth 2.0 Authorization Framework |
client_credentials, error codes, scope syntax, no repeated parameters |
| RFC 6750: Bearer Token Usage |
WWW-Authenticate challenges, insufficient_scope |
| SPIFFE |
Workload identity, SPIFFE ID, JWT-SVID, Workload API |
| SPIRE |
SPIFFE implementation used by the demo (1.15.3) |
| py-spiffe |
Python Workload API client (spiffe package) |
| Model Context Protocol Python SDK |
MCP server and client (mcp 2.x) |