Skip to main content

Trust Roles: Wallet Providers, Issuers and Relying Parties

Specifications:

In short​

  • A role says what a party is trusted to do: provide wallets, issue PIDs, issue a kind of attestation, or issue the certificates of relying parties.
  • The EU publishes one list for each role, and each list follows an ETSI profile. A trusted party is listed for its role, not in general.
  • A trust check always asks for one role. A party that is listed for another role is not trusted for this check.
  • In the iGrant.io Organisation Wallet Suite, each trust anchor has one role, shown as Used As. The NXD Trust List, which iGrant.io uses for demos, interoperability tests and other non-production use, has one list for each role.

The roles​

RoleWho it isWhere the EU lists itCertificate profileNXD Trust List
Wallet providerSigns the wallet instance attestations (WIA) and key attestations of its wallet unitsWallet Provider LoTE: TS 119 602 Annex E, type EUWalletProvidersListTS 119 412-6NXD-TL-WalletProviders.xml
PID providerIssues person identification dataPID Provider LoTE: TS 119 602 Annex D, type EUPIDProvidersListTS 119 412-6NXD-TL-PID.xml
QEAA providerIssues qualified attestations of attributesNational trusted lists: TS 119 612, a qualified trust service provider with an EAA serviceTS 119 412-6NXD-TL-QEAA.xml (TS 119 612)
PuB-EAA providerIssues attestations for a public sector bodyPuB-EAA Provider LoTE: TS 119 602 Annex H, type EUPubEAAProvidersListTS 119 412-6NXD-TL-PubEAA.xml
EAA providerIssues non-qualified attestations of attributesNot on an EU list: these providers are not notified (ARF §6.3.2)TS 119 412-6NXD-TL-EAA.xml (TS 119 612)
mDL issuerIssues mobile driving licences (ISO/IEC 18013-5)Not on an EU list. Relying parties use the IACA certificate of the issuing authority.ISO/IEC 18013-5 (IACA and document signer)none
Status issuerSigns the status list of a credentialIn a list of trusted entities, the revocation services of PID and PuB-EAA providers give this role. A trusted list (TS 119 612) cannot be used as status issuer. By default, the credential signer may sign the status list.none
Access certificate providerIssues the access certificates (WRPAC) of providers and relying partiesAccess Certificate Authority LoTE: TS 119 602 Annex F, type EUWRPACProvidersListTS 119 411-8NXD-TL-WRPAC.xml
Registration certificate providerIssues the registration certificates (WRPRC) of providers and relying partiesRegistration Certificate Provider LoTE: TS 119 602 Annex G, type EUWRPRCProvidersListTS 119 475NXD-TL-WRPRC.xml
Registrars and registersRegister providers and relying parties in a Member StateTS 119 602 Annex I, type EURegistrarsAndRegistersListNXD-TL-Registrars.xml

The type URIs start with http://uri.etsi.org/19602/LoTEType/. The NXD lists are at https://trustlist.nxd.foundation/trust-lists/, followed by the file name. The six TS 119 602 lists are also published in JSON, for example nxd-wallet-providers-lote.json.

A relying party is not on a list: A relying party is registered in the register of its Member State, not listed in a trusted list. Wallets trust it through its access certificate, which an access certificate authority on the Access Certificate Authority LoTE issued.

In the iGrant.io Organisation Wallet Suite​

On the Trust Anchors page, each trust anchor has exactly one role, Used As (usedFor in the API). A national trusted list that serves several roles therefore needs one trust anchor for each role.

Each check asks for one role, and its accepted list offers only the trust anchors of that role:

CheckRole it asks for
The issuer checks the WIA and the key attestations (credential definition)Wallet provider
The verifier checks who signed a credential (credential query), and the organisation wallet checks who signed a credential it receives (holder configuration)PID provider for a PID, mDL issuer for an mDL, otherwise any issuer role: PID provider, QEAA provider, PuB-EAA provider, EAA provider or mDL issuer
The verifier or the organisation wallet checks who signed the status listStatus issuer
The organisation wallet checks the signed metadata of an issuer, or the request of a relying partyAccess certificate provider

The role of an entry​

  • In a list, the service type of the entry gives its role (ETSI TS 119 612 §5.5.1, TS 119 602 §6.6.1), or else the list type. In a trusted list (TS 119 612), only the service types of attestations of attributes (http://uri.etsi.org/TrstSvc/Svctype/EAA, EAA/Q and EAA/Pub-EAA) give a role, and also http://uri.etsi.org/TrstSvc/Svctype/WRPAC, which some pilot lists use for access certificates (it is not a type of TS 119 612). The list names no role for its other services.
  • A trust anchor uses only the entries for its role: the entries that have its role, and the entries whose list names no role. An entry with no role takes the role of the trust anchor, but never Status issuer. The other entries are not used. The Entries column of the Trust Anchors page and the entries of a trust anchor show which entries it uses; see Manage Trust Anchors.
  • For a CA (X.509) trust anchor, its Used As role applies to each of its CA certificates.

When an entry matches, the check also checks the role of the entry. An entry for another role does not make the signer trusted: the result is not_trusted with the reason wrong_role.

Support notes​

  • Registration certificate provider: you can add trust anchors with this role, but no check uses it yet. The Organisation Wallet Suite does not yet check registration certificates (WRPRC).
  • Registrars and registers: there is no Used As role for this list.
  • QEAA, PuB-EAA and EAA providers: no credential type selects these roles on its own. A check asks for any issuer role, unless the credential is a PID or an mDL.