feat(oauth): advertise dpop_signing_alg_values_supported in discovery (#118)#149
Merged
Conversation
…#118) Fourth DPoP slice (RFC 9449 §5.1): the AS metadata document now lists the proof signing algorithms it accepts, so clients and resource servers can discover DPoP support (e.g. an MCP agent probing /.well-known before choosing to sender-constrain its tokens). - DpopDiscoveryMetadataHandler (HandleConfigurationRequestContext) emits dpop_signing_alg_values_supported via the free-form metadata dict, the same mechanism as the CIMD/DCR handlers. Unconditional — DPoP is offered to every realm (opt-in per request), so no per-realm gate. - The list is sourced from DpopProofValidator.SupportedSigningAlgorithms — now exposed publicly (in both the server and the duplicated client copy, kept identical) — so the advertised set can't drift from what the token endpoint actually enforces. Integration test asserts discovery carries the array including ES256/RS256/ PS256. Full DPoP suite green (50 unit + 6 integration). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 19, 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
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.
Part of #118. Fourth DPoP (RFC 9449 §5.1) slice.
The AS metadata document (
/.well-known/openid-configuration) now lists theDPoP proof signing algorithms it accepts, so clients and resource servers
can discover DPoP support — e.g. an MCP agent probing discovery before
deciding to sender-constrain its tokens.
Changes
DpopDiscoveryMetadataHandler(HandleConfigurationRequestContext)emits
dpop_signing_alg_values_supportedvia the free-form metadata dict,the same mechanism the CIMD/DCR discovery handlers use. Unconditional —
DPoP is offered to every realm (opt-in per request), so no per-realm gate.
DpopProofValidator.SupportedSigningAlgorithms, now exposed publicly (inboth the server copy and the duplicated client copy, kept identical), so
what's advertised can't drift from what the token endpoint enforces.
Tests
Integration test asserts discovery carries the array incl.
ES256/RS256/PS256. Full DPoP suite green (50 unit + 6 integration).Remaining DPoP follow-ups
RequireDpopenforcement (mirrorRequirePushedAuthorizationRequests);DPoP-Nonce/use_dpop_nonce), AS + RS;AddModgudClient);jtireplay cache.🤖 Generated with Claude Code