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 Flows - Revocation Request by Wallet Instance - Step 2 (PoP Verification) - Editorial Changes #424

Closed
pietroACN opened this issue Sep 25, 2024 · 2 comments · Fixed by #426
Assignees
Milestone

Comments

@pietroACN
Copy link

pietroACN commented Sep 25, 2024

The actual text states:

Step 2 (PoP verification): The Credential Issuer verifies the signature of the PoP using the the confirmation method that was attested in the issued Digital Credential. If the verification is successful, it means that the Wallet Instance owns the private keys associated with the Digital Credential, and therefore is entitled to request its revocation.

We propose to change "PoP" with "revocation_assertion_requests object"

Final Text would look like:

Step 2 (Revocation Assertion Request verification): The Credential Issuer verifies the signature of the revocation_assertion_requests object using the the confirmation method that was attested in the issued Digital Credential. If the verification is successful, it means that the Wallet Instance owns the private keys associated with the Digital Credential, and therefore is entitled to request its revocation.

@peppelinux
Copy link
Member

ok

@peppelinux
Copy link
Member

Fatto qui: #426

@peppelinux peppelinux added this to the 0.8.1 milestone Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants