France Identitรฉ Partenaires โ ISO/IEC 18013-5 proximity¶
โ Back to the Partenaires app overview
This guide describes the proximity presentation flow from the France Identitรฉ Partenaires app. The app acts as the mdoc holder and exposes the credential over a Bluetooth Low Energy (BLE) engagement.
ISO 18013 reference
For live access to the latest published versions of the ISO/IEC 18013 documents, use the OpenWallet Foundation's mdoc.online.
ISO/IEC 18013-5 defines the mdoc data model and native BLE proximity exchange.
Test the proximity flow¶
- Open the ID card from the Partenaires application home screen.
- Flip the card.
- Scan the QR code with the reader device to initiate the BLE exchange.
- Review and approve the requested attributes in the wallet.
- Complete the BLE exchange on the reader and verify the returned mdoc.
A browser-based proximity reader is available in the playground: mdoc web verifier. It requires a Chromium-based browser and must be configured to request the credential type being tested.
What the reader must verify¶
The reader should validate the complete ISO/IEC 18013-5 exchange, not only display decoded values:
- the mdoc
docTypeand requested namespaces; - the issuer authentication (
issuerAuth) and issuer certificate chain; - the issuer-signed item digests in the MSO;
- the device authentication and holder binding using the session transcript;
- the validity information and status checks required by the test environment.
Use the test data and trust material page to select the correct Partenaires trust chain. Do not use production trust anchors for credentials issued in the playground environment.
Do not diagnose a failure in one transport as a failure in the mdoc itself until the credential has been decoded and its issuer authentication, digests, and holder binding have been checked.
Troubleshooting¶
| Symptom | Check |
|---|---|
| The QR code does not start BLE | Confirm Bluetooth is enabled, the reader supports the required engagement, and the app has the required nearby-device permission. |
| The reader sees an empty or unparseable document | Check that the returned value is a complete mdoc Document encoded as CBOR, not JSON or a diagnostic Buffer object. |
| Issuer authentication fails | Use the Partenaires/pre-production trust anchor and verify the full certificate chain. |
| Device authentication fails | Verify the session transcript and that the reader validates the device signature against the holder key in the MSO. |
| The card is not displayed | Confirm the doctype, namespace, element identifiers, and CBOR value types are supported by the reader. |