bugfix: Non-empty paths in OAuth2 Authorization Server Metadata URLs #441
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
github-actions
bot
added
T-core
pnehrer
force-pushed
the
pnehrer/dcr-discovery
branch
from
e7cd98f to
33cc116
Compare
pnehrer
force-pushed
the
pnehrer/dcr-discovery
branch
from
33cc116 to
37f394a
Compare
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.
When constructing an OAuth2 Authorization Server Metadata URL from the MCP server URL, consider the resource URL path as required in the RFC.
Motivation and Context
This is requiired for MCP servers that use resource-specific authorization servers.
How Has This Been Tested?
Using the example DCR client.
Breaking Changes
None.
Types of changes
Checklist
Additional context
N/A