[auth] adjust default validation for resource parameter in client flow, and server example #664
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.
Motivation and Context
In the previous PR, we required strict matching for
resource
parameter between the requested server url likehttps://mcp.example.com/mcp
so we would fail if the metadata suggested a resource ofhttps://mcp.example.com
. However, the server is free to define the resource it wants to request, and will be the one checking on the server end, so if the resource metadata says a hierarchically lower URL, then we should use that instead of the more specific one, and not reject it.This also exposes
selectResource
function, to make it easier to leverage in e.g. auth debugger.How Has This Been Tested?
Added more tests
Breaking Changes
This should be more lenient, so not a breaking change.
Types of changes
Checklist
Additional context