feat: support w3c revocation #2072
Conversation
|
|
Hello @TimoGlastra, wanting to create a separate PR for w3c revocation, due to some conflicts in the original PR #2024 . I'll start with integrating the changes you suggested |
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
…ormats Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
GHkrishna
force-pushed
the
feat/support-w3c-revocation
branch
from
b2e1d60 to
078c43c
Compare
Signed-off-by: Krishna Waske <[email protected]>
| agentContext: AgentContext, | ||
| options: RevokeCredentialOptions | ||
| ) { | ||
| const credentialRecod = await this.getCredentialRecordById(agentContext, options.credentialRecordId) |
There was a problem hiding this comment.
- I think we should not use the credentialRecord to get tags as credentialRecord may or may not be present in wallet. To get the claimFormat we can use options
There was a problem hiding this comment.
Ahh yes you are right. Also as the specs suggest the issuer may not always be the one revoking the credential. Will change it
...ules/vc/models/credential/w3c-credential-status/bitstring-status-list/BitStringStatusList.ts
Outdated
Show resolved
Hide resolved
…ist credential Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
Signed-off-by: Krishna Waske <[email protected]>
What
This PR introduces support for W3C credential revocation. The following changes have been made:
Refactor functionality for Verify Credential and Verify Presentation.
Integrated with the Bit String Status List for checking and updating credential status.
How
Revocation Flow: Implemented the revocation flow by checking a credential status and updating the credential issuance process to handle revocable credentials.
Integration: Integrated the new revocation features with the existing system, ensuring compatibility and proper handling of revoked credentials.