Skip to content

fix(oid4vc): advertise only ES256 for DPoP - #40

Merged
Eldersonar merged 1 commit into
mainfrom
fix/dpop-advertised-algs
Sep 24, 2026
Merged

Eldersonar merged 1 commit into
mainfrom
fix/dpop-advertised-algs

Conversation

@Eldersonar

Copy link
Copy Markdown

Summary of Changes

AS metadata advertised dpop_signing_alg_values_supported: ["ES256", "ES384", "ES512"]. HAIP requires ES256, the only ECDSA algorithm jwt_verify supports, so ES384/ES512 had nothing behind them. A wallet that parses the list strictly (holdr 2.0.2-rc.4) rejected the whole metadata document on ES512 and couldn't receive credentials.

  • openid_configuration advertises ["ES256"].
  • Test: AS metadata advertises only ES256.

Related Issues

Pull Request Checklist

  • All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this).
  • Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components.
  • Added tests for changed code (run scripts/preflight to run tests and check code style).
  • Prefixed code comments with GitHub nick and an appropriate prefix.
  • Coding style is consistent with the rest of the framework.
  • Updated documentation for changed code and new or modified features.
  • (NEW) CHANGELOG.md is up to date and changed in this PR.

The authorization server metadata listed ES256, ES384 and ES512 in
dpop_signing_alg_values_supported. HAIP requires ES256, and it is the only
ECDSA algorithm jwt_verify supports, so ES384 and ES512 had nothing behind
them. Wallets that deserialize the list strictly also rejected the whole
metadata document on ES512, which blocked issuance to them entirely.

Signed-off-by: Eldersonar <slavaecu@gmail.com>

@mikekebert mikekebert left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thank you.

@Eldersonar
Eldersonar merged commit 902ab70 into main Sep 24, 2026
6 checks passed
@Eldersonar
Eldersonar deleted the fix/dpop-advertised-algs branch September 24, 2026 09:05
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