Bump auth SDK to use Improved AS Discovery #702
Merged
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.
Bump the MCP SDK pin from
^1.17.0
to^1.17.2
, to update the debugger to the latest AS metadata endpoint discovery method (discoverAuthorizationServerMetadata
introduced in modelcontextprotocol/typescript-sdk#652) and include the CORS retry bug fix introduced in1.17.2
(modelcontextprotocol/typescript-sdk#827).Motivation and Context
Needed to connect Inspector's auth debugger to MCP servers that use Azure for AS. Needed support for metadata at
/.well-known/openid-configuration
, and needed CORS fix so it didn't fail on earlier attempted incorrect endpoints.How Has This Been Tested?
Run all tests locally (and needed to update the mocks to the new method).
As tests were changed, also manually tested against an OOB MCP server (Neon's) and a custom one using Azure AD.
Breaking Changes
Types of changes
Checklist
Related Issues
I suspect this will resolve these issues that are all related to metadata:
openid-configuration
not justoauth-authorization-server
#563