Support CredentialQuery with empty `elements_dict`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Currently, Credential Queries must include at least one requested element. There exist a number of niche cases where it may be useful to request no elements. Semantically, this is proving you are in possession of a document of a particular type.
- This can be used as a 'proof-of-human' signal, as it's a strong proof that this is a user.
- This can be used with TransactionData in a case where you want something signed, but you don't care about the identity of the user
- (SD-JWT-VC Specific) You can get back mandatory claims (minorly efficient)
These are pretty niche, but limiting it in-spec doesn't seem particularly desirable, but we can discuss.
Raised by Martijn, this is does then require showing sensible UI for this, which is challenging.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names CredentialQuery and elements_dict but no files or tests; start by locating their handling in the repository and reviewing the existing empty-query validation. Done means empty queries are supported with sensible UI, including the described proof-of-human, TransactionData, and SD-JWT-VC cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100