Ecosystem Enforcement Reference for Verifiers

This page provides a reference of all checks and validations performed when verifying with an ecosystem enforced. For instructions on enforcing an ecosystem during verification, see Enforcing an Ecosystem as a Verifier.

EUDI

Before verification

When you create a proof request with EUDI ecosystem enforced, the system performs the following checks:

• Verifying identifier (verifier) must be a certificate
• Verification protocol must be OpenID4VP 1.0
• Schema must use SD-JWT VC and/or ISO mdoc as the credential format
• If the verifying identifier contains a Registration Certificate (found in trustInformation of identifier), the proof schema being used must match the intended use in this certificate

If any of these checks fail, the call to create a proof request returns an error.

During verification

The system performs the following checks:

• For the following types of credentials presented, the issuer must be trusted:
  • PID — identified by the schema IDs set in pidSchemaIds of your ecosystems configuration. The issuer must be found on the PID Provider trust list (subscribed with role PID_PROVIDER).
  • QEAA — auto-detected from the claims on the credential. The issuer (a Qualified Trust Service Provider, or QTSP) must be found on the QEAA Provider trust list (subscribed with role QEAA_PROVIDER).

If any of these checks fail, the presentation is rejected.

note

These checks only work if your organization subscribes to the trust lists above. See Prerequisites.