fix(client): detect authorization-server migration from fresh PRM#2450
Open
mattzcarey wants to merge 1 commit into
Open
fix(client): detect authorization-server migration from fresh PRM#2450mattzcarey wants to merge 1 commit into
mattzcarey wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: e4de221 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/core
@modelcontextprotocol/server
@modelcontextprotocol/server-legacy
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
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
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.
Previously unaddressed
#2358 isolated credentials by issuer once the current authorization server was known, but cached discovery could keep the client pinned to AS-A after a fresh
resource_metadatachallenge selected AS-B. Existing tests had to clear discovery manually before migration was detected.This PR
Verification
pnpm check:allpnpm build:allFollow-up to #2271, #2358, and #2286.