Skip to content

Catalog: add the RFC 9449 multi-header invalid_dpop_proof carve-out #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
RobertoIskandarani merged 3 commits into from
Aug 4, 2026
Merged

Catalog: add the RFC 9449 multi-header invalid_dpop_proof carve-out #2

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2f480b4
Encode the RFC 9449 multi-header invalid_dpop_proof carve-out
RobertoIskandarani Jul 27, 2026
01e109d
Catalog: add dpop_not_supported → Bearer/invalid_token row to error-c…
RobertoIskandarani Aug 3, 2026
f95e456
Correct the RFC 9449 7.1 scope in the error-mapping rationale; bump c…
RobertoIskandarani Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions oauth-sdk-conformance-catalog.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
schema_version: "1.0"
catalog_id: "oauth-sdk-conformance-catalog"
catalog_version: "2026-04-22"
catalog_version: "2026-08-04"

source_baseline:
intent: "Language-neutral OAuth SDK conformance catalog shared across SDK implementations."
Expand Down Expand Up @@ -2098,11 +2098,12 @@ cases:
standard_refs:
- "RFC6750"
- "RFC9068"
- "RFC9449"
surface: "sdk-verifier.error-response"
priority: "high"
requirement_summary: "RFC 9068 §4 requires resource servers to handle errors as described in RFC 6750 §3.1. The SDK MUST\
\ provide a helper that maps authentication errors to 'invalid_token' and authorization errors to 'insufficient_scope'\
\ in a WWW-Authenticate header value."
\ provide a helper that maps authentication errors to 'invalid_token', authorization errors to 'insufficient_scope',\
\ and a DPoP proof deemed invalid under RFC 9449 §4.3 to 'invalid_dpop_proof' in a WWW-Authenticate header value."
setup:
error_scenarios:
- error_type: "token_expired"
Expand All @@ -2117,13 +2118,22 @@ cases:
- error_type: "dpop_error"
expected_error_code: "invalid_token"
expected_scheme: "DPoP"
- error_type: "dpop_multi_header"
expected_error_code: "invalid_dpop_proof"
expected_scheme: "DPoP"
- error_type: "dpop_not_supported"
expected_error_code: "invalid_token"
expected_scheme: "Bearer"
stimulus:
operation: "www_authenticate(error)"
expected:
outcome: "accept"
www_authenticate_format: "<scheme> error=\"<error_code>\", error_description=\"<message>\""
rationale: "RFC 9068 §4 delegates error handling to RFC 6750 §3 which mandates specific error codes in WWW-Authenticate\
\ challenges. Without an SDK helper, every adapter must reimplement this mapping, risking inconsistency."
\ challenges. Without an SDK helper, every adapter must reimplement this mapping, risking inconsistency. RFC 9449 §7.1\
\ designates invalid_dpop_proof for a proof deemed invalid under the §4.3 criteria; the dpop_multi_header row profiles\
\ that designation for the §4.3 item 1 cardinality rejection. dpop_not_supported is the inverse case: the resource is\
\ bearer-only, so its challenge uses the Bearer scheme with invalid_token rather than DPoP."
- id: "rfc9728-prm-dpop-fields-should-be-advertised-when-dpop-is-supported"
title: "PRM should advertise DPoP signing algorithms and binding requirement when DPoP is configured"
standard_refs:
Expand Down
Loading