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

How to allow a existing key for a new purpose #27

Open
lemoustachiste opened this issue Sep 20, 2022 · 0 comments
Open

How to allow a existing key for a new purpose #27

lemoustachiste opened this issue Sep 20, 2022 · 0 comments

Comments

@lemoustachiste
Copy link

In my did document, the initial key created was authorized for authentication.
I would like the key to also be valid for assertion, so I was curious how I would go about to update the document to add the key into the assertionMethod array?

If I look at this: https://github.com/decentralized-identity/ion-tools#generateoperationtype-contents-commit-async, I could use an update event, but after that I am confused if I should use the addPublicKeys object, where I would just use the same id (hence overwriting?) and specifying the purposes ( ['authentication', 'assertion']?),

or should I use updatePublicKey via this interface: https://github.com/decentralized-identity/ion-tools/blob/9c6572daf91cc59f4bd489eb51da261d2483c0be/ion.js/lib.js#L172. Is the shape of the key object the same in both cases? How do I configure to pass through this object path: op.previous.update.publicJwk?

Thanks

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