Skip to content

3.3.3 EAA Deletion

This flow describes the EAA deletion process.

Design Decision

The EAA deletion is triggered either because the user specifically wants to delete a single EAA from its wallet or because the user deletes all of the WI's data. In both cases, the UI shall clearly communicate the consequences:

  • all remaining instances of the EAA credential are deleted
  • the EAA can no longer be presented to Relying Parties
  • the user has to get the EAA re-issued by the EAA Provider, which requires a new EAA issuance including the user authentication and authorization at the EAA Provider

Unlike the PID deletion, no Remote WSCA account is involved: the DPoP key and the holder binding keys of an EAA are managed in the local Hardware Key Store (HKS) of the device (see EAA issuance, steps 028 and 042 - 044). The WI therefore only deletes local data, while the Remote WSCA account, the RWSCA-PIN and the PID remain untouched.

The EAA Provider is not contacted during the deletion and does not learn about the deletion.

Data Flow

This section describes the data flow of the EAA deletion in a sequence diagram and a more detailed table. Artifacts in italics are further explained in the data register chapter

Sequence Diagram

EAA deletionUserWallet Instance . App .WI.UserUserWallet Instance / App (WI)Wallet Instance / App (WI)(001)request to delete EAA(002)user consent(003)delete ep_eaa_credential[], wi_eaa_device_prvk[], ep_access_token,ep_refresh_token, wi_dpop_prvk, ep_meta_data

Detailed Description

No Description
001 The user clicks/triggers to delete one of its EAAs. The UI should communicate the user the impact and consequences of this operation.
002 The user consents to delete the EAA.
003 The WI deletes all data related to that EAA, this includes:
  • all the remaining EAA credential instances ep_eaa_credential and, for cryptographic holder binding, the corresponding holder binding keys wi_eaa_device_prvk from the local HKS
  • access token ep_access_token, refresh token ep_refresh_token and the wi_dpop_prvk that sender-constrains the access tokens of that EAA Provider
  • the stored metadata ep_meta_data of the EAA, such as the display information shown in the dashboard
Note that for claims-based holder binding no wi_eaa_device_prvk exists, as the EAA is not bound to a key. The deletion is local only, the EAA Provider is not notified and no data is deleted at the EAA Provider.