eudi.tools

Errors, explained

Refusals a wallet meets while collecting a credential over OpenID4VCI — what each one means, the specification behind it, and how to fix it. Each was met from a real Authorization Server; the eudi.tools wallet now handles or explains every one of them where it happens.

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

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