eudi.tools · Errors

use_attestation_challenge: the attestation proof needs a fresh 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.

What the server answers

{"error": "use_attestation_challenge", "error_description": "Invalid client authentication. Missing challenge in attestation pop. (trace_id=…)"}

What it means

Some Authorization Servers want each attestation proof of possession to answer a challenge they issued, so a captured proof cannot be replayed. Such a server publishes a challenge_endpoint in its metadata.

A wallet that sends its proof without a challenge claim — or with an old one — is told to use one: use_attestation_challenge.

How to fix it

  • Read the Authorization Server's metadata. If it publishes challenge_endpoint, POST to it before each proof and read attestation_challenge from the JSON reply.
  • Put that value in the proof of possession as its challenge claim. Fetch a new one for the next proof: the token request needs its own, not the one the pushed authorization request used.
  • A server that publishes no challenge_endpoint gets proofs without a challenge, as before.

Seeing it on eudi.tools

The wallet fetches a challenge whenever the server publishes the endpoint. On the wire it is its own step, “Attestation challenge”, before the pushed authorization request and again before the token request — open it to see what the server returned.

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.
  • 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.
  • invalid_dpop_proof — A server refuses a DPoP proof because it is not signed with the wallet attestation's key — stricter than attestation-based client authentication requires.