conformance: pass auth/dpop (SEP-1932 baseline) - #1138
Open
gbshankar wants to merge 1 commit into
Open
Conversation
Author
|
Follow-up SDK design: #1139 |
4 tasks
Wire the everything-client to the DPoP baseline scenario with a hand-rolled OAuth + per-request proof path so CI stops expecting auth/dpop to fail. Nonce posture (auth/dpop-nonce) remains deferred; this is harness coverage, not SDK DPoP support. Co-authored-by: Cursor <cursoragent@cursor.com>
gbshankar
force-pushed
the
dpop-1-conformance-auth-dpop
branch
from
August 4, 2026 22:10
8c0ec10 to
7fc4b73
Compare
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
1 participant
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
everything-clientto passauth/dpop(SEP-1932 / RFC 9449 baseline): DPoP proof at the token endpoint,Authorization: DPoP, and a fresh proof per MCP request.auth/dpopfromconformance/baseline.yml; keepauth/dpop-nonceas an expected failure.This is harness coverage only. It does not add SDK DPoP support for apps using
AuthorizationCodeHandler+StreamableClientTransport. That follow-up is tracked separately (design issue + SDK PR).Nonce handling (
auth/dpop-nonce) is intentionally out of scope.Test plan
node dist/index.js client --command <everything-client> --scenario auth/dpop→ 12/12 including the threesep-1932-client-*checks--suite all+baseline.yml) green forauth/dpop;auth/dpop-noncestill expected-failMade with Cursor