Repository navigation
Replies: 4 comments
|
This is related to the token-status list from the SD-JWT-VC specification |
|
Hyperledger |
|
adorsys working implementation for status list server: https://github.com/adorsys/status-list-server |
|
@Captain-P-Goldfish @tdiesler @Ogenbertrand Thanks for sharing! Adding few more links from @thomasdarimont for the reference (Referencing "token status list"): |
Uh oh!
There was an error while loading. Please reload this page.
I wanted to raise one thing related to OID4VCI. I wonder if there is any standard API, which allows credential issuer (EG. Keycloak) to address the use-cases like:
Ability for Keycloak administrator to revoke some previously issued verifiable credential issued to some user
joeAbility for Keycloak administrator to revoke all verifiable credentials issued to some user
joeAbility for Keycloak administrator to see the available credentials of some user
joeFor example, user did some trespass when driving his car, so his driving licence VC should be revoked.
Regarding revocation, I suppose it can be nice to make sure that related OID4VCI credential is not possible to be used anymore by Wallet at corresponding OID4VC verifiers. So for example there is either:
There is a way to update some "revocation registry". So when administrator revokes credential, Keycloak will somehow update the revocation registry. This assumes that when later Wallet wants to present the credential to some verifier, the verifier will be able to check the "revocation registry" and see that credential was revoked.
Alternatively verifier can ask Keycloak itself to check if credential is still valid (I am thinking something similar to OAuth2 token introspection endpoint when OAuth2 RP can send request to Keycloak to check if particular OAuth2 access token issued by Keycloak is still valid).
Do you please know if there are any standard ways of doing this or any best practices?
All reactions