From 800c795a124cd55a75765e48c0de328390e4d556 Mon Sep 17 00:00:00 2001 From: Koichi ITO Date: Sat, 25 Oct 2025 01:43:56 +0900 Subject: [PATCH] Fix incorrect link label The specification for "OAuth 2.0 Token Exchange" is RFC 8693. https://datatracker.ietf.org/doc/html/rfc8623 refers to a different specification, so the current link is correct. This PR fixes the incorrect link label. --- specification/draft/enterprise-managed-authorization.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/draft/enterprise-managed-authorization.mdx b/specification/draft/enterprise-managed-authorization.mdx index 5f5d11b..f07f4b1 100644 --- a/specification/draft/enterprise-managed-authorization.mdx +++ b/specification/draft/enterprise-managed-authorization.mdx @@ -38,7 +38,7 @@ This profile is an application of the "Identity Assertion Authorization Grant" [ The Identity Assertion Authorization Grant follows three steps: 1. Single Sign-On to the MCP Client via OpenID Connect or SAML -2. Token Exchange ([RFC8623](https://datatracker.ietf.org/doc/html/rfc8693)) +2. Token Exchange ([RFC8693](https://datatracker.ietf.org/doc/html/rfc8693)) 3. JWT Authorization Grant ([RFC7523](https://datatracker.ietf.org/doc/html/rfc7523)) The core flow is as follows: