eudi.tools · Errors

invalid_scope “No scopes requested”: send the credential's scope too

An Authorization Server that grants by scope refuses an OpenID4VCI authorization request that carries only authorization_details — add the scope the credential configuration names.

What the server answers

{"error": "invalid_scope", "error_description": "No scopes requested. (trace_id=…)"}

What it means

OpenID4VCI lets a wallet ask for a credential two ways: with authorization_details of type openid_credential, naming the credential configuration, or with the scope that configuration declares in the Credential Issuer's metadata. Either is valid.

Some Authorization Servers still decide by scope alone. Asked with authorization_details and no scope, they find nothing requested and say so, even when the configuration the wallet named is one they serve.

How to fix it

  • Look up the configuration in credential_configurations_supported. If it declares a scope, send it in the request's scope parameter alongside authorization_details.
  • Leave it out when the Authorization Server's scopes_supported lists other scopes and not this one: that server says it does not support it.

Seeing it on eudi.tools

The wallet sends both whenever the configuration has a scope the server supports. The pushed authorization request on the wire shows the form body, with scope and authorization_details side by side.

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