Correctly construct resource_metadata per RFC 9728 Section 3.1 #2203
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
The resource_metadata parameter in WWW-Authenticate header must contain the full URL to the metadata endpoint, formed by inserting /.well-known/oauth-protected-resource between the host and path. Examples: - Resource: http://localhost:8080 Metadata: http://localhost:8080/.well-known/oauth-protected-resource - Resource: http://localhost:9090/mcp Metadata: http://localhost:9090/.well-known/oauth-protected-resource/mcp This enables clients to discover OAuth metadata for the protected resource. Fixes #2202
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2203 +/- ##
==========================================
+ Coverage 53.06% 53.14% +0.07%
==========================================
Files 222 222
Lines 28916 28926 +10
==========================================
+ Hits 15345 15372 +27
+ Misses 12431 12410 -21
- Partials 1140 1144 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ChrisJBurns
approved these changes
Oct 14, 2025
JAORMX
approved these changes
Oct 15, 2025
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.
The resource_metadata parameter in WWW-Authenticate header must contain the full URL to the metadata endpoint, formed by inserting /.well-known/oauth-protected-resource between the host and path.
Examples:
Resource: http://localhost:8080 Metadata: http://localhost:8080/.well-known/oauth-protected-resource
Resource: http://localhost:9090/mcp
Metadata: http://localhost:9090/.well-known/oauth-protected-resource/mcp
This enables clients to discover OAuth metadata for the protected resource.
Fixes #2202