modelcontextprotocol/ext-auth
Watch
1
0
Fork
You've already forked ext-auth
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #23 from max-stytch/patch-1

Browse source 
Correct reference from MCP server to MCP Client
This commit is contained in:
Den Delimarsky 2026-03-22 22:46:15 -07:00 • committed by GitHub
commit aae001d942
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
specification/draft/enterprise-managed-authorization.mdx
View file

@ -98,7 +98,7 @@ Location: https://acme.idp.example/authorize?response_type=code&scope=openid&cli
The user authenticates with the IdP, and is redirected back to the Client with an authorization code, which it can then exchange for an ID Token.
The enterprise IdP may enforce additional security controls such as multi-factor authentication before granting the user access to the MCP Client.
For example, in an OpenID Connect flow, after receiving a redirect from the IdP with an authorization code, the MCP server makes a request to the Authorization Server and, if valid, receives the tokens in the response:
For example, in an OpenID Connect flow, after receiving a redirect from the IdP with an authorization code, the MCP Client makes a request to the Authorization Server and, if valid, receives the tokens in the response:
```
POST /token HTTP/1.1