OID4VPs new error codes

Issue #1741 resolved
David W Chadwick created an issue

During our NGI project we are developing tests for requesting a VP from wallets. We do not think that suitable errors exist for some of the new parameters that OID4VPs has introduced, or text is missing to describe which errors should be used. In particular:

It the presentation definition does not conform to the DIF PEv2 specification - We suggest Error code 400 with the error ‘invalid_request’ (this error already exists but we think it would be best to add text to say that this error should be used for this type of failure)

If the presentation definition URL cannot be reached - We suggest Error code 400 with a new error 'invalid_presentation_definition_location”

If the presentation definition URL can be reached but the specified policy cannot be found in the policy server - We suggest Error code 400 with a new error ‘invalid_policy_reference’

If the scope is unrecognised as an alternative to a presentation definition then this is already covered with descriptive text so no changes are required for this.

Comments (6)

  1. Kristina Yasuda

    I do not see any issues with the proposed error codes and descriptions. I am just unsure at what granularity we should be defining error codes in this specification.

  2. Log in to comment