Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revocation request flows triggered by different Entities than WI and CI #369

Open
peppelinux opened this issue Jul 25, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@peppelinux
Copy link
Member

The revocation flow could be triggered by:

  1. Legal Authority or law enforcement
  2. Wallet Provider (if it enables this feature)
  3. Authentic Source

The current version specify only the protocol interface between the Wallet Instance and the Credential Issuer. We probably should define protocol interfaces for the above entities in a future milestone.

@peppelinux and @fmarino-ipzs, do you agree?

Originally posted by @m-basili in #308 (comment)

@peppelinux
Copy link
Member Author

During the meeting of the 31 July 2024 we have discussed that:

  1. for public players PDND is suitable, not clear about playing with private sector Wallet Provider using PDND
  2. for legal authorities we must provide out of band mechanisms, therefore these must be considered out of the scopes of the technical specification
  3. [revoke-all proposal] wallet provider may use an endpoint about the revocation of all the credentials issued about a specific subject (if the holder enables/gives consent to inform the wallet provider about the digital credentials hold)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

No branches or pull requests

4 participants