nuts-foundation / nuts-foundation/nuts-node
Support key rotation and key ordering
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Currently the VerificationMethod SQL table has a weight property that can be used to sort keys. This will allow newer keys to get preference over older keys.
Also:
Hashicorp vault and azure keyvault support keyroration where a key with the same keyname gets a new version (preventing the use of older keys). We do not use this feature.
We generate a new uuid for the backend when creating a new key.
When adding proper key rotation we probably want to make use of this backend feature. This means that a Rotate(keyname) (keyname, version) method has to be added to the backend and a RotateKey(DID, KeyFlags) error to Crypto (creates a new VerificationMethod with bigger weight using rotate on the backend)
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
Start by locating the VerificationMethod SQL table and the backend and Crypto interfaces mentioned in the issue. Define how backend key rotation and version handling should work, then ensure RotateKey creates a new VerificationMethod with a greater weight; the issue provides no named files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- backend, cryptography, databases, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100