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

Rotate keys for a given Identifier #82

Open
1 task
abhi3700 opened this issue Jul 23, 2024 · 0 comments
Open
1 task

Rotate keys for a given Identifier #82

abhi3700 opened this issue Jul 23, 2024 · 0 comments
Assignees
Labels
auto-id Anything related to Auto-ID

Comments

@abhi3700
Copy link
Contributor

abhi3700 commented Jul 23, 2024

Currently, as per commit 70348e4 we use the same keypair to generate a new certificate for renewing a given identifier.

But we might have a use case as found in Verified Credentials (VC) notion doc where we need to rotate keys keeping same identifier. The steps would remain same as renew example, but need to use new keypair.

A common application of identifiers is their use in VCs. If a VC is issued to an identifier, as opposed to a public key, it will allow the holder of the VC to rotate their keys, while not needing to renew their VC.

In order to rotate keys for a given identifier, follow the steps below:

  1. Generate a new keypair
  2. Create a Certificate Manager with the keypair
  3. Issue certificate with the same Subject Common Name like test500.
  4. Use renewAutoId extrinsic to renew the existing auto id with new certificate.

    💡 New certificate has a new serial no. and new public key info.

Done! 🎉

Tasks

Preview Give feedback
@abhi3700 abhi3700 self-assigned this Jul 23, 2024
@abhi3700 abhi3700 added the auto-id Anything related to Auto-ID label Jul 23, 2024
@github-project-automation github-project-automation bot moved this to Todo in Auto-SDK Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-id Anything related to Auto-ID
Projects
Status: Todo
Development

No branches or pull requests

1 participant