nuts-foundation / nuts-foundation/nuts-node
Pruning short-lived credentials
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
With OpenID4VP, the Authorization Server will issue an EmployeeCredential (to the user's session wallet) for each initiated OpenID4VP flow. These will all be stored in the issuer's SQL database, never cleaned up.
Potential solutions:
- An apparent simple solution would be to introduce a cleanup-job for the issuer store, but when the Nuts node is used as primary VC issuer (e.g. CiBG), automated cleanup of issued credentials might destroy administration? Might also break statuslist2021?
- Alternatively, we could introduce a "store in issuer administration" flag, but that feels like hacky design (and leads to awkward APIs).
- Automatically clean up short-lived credentials
- ...
The requirements question behind it is; when would an issuer be cleaning up issued VCs?
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by tracing how OpenID4VP-issued EmployeeCredentials are stored in the issuer's SQL database, then establish retention and status-list requirements before choosing a cleanup approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100