-
Notifications
You must be signed in to change notification settings - Fork 21
VCR: Add wallet credential search endpoint for expired/revoked credential management #4012
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
Conversation
|
Coverage Impact ⬇️ Merging this pull request will decrease total coverage on Modified Files with Diff Coverage (6)
🤖 Increase coverage with AI coding...🚦 See full report on Qlty Cloud » 🛟 Help
|
|
@copilot use |
Changed to use Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
ea24c5f to
773071f
Compare
docs/_static/vcr/vcr_v2.yaml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Improve the docs of the list:
Lists all VALID VCs in the holders wallet.
Perhaps adding a reference to the search operation for when you want to list ALL VCs.
I personally prefer adding some filter params to the list rather than creating an almost duplicate endpoint.
Something like:
GET /internal/vcr/v2/holder/{subjectID}/vc?include_invalid=true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like an endpoint that includes the revocation status, but the existing list endpoint only returns the credential. We can't simply change that due to backwards compatibility, that's why I decided to introduce a new endpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively, I could alter the List() call to include revoked/expired credentials, but UIs will still have to perform an API call for each credential to check revocation status.
1 new issue
|

This PR adds a new endpoint, that works exactly like the issuer's "search" API, to find credentials in a wallet that are revoked/expired. The existing
List()function on the wallet can't be used for that, since it filters out those unusable credentials (which is used for building VPs).So, as backwards compatible solution which mimics the existing
issuer.SearchCredentials()functionality, I added an API that does the same for wallets:It currently supports no search parameters yet, which can be added later if needed.
This API is required, for being able to inspect and clean up expired/revoked credentials (there's currently no way to list them).