EUDI Wallet Connect
Create an OpenID Connect client so your users can sign in with their Wallet or prove they are 18 or over.
Watch the connection setup tutorial ↗
You are registering an application, not creating a user account.
In WordPress, open Settings → Talao Wallet Login for EUDI Wallet and copy the return URL shown by the plugin. After registration, download the JSON and import it into the plugin.
In Moodle, open the EUDI Wallet authentication plugin settings and copy its callback URL. After registration, import the configuration JSON into the plugin. The Moodle login plugin uses identity and verified contact email. An age-only client needs an age-check integration; it cannot sign users into accounts.
In your Keycloak realm, add an OpenID Connect identity provider and copy its Redirect URI. Choose identity verification for user sign-in; your applications remain connected to Keycloak.
For Claude, Codex or another local MCP client, choose age verification and use http://127.0.0.1:5088/callback. Download the JSON after verifying your developer email. This public client uses PKCE S256 and has no client secret.
Shopify Plus requires capabilities this connector does not provide directly, including logout. Contact us to assess an adapter before registering a connection. View offers and contact us →
For Microsoft Entra, assess an External ID custom OIDC federation configuration. Confirm outbound PKCE S256 and the claims your configuration requires; a standard Entra application registration is not enough.
Configure an external OpenID Connect identity provider in Okta, rather than an application that uses Okta as issuer. Confirm outbound PKCE S256 support, required claims and the exact callback for your edition.
Configure an enterprise OIDC connection in Auth0 and confirm outbound PKCE S256 support. Register the callback supplied by Auth0 and review the required user claims before deployment.
Use the exact HTTPS redirect URI from your application. Your OIDC client must support Authorization Code with PKCE S256.
Identity shares authorized identity attributes. Age verification proves 18+. Pseudonymous authentication shares a stable sub without identity attributes. Use a separate OIDC client for each purpose. Pseudonymous authentication still verifies the PID through the bridge. It is not anonymous to the bridge. Clients sharing the same callback hostname may receive the same sub.
Add your application name, logo and colour to the Wallet verification page. Leave these options unchanged to keep the standard page. You can change them later through the administrator.
Your registered callback hostname remains visible. A custom name or logo is not a certification.
No payment required. Your connection is created after email verification.