-
Notifications
You must be signed in to change notification settings - Fork 69
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
Provide resolver options with verifyCredential
API
#285
Comments
verifyCredential
APIverifyCredential
API
Hi @nichonien, Can you say more about what why you need the resolver options, e.g. what are the use cases?
There are also DID resolution options ("DID resolution input metadata", e.g. The API of didkit web and node are based on that of didkit-http, which is based on VC API. The VC API verify operations don't have an option for DID resolution options or DID resolvers to use during verification. Possibly we could extend VC API to allow this - although the trend in VC API seems to be about reducing optionality, so maybe such options would have to be added outside the VC API data structures. |
Hey @clehner, The current requirement that we are looking at is to verify a We can verify a credential known before hand from a VP, but for the case where you also want to verify let's say |
Hi Team,
I'm currently exploring
didkit
for our projects with context to verifiable credential and presentation. The current implementation ofverifyCredential
inweb
ornode
module doesn't haveresolver_options
while I can see that it is very much there forcli
. Would it be possible to align all three modules with resolver option so thatdid
resolution andverification
could be consumed for last updated DIDDoc?If there is any specific reason why there is no resolver option for web or node modules, please help me understand as I might have missed or misunderstood the implementation. Appreciate your help!
The text was updated successfully, but these errors were encountered: