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

Using verification method id to identify keys to sign creds in vc api #3078

Open
dbluhm opened this issue Jul 2, 2024 · 2 comments
Open

Comments

@dbluhm
Copy link
Contributor

dbluhm commented Jul 2, 2024

Related to #2991; this issue tracks our intent to be able to use verification method ids to sign JSON-LD credentials.

Support for identifying keys by verification method ID was recently merged in #2959. The support needs to be augmented to enable associating multiple kids with a key to better support the use case outlined in #2991.

cc @PatStLouis

@PatStLouis
Copy link
Contributor

@dbluhm from that pr, is the reverse possible, identify a verificationMethod.id from a registered did?

@dbluhm
Copy link
Contributor Author

dbluhm commented Aug 20, 2024

No; the challenge with this is that there is potentially more than one VM ID per DID. When signing a VC (either through the VC API or when issuing using DIDComm), what we really need is a clear unambiguous declaration of which VM should be used. I think this is best achieved by using the assertion verification relationship. If a specific verification method is not specified and just a DID is given, we can/should default to selecting the first valid VM (supporting the crypto type we're using) in the assertion list.

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

2 participants