Skip to main content

Standards Support and Conformance: Trust in the iGrant.io Organisation Wallet Suite

Sources:

In short​

  • This page states which specifications the trust checks of the iGrant.io Organisation Wallet Suite implement, and how it meets the ARF v3.0.0 trust requirements of the roles that it plays: verifier, holder wallet, issuer and wallet provider.
  • Status is one of three values:
    • Supported: the Organisation Wallet Suite does it, often once you turn on the Require switch of the check.
    • Partly: it does part of it; the note says which part.
    • Not yet: a gap.
  • The main gaps: registration certificates (WRPRC), which the Organisation Wallet Suite neither sends nor checks yet, and the Certificate Transparency check of access certificates.
  • The status is as of 18 November 2026. Requirements that bind Member States, registrars, certificate authorities or the Commission are out of scope.

Specifications​

SpecificationIn the Organisation Wallet SuiteStatus
ETSI TS 119 612 V2.4.1: trusted listsReads trusted lists in XML as ETSI TL trust anchors: verifies the XAdES signature with the list signer certificate, follows the next update, reads entries, statuses and historySupported
ETSI TS 119 602 V1.1.1: lists of trusted entities, XMLReads lists of trusted entities in XML as ETSI LOTE trust anchors, for the profiles of Annexes D to ISupported
ETSI TS 119 602 V1.1.1: lists of trusted entities, JSONReads the entries of a JSON list. Tested with the NXD Trust List, whose JSON signature does not verify; see InteroperabilityPartly
IETF RFC 5280 §6: path validationThe path to a trust anchor of the role: the signatures, validity and CA rules of the path, the key usage of the signer certificate, and its revocation with the CRLs of a CA (X.509) trust anchorSupported
IETF RFC 7515 (x5c) and RFC 9360 (x5chain)Reads the signer chain of credentials, attestations, requests and status lists, and sends its own up to the trust anchor that you chooseSupported
ETSI TS 119 412-6 V1.1.1: certificate profiles of providersCertificate presets for the CSRs of PID, wallet, EAA, QEAA and PuB-EAA providersSupported
ETSI TS 119 411-8 V1.1.1: access certificatesCertificate presets for access certificates (WRPAC) of legal and natural personsSupported
ETSI TS 119 475 V1.2.1: registration certificatesNeither sent nor checkedNot yet
OpenID4VCI 1.0: signed issuer metadataThe issuer signs its metadata with its access certificate key, and the holder wallet can require a trusted signerSupported
OpenID4VP 1.0: trusted_authorities (etsi_tl, aki) and the client ID prefixes x509_san_dns and x509_hashThe verifier sends them, and the holder wallet checks themSupported
IETF RFC 9162: Certificate TransparencyThe trust checks do not check Signed Certificate TimestampsNot yet
OpenID Federation 1.0On the roadmap

ARF v3.0.0 requirements​

As a verifier​

RequirementIn shortStatusHow
OIA_12Validate a PID with a trust anchor of a PID Provider LoTESupportedRequire a trusted credential signer, with the PID Provider LoTE in Accepted credential signers. See Trust When Verifying.
OIA_13Validate the qualified signature of a QEAA (Art. 32), with a trust anchor of a QEAA Provider trusted listPartlyThe chain is validated to a trust anchor of the QEAA provider trusted list that you accept. The other checks of a qualified signature under Art. 32 are not part of the trust check.
OIA_14Validate a PuB-EAA with a trust anchor of a PuB-EAA Provider listSupportedThe same, with the PuB-EAA provider list
OIA_15Validate a non-qualified EAA with the trust anchors that its rulebook definesSupportedThe same, with any ETSI TL, ETSI LOTE or CA (X.509) trust anchor used as EAA provider
RPACANot_03Your access certificates can be authenticated with the trust anchors of a notified Access Certificate AuthoritySupportedSign requests with an access certificate key, issued by such an authority. See Your Certificates.
RPRC_19, RPRC_20Include a registration certificate in each presentation requestNot yet

As a holder wallet​

