[Story] Remote Attestation Presentation with Digital Credentials API on iOS (Cross - Device)

[marinakarampatsa]

User Story

Description

As a EUDI Wallet User
I want to present digital attestations to a requestor Relying Party residing on a different device (e.g., Laptop/Desktop) than my EUDI Wallet, by utilising browser capabilities
So that I can provide verified information seamlessly through the browser, without manual app switching.

Assumptions

• User is registered to a valid EUDI Wallet on their mobile device
• User is accessing the Relying Party via a Browser on a separate device (laptop/desktop)
• The Browser supports the Digital Credentials API (e.g., Chrome, Edge, Safari) and the required flags are enabled.
• Internet is available for connectivity and data transfer capabilities respectively between the Relying Party and the EUDI Wallet.
• Bluetooth (BLE) is enabled on both devices
• Relying Party is considered a certified EUDI Wallet ecosystem entity included in a Trusted List
• The User has not disabled the setting for disclosure of stored attestations via the Digital Credentials API framework in their Wallet
• The Relying Party creates and sends a valid presentation request.
• The mobile OS receives the presentation request and searches for suitable attestations.
• The Wallet Unit authenticates the RP and verifies the request origin.

Acceptance Criteria:

• User visits the Relying Party service on their Desktop/Laptop browser, where they are requested to present certain attestations
• User indicates they want to present attestations from their installed Wallet Unit by clicking the corresponding button (e.g., "Verify with EUDI Wallet" button)
• The Desktop Browser asks permission from the user to allow Digital Credentials API invocation from this website.
  • User grants permission to proceed.
• The Browser displays a QR code
• User scans the QR code using the camera on their mobile device
• If no suitable attestations are found, iOS displays a dedicated system screen notifying the user and ends the flow.
• When the system identifies one or more suitable attestations, the user sees an extension of the Wallet open automatically after selecting an attestation.
• User views the presentation request screen, which includes:
  • The verified identity of the requesting Relying Party
  • A list of the attestations and related attributes being requested
• User consents to share the selected attributes and enters their 6-digit PIN
• Relying Party service verifies the attestation, and the browser displays confirmation of the verification
  • If verification fails, the Relying Party displays an error message and allows the user to retry