eudi.tools · Errors

invalid_dpop_proof after a wallet attestation: which key signs DPoP

A server refuses a DPoP proof because it is not signed with the wallet attestation's key — stricter than attestation-based client authentication requires.

What the server answers

{"error": "invalid_dpop_proof"}
{"error": "invalid_dpop_proof", "error_description": "… cnf …"}

What it means

A wallet using a wallet attestation and DPoP signs two kinds of proof: the attestation's proof of possession, with the key in the attestation's cnf, and DPoP proofs, which bind the access token to a key.

In the attestation draft's normal mode the DPoP key is not required to match the attestation's key. Some servers require it anyway, and refuse a DPoP proof made with a key of its own.

How to fix it

  • If the server needs one key, sign DPoP proofs with the attestation's key for that server.
  • Running the server: if you advertise the normal attestation mode, accept a separate DPoP key — or say in error_description that you want them to match.

Seeing it on eudi.tools

The refusal stays the answer, and beside it the wallet offers to try again with the attestation's key for DPoP — a test switch, so you can see whether that is the only difference.

Open the wallet → and collect from your issuer: paste its credential offer, or drop a screenshot of its QR code.

Specifications

Other errors

  • Unknown JWT audience — An Authorization Server refuses a wallet's attestation proof of possession because its aud names the Credential Issuer, not the Authorization Server that checks it.
  • use_attestation_challenge — An Authorization Server that hands out attestation challenges refuses a proof of possession that carries none — fetch one from its challenge_endpoint for every proof.
  • invalid_scope — An Authorization Server that grants by scope refuses an OpenID4VCI authorization request that carries only authorization_details — add the scope the credential configuration names.
  • invalid_client — When an Authorization Server answers invalid_client to a wallet that sent a valid attestation, it most often does not trust the wallet provider that signed it.