Update credential revocation reason from issuer's perspective (#307)

* Update credential revocation reason from issuer's perspective this pr aims to solve this issue #266 * Added how a user can authenticate in case of loss of the priv key * editorial update Co-authored-by: Giuseppe De Marco <[email protected]> * Apply suggestions from code review * Update docs/en/revocation-lists.rst * Apply suggestions from code review --------- Co-authored-by: Giuseppe De Marco <[email protected]> Co-authored-by: Francesco Grauso <[email protected]>
italia · Jun 26, 2024 · c2a6d8f · c2a6d8f
1 parent 3bc6eb4
commit c2a6d8f
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/en/revocation-lists.rst b/docs/en/revocation-lists.rst
@@ -57,8 +57,8 @@ Functional Requirements
 - revoke a Digital Credential when the following circumstances occur:
 
   - the Digital Credential requires to be updated, whenever one or more attributes are changed; in this case the User will request a new issuance for that Digital Credential;
-  - the Wallet Instance that holds the Digital Credential was issued is revoked;
-  - the User deletes the Digital Credential from the Wallet Instance;
+  - the Holder needs to address the loss or compromise of cryptographic key material associated with the issued Digital Credential. In such case, the End-User should request the revocation of the Digital Credential through a service provided by the Credential Issuer and using an authentication method that offers the same Level of Assurance obtained during the Credential Issuance;
+  - the User deletes the Digital Credential from the Wallet Instance. The Wallet Instance therefore should request the revocation of such Digital Credential to the Credential Issuer;
 
 - provide a web service for allowing a Wallet Instance, with a proof of possession of a specific Digital Credential, to