Catalog: add the RFC 9449 multi-header invalid_dpop_proof carve-out - #2
Open
RobertoIskandarani wants to merge 1 commit into
Open
Catalog: add the RFC 9449 multi-header invalid_dpop_proof carve-out#2RobertoIskandarani wants to merge 1 commit into
RobertoIskandarani wants to merge 1 commit into
Conversation
RobertoIskandarani
force-pushed
the
rob/dpop-multi-header-carve-out
branch
from
July 28, 2026 20:04
4b60185 to
f6b7c09
Compare
The www_authenticate error-mapping case pinned every DPoP failure to invalid_token. RFC 9449 section 7.1 prescribes invalid_dpop_proof for the section 4.3 multi-header rejection; add that row as the one DPoP carve-out, leaving the other proof failures on invalid_token.
RobertoIskandarani
force-pushed
the
rob/dpop-multi-header-carve-out
branch
from
July 29, 2026 13:02
f6b7c09 to
59d66d9
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.
What
Adds a
dpop_multi_headerrow to theerror_scenariosofrfc6750-error-response-must-map-error-codes, plusRFC9449in that case'sstandard_refsand a rationale note scoping the carve-out.Why
RFC 9449 §4.3 #1 requires that a request carry not more than one
DPoPheader field. Unlike the other DPoP proof-validation failures — which RFC 6750 §3.1 maps toerror="invalid_token"— RFC 9449 §7.1 prescribeserror="invalid_dpop_proof"for this rejection, still on theDPoPscheme.The catalog currently models only
dpop_error → invalid_token / DPoP, so SDKs implementing the §4.3 cardinality check have nowhere to pin a conformance assertion for the divergent error code. The rust-sdk already carries the mapping with unit coverage and a deliberate carve-out comment in its catalog-pinned conformance case, deferred until this row exists; other SDKs implementing §4.3 hit the same gap.Once merged, downstream SDK conformance suites can restore the assertion inside the catalog-pinned case.