The Drop Times: What EU Digital Identity Wallets Could Mean for Drupal

The useful part

States must make wallets available to citizens, residents, and businesses by the end of 2026. For Drupal teams, that makes digital identity less a future policy topic and more an application-architecture question. Instead of treating identity as one complete profile, users can present particular identity data or attestations and disclose only the information required for a transaction.

How it works

• Under the European framework, organisations that use wallets for digital services must register their intended use and indicate the data they plan to request.
• The wallet model changes what an online service can ask a user to prove.
• That puts the request itself inside a defined trust and registration model rather than leaving every application to decide independently what identity information it wants to collect.
• The technical exchange is also more specific than adding another login provider.
• For remote presentation flows, the EUDI architecture uses OpenID for Verifiable Presentations to carry requests and wallet responses between wallets and relying parties.

Details worth keeping

Commission figures say more than 550 companies and public authorities across 26 Member States, Norway, Iceland, and Ukraine are participating in large-scale pilots covering government services, banking, education, health, transport, telecommunications, and other uses. The relevant role for a Drupal application is the relying party.