Wallet Function: (Q)EAA Issuance and Presentation¶
The eIDAS proposal and the Architecture Reference Framework (ARF) describe (Qualified) Electronic Attestation of Attributes as generic, general purpose electronic credentials that attest any user data. QEAAs are provided by Qualified Trust Service Providers (QTSP) governed under eIDAS. EAA are provided by any Trust Service Provider that while supervised under eIDAS may rely on other contractual frameworks and trust domains. EAAs may also be provided by or on behalf of a public sector body responsible for an authentic source, in this case have to match specific requirements equally to QEAAs and both shall have the same legal effect as lawfully issued attestations in paper form. Any Relying Party may request presentations for QEAAs and EAAs if they are authorized under the eIDAS trust management for RPs.
Use Case Examples¶
The following use cases are examples for (Q)EAAs:
- mobile driving license
- municipal ID
- educational credentials, e.g. diploma
- payment
- ePrescription
- public transport ticket
Requirements¶
- Technical interoperability to ARF technologies
- Remote issuance
- Presentation for remote and proximity flows
- Support level of assurance required by use cases (details TBD)
Credential Formats & Protocols¶
As the PID and a (Q)EAA have the same technical foundation, the credential formats and transport protocols of the PID should also apply to (Q)EAAs. To achieve the best interoperability, the EUDIW should be limited to as few technological options as possible.
For the transport protocols the EUDIW shall support:
- OpenID4VCI
- in Pre-Authorized Code Flow
- in Authorization Code Flow
- OpenID4VP
For credential formats the EUDIW shall support:
- ISO mdoc according to 22230-2 / 18013-5
- IETF SD-JWT VC
Additional credential formats may be added if the use case requirements cannot be met by the existing formats.
Remote Issuance Flow¶
User Experience¶
User Journey: (Q)EAA Issuance - Authorization Code
User Journey: (Q)EAA Issuance - Pre-Authorized Code
Via the link, the user journey of the sequence diagram can be viewed in the form of lo-fi wireframe screen sequences. All screens of the User Journey are labeled with a specific name. Within the associated sequence diagram, green hexagonal markers labeled "Screen: screen_name" are placed to indicate the corresponding screen in that sequence. The Lo-fi wireframes primarily serve to illustrate the architecture flow from the UX/UI perspective and to show how an implementation could look from the UX/UI perspective. However, it should be kept in mind that the actual realization and implementation of the UX/UI is the responsibility of the wallet providers and the relying parties.
Remote Presentation Flow¶
User Experience¶
User Journey: (Q)EAA Presentation - Same Device
User Journey: (Q)EAA Presentation - Cross Device
Via the link, the user journey of the sequence diagram can be viewed in the form of lo-fi wireframe screen sequences. All screens of the User Journey are labeled with a specific name. Within the associated sequence diagram, green hexagonal markers labeled "Screen: screen_name" are placed to indicate the corresponding screen in that sequence. The Lo-fi wireframes primarily serve to illustrate the architecture flow from the UX/UI perspective and to show how an implementation could look from the UX/UI perspective. However, it should be kept in mind that the actual realization and implementation of the UX/UI is the responsibility of the wallet providers and the relying parties.
Proximity Presentation Flow¶
NOTE: THIS SECTION WILL BE DEVELOPED IN A FUTURE RELEASE
(Q)EAA Provider Trust Management¶
NOTE: THIS SECTION WILL BE DEVELOPED IN A FUTURE RELEASE