Admin: populate the OIDC profile fields that the four German EUDI credentials draw from. Once these are filled in for a user, the user can self-issue the card to their wallet via /member-card.html. See the status matrix for what is ratified vs. draft.
This page edits user profile data for the tenant. Sign in with an admin OIDC session.
App_Data/<tenant>/sip-credentials/<tenant>.json under users[user].profile via signal.ashx?credentials=setprofile. The IdP echoes those fields into the standard OIDC userinfo response when the caller's scope includes profile. The VCI issuer (vci.ashx) loops back to userinfo when a member requests self-issuance, and BuildClaimsForVct mints the credential from what it finds. Missing fields surface as an actionable not ready message on the member's card.
These fields feed two credentials: the Identity Card (PID) (urn:eudi:pid:1, EUDI PID Rulebook v1.7) and the German PID (urn:eudi:pid:de:1, German PID Rulebook 1.0.0). Both need given_name, family_name and birthdate from the standard profile (edit those in register.html); the postal address also comes from the profile. The attributes below round out the cards.
birth_given_name).German PID Rulebook 1.0.0, namespace eu.europa.ec.eudi.pid.de.1. Empty fields are issued as empty strings, as the rulebook requires.
family_name_birth.1983-00-00 when unknown. Empty = same as birthdate.ISO/IEC 18013-5 attributes. All optional individually, but document_number, issuing_country, issue_date, expiry_date and at least one driving_privileges entry are needed for a useful mDL.
ISO/IEC DIS 7367-1 working attribute set. The VIN is validated (17 chars, ISO 3779, no I/O/Q). Mass fields are in kilograms.
DC4EU + CEN WS/eEHIC working attribute set. Not the national eGK — this is the cross-border EHIC.