Wallet Connectors introduces an EUDI Wallet connector for Keycloak. It brings identity credentials presented through a wallet into the sign-in journey of applications that already rely on Keycloak for identity and access management.

Why connect an EUDI Wallet to Keycloak?

Public-sector teams, software vendors, enterprise IAM teams and systems integrators can explore wallet-based sign-in within an environment they already operate. The integration connects wallet identity verification to existing access management, while applications keep their Keycloak integration.

Web3 Digital Wallet, the company behind Talao, builds identity wallets. With Wallet Connectors, we also help application teams accept the credentials users present through those wallets.

How the wallet sign-in flow works

  1. The user starts signing in to an application connected to Keycloak.
  2. Keycloak offers the configured EUDI Wallet identity provider.
  3. The user presents identity credentials through their wallet, and Wallet Connectors verifies the presentation.
  4. Keycloak handles the account association and applies the application's roles and access policies.

This separates the verification of presented identity information from the application's authorization decisions. Keycloak remains responsible for the account and access rules configured in your realm.

Use Keycloak's built-in OpenID Connect provider

The connector uses Keycloak's native OIDC identity brokering. You configure an OpenID Connect identity provider in the realm, rather than adding wallet-specific integration code to each application.

For the configuration and video walkthrough, visit the Wallet Connectors Keycloak integration page. Keycloak also provides OpenID Connect documentation for teams reviewing their application architecture.

Prepare a practical pilot

In the demonstration announced with the connector, a successful wallet sign-in was completed in under five minutes once the local Keycloak environment was ready. That observation describes the prepared demonstration; a production deployment also requires integration and policy review.

The current guide calls for a public HTTPS callback copied from your realm, connection credentials and a review of first-login behavior. Test the complete journey from an application connected to that realm before expanding the pilot.

Account linking and identity attributes

The documented identity flow uses openid profile. It does not request an email address or an 18+ proof. Review any mandatory email requirement in your realm before using the flow.

For an existing account, require authentication to that account before linking the external identity provider. Names and email addresses alone are not sufficient for automatic matching. The provider association uses its external subject identifier.

Start your Keycloak integration

Explore the Keycloak setup guide and video tutorial, or read the Wallet Connectors launch announcement. Organizations building their own wallet can also explore Talao's white-label EUDI Wallet applications and backend.

Based on Thierry Thevenet's launch announcement. Configuration details were checked against the linked integration guide on 18 November 2026.