-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Implement RFC9728 - Support WWW-Authenticate header by MCP client #1071
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
pcarleton
merged 12 commits into
modelcontextprotocol:main
from
yurikunash:RFC9728_www-authentication
Jul 15, 2025
Merged
Changes from 9 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
cfb3f7e
Added method for parsing WWW-Authenticate header
yurikunash 41b3d91
Update async_auth_flow
yurikunash dd0902e
Check for WWW-Authenticate header
yurikunash b7e88d8
Added unit-tests
yurikunash 2bc58db
Liniting issues fixed
yurikunash 2709b97
Merge branch 'main' into RFC9728_www-authentication
yurikunash 800ffa8
Merge branch 'main' into RFC9728_www-authentication
yurikunash d4a569b
Merge branch 'main' into RFC9728_www-authentication
yurikunash 5165c54
Merge branch 'main' into RFC9728_www-authentication
yurikunash 8e210ac
Merge remote-tracking branch 'upstream/main' into RFC9728_www-authent…
yurikunash 556eebd
Fix type checking issue
yurikunash 2c1c35d
Try refresh token first
yurikunash File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I agree with this part... if we know our current tokens are invalid, and we know we can refresh them, shouldn't we do that before sending a request we know is going to 401?
I think that would mean moving this
if/else
block ahead of line 526 where we yield request.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the suggestion @pcarleton
I was hesitant about it, so I implemented the "try first" approach, as it seemed more reliable.
As this article states, it's also perfectly fine to have that kind of optimization and refresh the token preemptively, so I updated the code as you proposed.