RequirementIn shortStatusHow
ISSU_07, ISSU_09, ISSU_10Validate a received PID, PuB-EAA or EAA with a trust anchor of its providerSupportedRequire a trusted credential signer in the holder configuration. See Trust in Your Wallet.
ISSU_08Validate the qualified signature of a received QEAAPartlyAs for OIA_13
ISSU_23, ISSU_24, ISSU_33, ISSU_34Authenticate the access certificate of a PID provider or attestation provider before requesting issuance, with the trust anchors of the Access Certificate Authority LoTEsSupportedRequire a trusted issuer: the signer of the signed issuer metadata must be trusted as an access certificate provider. To accept only the EU lists, as ISSU_33 asks, put only Access Certificate Authority LoTEs in Accepted issuers.
ISSU_24a, ISSU_33a, ISSU_34a, RPRC_23Check the registration certificate of an issuer, and that it is registered for the type of credentialNot yet
RPA_04Authenticate the access certificate of a relying party with the trust anchors of the Access Certificate Authority LoTEsSupportedRequire a trusted relying party, with Access Certificate Authority LoTEs in Accepted relying parties
RPRC_17, RPRC_17a, RPRC_21Check the registration certificate in a presentation request, its identifiers, and the requested attributes against itNot yetThe dashboard shows the registration certificate as Not supported.
CT_05, CT_06Check that an access certificate has a valid Signed Certificate TimestampNot yet

As an issuer (PID or attestation provider)​

RequirementIn shortStatusHow
ISSU_19, ISSU_28Accept the trust anchors of the Wallet Provider LoTE for WIAs and key attestationsSupportedThe Wallet Provider LoTE in Accepted wallet providers. See Trust When Issuing.
ISSU_21, ISSU_30, ISSU_30aVerify the WIA and the key attestation with a trust anchor of the Wallet Provider LoTE, and that the wallet instance and its keys are not revokedSupportedRequire a trusted wallet provider. The issuer checks the signature, expiry and revocation of the WIA and of the key attestation.
ISSU_22, ISSU_32Sign the credential issuer metadata with the key of the access certificateSupportedThe access certificate key of the issuer configuration
PPNot_03, PPNot_04Your PIDs and access certificates can be authenticated with the notified trust anchorsSupportedChoose the trust anchor of each signing key. See Your Certificates.
RPRC_22Include your registration certificate in the credential issuer metadataNot yet

As a wallet provider​

RequirementIn shortStatusHow
WPNot_03WIAs and key attestations can be authenticated with the notified trust anchorsSupportedEach WIA and key attestation carries its chain in x5c, up to the trust anchor that you choose for the key

Lists​

RequirementIn shortStatusHow
PPNot_07, WPNot_05, RPACANot_05, PuBPNot_03PID Provider, Wallet Provider, Access Certificate Authority and PuB-EAA Provider LoTEs in the format of ETSI TS 119 602, Annexes D, E, F and HSupportedKind ETSI LOTE, with the role PID provider, Wallet provider, Access certificate provider or PuB-EAA provider
RPACANot_05aThe LoTE of providers of registration certificates (Annex G)PartlyIt can be added with the role Registration certificate provider, but no check uses it yet

Known gaps​

  1. Registration certificates (WRPRC).
    • The Organisation Wallet Suite does not send a registration certificate as a verifier or as an issuer.
    • It does not check one as a holder wallet.
    • The Registration certificate provider role exists for trust anchors, but no check uses it yet.
  2. Certificate Transparency. The checks of access certificates do not check Signed Certificate Timestamps.
  3. Qualified signatures of QEAAs. The trust check validates the chain to a trusted list of QEAA providers, not the further checks of a qualified signature under Art. 32.
  4. Lists of trusted entities in JSON. The entries are read. The signature of the NXD JSON lists, the only JSON lists tested, does not verify.
  5. Lists without entries, and registrars.
    • A list with no entries cannot be added as a trust anchor.
    • No Used As role fits a list of registrars and registers (Annex I).
  6. OpenID Federation. Not supported; it is on the roadmap.