client/auth: register dpop and wif scenarios as extensions#401
Merged
Conversation
commit: |
claude
Bot
force-pushed
the
dpop-client-extension-registration
branch
from
ce91890 to
cd2f0cb
Compare
claude
Bot
changed the title
Move the DPoP scenarios (auth/dpop, auth/dpop-nonce) and the WIF JWT-bearer scenario (auth/wif-jwt-bearer) off the draft spec timeline and register them as the io.modelcontextprotocol/auth/dpop and io.modelcontextprotocol/auth/wif protocol extensions (SEP-2133 reverse-DNS ids), so they run under --suite extensions rather than at --spec-version draft. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012E7BriGaLimJxQr7B7ChiM
claude
Bot
force-pushed
the
dpop-client-extension-registration
branch
from
cd2f0cb to
b67b69b
Compare
pcarleton
approved these changes
Jul 10, 2026
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
2 participants
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.
Requested by Paul Carleton · Slack thread
Follow-up to #394, as discussed there — split out of #400 so that PR carries only the remaining review fixes.
Before: the DPoP scenarios from #394 (
auth/dpop,auth/dpop-nonce) and the WIF JWT-bearer scenario (auth/wif-jwt-bearer) ride the draft spec timeline, so a client that doesn't implement these optional extensions fails draft-suite checks.After: they're registered as protocol extensions
io.modelcontextprotocol/auth/dpopandio.modelcontextprotocol/auth/wif(SEP-2133 reverse-DNS ids), selected via--suite extensions, like the other auth extensions.How: adds
io.modelcontextprotocol/auth/dpopandio.modelcontextprotocol/auth/wiftoEXTENSION_IDS, tags the scenarios'sourcewith the extension ids, moves them fromdraftScenariosListtoextensionScenariosList, and drops the now-deadspecVersionsfield on the WIF scenario class.Generated by Claude Code