invalid_client with a wallet attestation: usually trust, not the request
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.
What the server answers
{"error": "invalid_client"}What it means
invalid_client is the Authorization Server declining the wallet as a client. It very often comes without a description, so the request looks wrong when it is not.
With attestation-based client authentication, the server checks the wallet attestation's signature against the wallet providers it trusts. A wallet whose provider is not on that list is refused this way, however correct everything else is.
The other causes are the attestation itself: expired, revoked on the provider's status list, or a proof of possession that does not match it.
How to fix it
- Check trust first: is the certificate of the wallet provider that signed the attestation in the server's trust list? That is a change on the server's side, by whoever runs it.
- Then the attestation: its exp, its status, and that the proof of possession is signed with the key in the attestation's cnf.
- Running the server: say which of these failed in error_description. The wallet cannot tell them apart.
Seeing it on eudi.tools
At an invalid_client refusal the wallet says where to start, and links to the wallet provider's certificate on eudi.tools/trust — a page to send to whoever runs the server.
Open the wallet → and collect from your issuer: paste its credential offer, or drop a screenshot of its QR code.
Specifications
- RFC 6749 — The OAuth 2.0 Authorization Framework — invalid_client (§5.2)
- OAuth 2.0 Attestation-Based Client Authentication (IETF draft) — the Client Attestation and its proof of possession
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_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.