Skip to content
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

Support key rotation and key ordering #3289

Open
woutslakhorst opened this issue Jul 31, 2024 · 0 comments
Open

Support key rotation and key ordering #3289

woutslakhorst opened this issue Jul 31, 2024 · 0 comments

Comments

@woutslakhorst
Copy link
Member

woutslakhorst commented Jul 31, 2024

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant