feat(auth): add subject field to AccessToken#2446
Open
Sagargupta16 wants to merge 1 commit intomodelcontextprotocol:mainfrom
Open
feat(auth): add subject field to AccessToken#2446Sagargupta16 wants to merge 1 commit intomodelcontextprotocol:mainfrom
Sagargupta16 wants to merge 1 commit intomodelcontextprotocol:mainfrom
Conversation
Add an optional `subject` field to `AccessToken` to store the JWT `sub` claim (user ID). This allows token verifiers to pass through user identity without requiring consumers to re-decode the JWT. Backward compatible - field defaults to None. Fixes modelcontextprotocol#1038
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Add an optional
subjectfield toAccessTokenfor storing the JWTsubclaim (user ID).Motivation
Currently, token verifiers that decode JWTs have no standard way to pass through the subject/user identity. Consumers must re-decode the JWT to retrieve
sub, duplicating work.With this change:
Then downstream code can access the user ID directly:
Changes
subject: str | None = NonetoAccessTokeninprovider.pyBackward compatible - field defaults to
None.Fixes #1038