Feat: Add RFC 7523 (JWT Bearer Grant) support #875
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ZachGerman
force-pushed
the
RFC-7523-support
branch
4 times, most recently
from
7092743 to
1094286
Compare
ZachGerman
force-pushed
the
RFC-7523-support
branch
from
4d5cad5 to
c598a2f
Compare
felixweinberger
force-pushed
the
main
branch
from
0845a57 to
c94ba4b
Compare
Author
|
@pcarleton @felixweinberger Any review possible for this some time soon? |
|
Considering the recent change (the spec is now part of ext-auth). We took the approach to have this in mcp.client.auth.extensions.client_credentials in the python SDK to highligh the "extension". I think this might be wise to find a similar way for typescript sdk |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for JWT Credentials passed to the OAuthClientProvider.
Also added a JWT OAuth client in the examples directory.
Motivation and Context
This provides support for machine-to-machine auth.
How Has This Been Tested?
Tested E2E via Auth0.
Breaking Changes
codeVerifierfor token exchange, but I'm pretty sure it's desirable behavior since PKCE is required per MCP spec.Types of changes
Checklist
Additional context
Draft until tested end-to-end.Tested E2E via Auth0.Bloated jwt-utils, as I was oiriginally going to add it to the built-in AS, but did a 180. Leaving it as-is in case someone wants to add built-in AS support for JWT.