Wallet should not return credentials where the signature has expired
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 112
- Forks
- 38
- Avg merge
- 12d 19h
- Merged PRs (30d)
- 4
Description
Vaguely related to #159, as discussed on yesterday's WG call, we should probably clarify whether the wallet should return credentials that are expired and could no longer be validated.
For example, an SD-JWT where the current time is after the 'exp' header should not be returned to a verifier.
(For clarity, this is completely separate to the concept that an mDL that is cryptographically valid where the user's driving privileges have expired, which could still be used for identity validation purpose.)
[Kristina thought there might have already been an issue on this subject but I couldn't spot it.]
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 no repository files or tests. Start by reviewing the OpenID4VP wallet credential-returning requirements and the related #159 discussion; done means an agreed specification for handling credentials whose SD-JWT exp has passed, distinct from expired driving privileges.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100