CodeB · Standards & compliance

EU Digital Identity Wallet — registry registration

← Admin LOTL cache

What this does. Self-registers this tenant () with the European Digital Identity Wallet reference Wallet Relying Party (WRP) registry at . Registration is bound to a natural person (director / DPO) via their EU-issued PID and produces two on-disk certificates that make EU reference wallets recognise the verifier as an authorised RP.

Prerequisite. Install the EU reference Wallet (Android or iOS build published by the European Commission’s EUDI reference programme) on a phone and load a test PID from the EU reference issuer. Without a PID on hand the QR scan below cannot complete.

Steps. (1) Click Start. (2) Scan the QR with your EUDI wallet. (3) Approve the PID presentation in the wallet. (4) Enter a strong password (12+ chars) for the PKCS#12 archive. (5) Click Finalise to walk the 14-step registration tree and install both certificates under App_Data/<tenant>/vci/. (6) Once wrp.p12 is in place, presentation requests to EU reference wallets are signed with the registry-issued key automatically.

Succession & ownership. The registry binds every write to the natural person whose PID was scanned in step 2 (via an opaque hash_pid). The current WRP registry Swagger exposes no transfer-ownership or add co-owner endpoint on the Legal Entity or WRP records, so if the person who registered this tenant later leaves the company, their successor must complete a fresh registration under their own PID. The installed wrp.p12 continues to work until it expires; the successor’s registration produces a new key that supersedes it via the same auto-swap flow. Practical implication: register under a role account’s PID (e.g. the DPO’s dedicated identity) rather than a personal one, and keep the recovery cadence < cert expiry.

Current state

Tenant
Registry base URL
Last kickoff (UTC)
Last finalise (UTC)
hash_pid on record
JAR signing preference
wrp.p12
intended-use.jades
issuer.pfx (self-signed)

0. Configuration — identity + contact details

These values are baked into every registry write during Finalise. Save before Kickoff so the WRP registry sees accurate data. All comma-separated arrays accept multiple values. The Supervisory Authority + Advanced sections use ARF-conformant defaults for Aloaha / Malta — edit only if your legal setup differs.

Legal names (comma-sep)
Identifier type
Identifier value
Country (2-letter EU code)
Trade name
DPO / contact email (comma-sep)
Phone (comma-sep, E.164)
Postal address (comma-sep)
Info URI (comma-sep)
Registry URI (this tenant)
Support URI (comma-sep)
Service description (English)
Privacy statement URI
DPIA / intended-use policy URI
Public Sector Body (isPSB)
Advanced — Supervisory Authority + entitlements + formats
SA name
SA country
SA email (comma-sep)
SA complaint form URI (comma-sep)
SA phone (comma-sep)
Entitlements (comma-sep ARF URIs)
Formats provided (comma-sep)
Legal basis (comma-sep)
Legislative identifier
Intended-use identifier
Intended-use purpose (English)

1. Kickoff — authenticate with your PID

Debug & status

Live view of the last error the registry returned, plus a scrolling event log of every kickoff / poll / save / finalise / revert with the raw upstream response body. Use this to diagnose why a step failed.

Last error on record
Failed step
Failed URL
Failed HTTP status
Failed at (UTC)
Assigned registry IDs
Failed request body (what we POSTed to the registry)
(no failure recorded)
Failed response body (what the registry returned)
(no failure recorded)
Event log (newest first)
(no events yet -- Kickoff / Save / Finalise will populate)

Registration progress