Skip to content

Rework how keys are represented, named, and bound - #8

Merged
jricher merged 2 commits into
jricher:mainfrom
panva:design-c-hybrid
Jul 28, 2026
Merged

jricher merged 2 commits into
jricher:mainfrom
panva:design-c-hybrid

Conversation

@panva

@panva panva commented Jul 27, 2026 •

Copy link
Copy Markdown
Collaborator

Keep each binding method within one algorithm registry. A pre-registered key is a JWK naming a fully specified JWS algorithm. A runtime key names an "HTTP Signature Algorithms" value in alg.

Replace the runtime key per-algorithm parameters with a single pub signature parameter, defined for ECDSA, Ed25519 and ML-DSA. The bound key MUST be asymmetric.

Select a pre-registered key with keyid rather than a pinned httpsig_bound_access_token_kid, so that rotation needs no registration change.

The RS takes the key from the token binding, using cnf.jwk or a new HTTP Signature Key (htsk) confirmation method.

Rendered | diff

Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Comment thread draft-richer-oauth-httpsig.md
Comment thread draft-richer-oauth-httpsig.md Outdated

@jricher jricher left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One wording note to call out parallelism between methods but otherwise I think this is really good work.

Co-authored-by: Justin Richer <github@justin.richer.org>
@jricher
jricher merged commit f67f8ba into jricher:main Jul 28, 2026
1 check passed
@panva
panva deleted the design-c-hybrid branch July 28, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants