Skip to content

Trusted List Provider (TLP)

The Trusted List Provider (TLP) is a supporting ecosystem service responsible for creating, maintaining, signing, and publishing the national Trusted Lists (TLs) and the EU List of Trusted Lists (LoTL), which contain the trust anchors and status information of Wallet Providers, PID Providers, QEAA Providers, PuB-EAA Providers, Access Certificate Providers, and Registration Certificate Providers. By providing authenticated, machine-readable Trusted Lists, the TLP enables Wallets, Relying Parties, and ecosystem components to verify that an entity is supervised and trusted, ensuring cross-border trust, interoperability, and the integrity of cryptographic verification processes within the EUDI Wallet ecosystem.

TLP Role in the EUDI Wallet Ecosystem

The Trusted List Provider (TLP) is a supporting service responsible for the management, maintenance, and publication of Trusted Lists (TLs) used across the EUDI Wallet ecosystem. Trusted Lists form a critical trust infrastructure: they contain trust anchors (public keys and identifiers) for all entities that must be recognised as trusted by relying parties and other ecosystem components.

A TLP ensures that the Wallet Providers, PID Providers, QEAA Providers, PuB-EAA Providers, Access Certificate Providers, and Registration Certificate Providers can be automatically and reliably verified by any stakeholder in the ecosystem. An entity’s trusted status is established by verifying its presence on the relevant Trusted List.

TLPs operate at two levels:

  1. National Trusted Lists (TL) – created, signed, and managed by Member States.
  2. EU List of Trusted Lists (EU LoTL) – a unified list created, signed, and managed by the European Commission that aggregates all national TLs.

The source of trust for the LoTL is the Official Journal of the European Union (OJEU).

Reference Implementation TLP

The Reference Implementation Trusted List Provider (TLP) is designed solely to support experimentation, validation, and interoperability testing within the EUDI Wallet ecosystem. It serves as an illustrative, non-production example of how Trusted Lists and the EU List of Trusted Lists can be created, managed, and published, enabling developers, Member States, and ecosystem participants to familiarise themselves with the trust infrastructure envisioned by the ARF. This implementation is not subject to the security, robustness, operational, or compliance requirements applicable to production-grade TLPs and must therefore not be deployed or relied upon in real operational environments.

Reference Implementation TLP service

For testing purposes, a hosted instance of the Reference Implementation TLP is available at https://trustedlist.serviceproviders.eudiw.dev/.

It provides:

  • A complete UI for managing TLs, TSPs, trust services, and LoTL.
  • Integration with EUDI Wallet authentication.
  • XML generation and signing for TL and LoTL.
  • A configuration model based on environment variables.
  • Docker support for rapid deployment.

This service demonstrates the operational workflows of a TLP and can be used for creating TLs and LoTL for testing, development, or conformance checks.

Core functionalities

Trusted List Lifecycle Management

The RI TLP service provides capabilities for the Member State (TSL Operator) to:

  • Onboard and manage Trust Service Providers (TSPs) relevant to the EUDI Wallet ecosystem.
  • Manage trust services associated with each TSP.
  • Create, update, and electronically sign the National Trusted List (TL).
  • Publish the TL in a secure and accessible location.
  • Maintain TL metadata and multilingual information.
LoTL Management (for EC Operators)

For the European Commission, the TLP supports:

  • Aggregating all TLs published by Member States.
  • Creating and signing the EU List of Trusted Lists (LoTL).
  • Managing LoTL metadata and multilingual content.
  • Publishing the LoTL.
Trust Anchor Publication

Each TL contains:

  • The public key (trust anchor) for each recognised entity.
  • The identifier of the entity.
  • Status information and service metadata.

Relying Parties and Wallets use these trust anchors to verify:

  • digital signatures,
  • attestations,
  • credential issuances,
  • authentication responses.

Users and Access Model

The TLP supports three user roles:

  • TSL Operator
  • TSP User
  • LoTL Operator

The TSL Operator manages the national Trusted List:

  • Manage TSPs and trust services.
  • Create, edit, and sign TLs.
  • Add multilingual information.
  • Associate TSPs and services before generating the signed XML TL.

The TSP (Trust Service Provider) User manages their own TSP records and trust services:

  • Create and manage Trust Service Provider (TSP) entries.
  • Create and manage trust services.
  • Maintain multilingual service information.

The LoTL Operator is the only user who may:

  • Create, update, and sign the EU List of Trusted Lists.
  • Manage LoTL metadata and multilingual content.
  • Aggregate TLs provided by Member States.

Format of the TL and LoTL

The current Reference Implementation of the Trusted List Provider (TLP) focuses on demonstrating the fundamental trust-establishment mechanisms of the EUDI Wallet ecosystem and its present capabilities are limited to the generation of national Trusted Lists (TLs) and the EU List of Trusted Lists (LoTL) strictly following the ETSI EN 119 612 specification. This means that all outputs—structure, metadata, signing model, and publication format—adhere exclusively to the ETSI 119 612 schema. Other formats, profiles, or alternative serialisation approaches are not supported at this stage, but will be added after ETSI 119 602 is published.

Reference Implementation TLP deployment and configuration

The complete source code, deployment instructions and configuration details for the Trusted List Provider (TLP) Reference Implementation are publicly available in the GitHub repository at eudi-srv-web-trustedlist-manager-py.

The TLP can be run:

  • Locally (Python/Flask environment),
  • With Docker (via provided docker-compose).

It supports configuration via environment variables covering:

  • Service URLs,
  • Trust anchor validation paths,
  • Verifier endpoints,
  • XML signing certificate paths,
  • Logging, and
  • Database configuration.