PID verification (ISO mdoc)
Description:
Verifies an ISO mdoc Person Identification Data credential (doctype
eu.europa.ec.eudi.pid.1) and returns family name, given name and date of birth.
This is the mdoc counterpart of the SD-JWT VC flow, and it exercises the parts of the
stack that are specific to ISO 18013-5: issuer anchoring against the IACA trust store
and VICAL, MSO validity, and device authentication accepted as either
DeviceSignature or DeviceMac — the MAC variant, derived over ECDH from the
reader's response-encryption key, is often where remote mdoc presentation breaks.
The request profile is unchanged: a signed JAR request object with an x509_hash
client identifier (HAIP 1.0 §5), served over request_uri (GET and POST), with the
response encrypted using direct_post.jwt.
Date of birth is requested rather than an age predicate because the EU reference PID
no longer carries an age attribute. Where a wallet can attest a predicate we ask for
that instead — see the driving licence use case, which requests age_over_21 and
never the date of birth.
Try it in the live demo; the verifier behind it is built by PASS2RENT (UAB Odifis).
QR code:
Processing YAML configuration...
Workflow YAML:
version: "1.0"
name: "PID verification (ISO mdoc)"
env:
host: "https://api.playground.france-identite.gouv.fr/odifis/eudi-demo"
tests:
pid-mdoc:
steps:
- name: "Create presentation request"
http:
method: POST
url: ${{ env.host }}/api/identity/start
headers:
content-type: "application/json"
accept: "application/json, text/plain, */*"
json:
kind: "fr-pid"
noAv: true
captures:
deeplink:
jsonpath: $.deeplink
qr:
jsonpath: $.qrDataUrl
sessionId:
jsonpath: $.presentationId
DCQL Query:
{
"credentials": [
{
"id": "pid",
"format": "mso_mdoc",
"meta": { "doctype_value": "eu.europa.ec.eudi.pid.1" },
"claims": [
{ "path": ["eu.europa.ec.eudi.pid.1", "family_name"] },
{ "path": ["eu.europa.ec.eudi.pid.1", "given_name"] },
{ "path": ["eu.europa.ec.eudi.pid.1", "birth_date"] }
]
}
]
}