italia/eid-wallet-it-docs 1.5.0

1.5.0 EUDIW

on GitHub

Version 1.5.0 is the notification baseline for the IT-Wallet as a European Digital Identity Wallet, under Regulation (EU) No 910/2014 as amended by Regulation (EU) 2024/1183, the Architecture and Reference Framework, and the implementing regulations that govern the EUDIW ecosystem,

The relevant updates can be summarised as follows.

• Notification. The Member State, through the Supervisory Body, notifies the Commission. The Commission publishes the result in the Lists of Trusted Entities. The Onboarding System only collects and maintains the notifiable data. Wallet Providers, PID Providers, providers of access and registration certificates, and Registrars are notified under Implementing Regulation (EU) 2024/2980. Public-sector attestation providers are notified under Implementing Regulation (EU) 2025/1569. Other Relying Parties appear through their register.
• PID. Person Identification Data is not issued, stored, or presented until the wallet is notified. Until then, national identification uses the IT-Wallet ID. A Wallet Instance becomes valid only when it obtains a PID.
• Two trust frameworks. A PID, a qualified or public-sector attestation, a credential from another Member State, and a cross-border Relying Party use the EUDIW Trust Framework, rooted in the Trusted Lists and the Lists of Trusted Entities. A national non-qualified attestation, including the IT-Wallet ID, uses the National Trust Framework, based on OpenID Federation. Each issuance or presentation selects one framework for the whole interaction. Where the two configurations differ, the EUDIW one prevails.
• Relying parties. On the European path a Relying Party is recognized through its access certificate and registration certificate. On the national path it is recognized through the federation and the registration Trust Mark.

What's Changed

• TS3-1.5.2 KA and WIA alignment by @Sh-Amir in #1180
• Update Wallet Metadata and EC by @giadas in #1092
• fix: make kid conditionally required based on client_id_scheme by @grausof in #1183
• editorials: eudiw and national trust by @peppelinux in #1195
• Alignment SD-JWT VC draft-13 by @m-basili in #1199
• eudiw: wallet architecture, issuance and presentation aligned with ARF and CIRs by @peppelinux in #1218
• Introduce Keystore / WSCA + Remote WSCD architectural split for Wallet secure cryptographic storage by @grausof in #1182
• Clarify when the PID portrait becomes mandatory by @fventola-ipzs in #1223
• Etsi 472 alignements by @andmoro in #1221
• EUDIW Trust Layer bound to CIR 2026/1730 and ARF 3.0 by @peppelinux in #1216
• EUDIW trust infrastructure by @fmarino-ipzs in #1192
• Bring versione-corrente (1.4.6 and 1.4.7) into the EUDIW trust line by @peppelinux in #1225
• add AI general rules for this project by @peppelinux in #1229
• eudiw: backup and export aligned with Article 5a(4)(f) and (g) of Regulation ... by @peppelinux in #1232
• eudiw: SD-JWT VC compliance with ETSI TS 119 472-1 by @peppelinux in #1233
• Wallet Solution: several improvements and clarification about Wallet Instance and Key Attestation issuance by @peppelinux in #1234
• eudiw (TS7): support_uri consolidation and removal of RP erasure endpoint by @peppelinux in #1236
• eudiw (TS11): Digital Credential Catalogue aligned to ARF 3.0 by @peppelinux in #1238
• Profile QEAA and PuB-EAA in compliance with ETSI TS 119 472-1 by @peppelinux in #1237
• Editorial clarity by @peppelinux in #1244
• chore(deps-dev): bump urllib3 from 2.7.0 to 2.8.0 by @dependabot[bot] in #1240

New Contributors

• @fventola-ipzs made their first contribution in #1223