Repository navigation
Conversation
|
@modelcontextprotocol/client
@modelcontextprotocol/codemod
@modelcontextprotocol/core
@modelcontextprotocol/server
@modelcontextprotocol/server-legacy
@modelcontextprotocol/express
@modelcontextprotocol/fastify
@modelcontextprotocol/hono
@modelcontextprotocol/node
commit: |
This branch has not been deployed
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.
Summary
Documents the client-side DPoP activation path introduced in #2629.
The OAuth guide shows how a provider reuses one asynchronous
DpopSessionand explains its lifetime, DPoP versus Bearer presentation, and the signing-key requirement when tokens survive a restart. The middleware guide clarifies thatwithOAuthalready composes DPoP request signing and nonce handling.Changes
withOAuth/withDpopboundary.Verification
On Node 24 with the repository's pnpm version:
pnpm sync:snippets --checkpnpm --filter @modelcontextprotocol/examples typecheckpnpm check:all, including the documentation buildpnpm build:allnode scripts/smoke-dist-types.mjspnpm test:allwas also run. Unit and integration suites pass. The e2e suite reports two failures inprotocol:timeout:max-totalfor SSE, plus two unhandled timeout errors. Running those SSE scenarios on unmodifiedmainreproduces one failure while the other variant passes. This PR changes documentation and a typecheck-only companion; it does not change runtime code.The companion is typecheck-only; this does not claim an end-to-end run against a real authorization server.
Related to #2629