eudi.tools · Errors

“Unknown JWT audience”: the wallet attestation PoP is addressed to the wrong server

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.

What the server answers

{"error": "invalid_client", "error_description": "… Unknown JWT audience …"}
{"error": "invalid_client"}

What it means

A wallet that authenticates with a wallet attestation (attest_jwt_client_auth) sends two JWTs with its pushed authorization request and its token request: the attestation, in the OAuth-Client-Attestation header, and a fresh proof of possession, in OAuth-Client-Attestation-PoP. The proof's aud must identify the Authorization Server that receives it.

The Credential Issuer and its Authorization Server are often the same host, which makes the issuer's URL look like the right audience. When they are not, a proof addressed to the Credential Issuer reaches a server that does not recognise itself in aud, and refuses the client.

How to fix it

  • Address the proof to the Authorization Server: the one the credential offer's grant names in authorization_server, else the first entry of authorization_servers in the Credential Issuer's metadata, else — only when it lists none — the Credential Issuer itself.
  • Use the same server for every proof in the flow: the pushed authorization request, and the token request after the user signs in.
  • Running the server: say which audience you expected in error_description. “Unknown JWT audience” is right, but naming the value saves a round of guessing.

Seeing it on eudi.tools

The wallet picks the audience in that order and shows it: open See the wire on the collection, choose the pushed authorization request, and the Decoded tab shows the proof's aud next to the server it was sent to.

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

Specifications

Other errors

  • 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.
  • 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.