-
Notifications
You must be signed in to change notification settings - Fork 51
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 different keys for VC issuance vs VP signing causes VerificationError #103
Comments
Actually, I missed to add the suite of the issuer for the verification part ( I'm on the assumption the keys can be resolved from documentLoader ) having this works now const result = await vc.verify({
challenge,
suite: [suiteOfHolder, suiteOfIssuer],
documentLoader,
presentation: vp,
}); best if we don't share the private keys from the suites const holderPubKey = await keyPairOfHolder.export({ publicKey: true })
const issuerPubKey = await keyPairOfIssuer.export({ publicKey: true })
const result = await vc.verify({
challenge,
suite: [
new Ed25519Signature2018({
key: new Ed25519VerificationKey2018(holderPubKey),
}),
new Ed25519Signature2018({
key: new Ed25519VerificationKey2018(issuerPubKey),
}),
],
documentLoader,
presentation: vp,
}); but why do we need the Tnx |
Were you able to resolve this? I am now experiencing same. vc.verifyCredential and vc.verify (presentation) with IssuerSuite works but cant get it working with holder and also get the proof check by verifier? any suggestions? |
The tests when being run always uses the same KP for VC issuance and VP signing/verification.
Using a different KP for issuance will result in the presentationResult part as verified but failed in the :
snippet for issuance:
snippet for presentation:
snippet for failing verify:
but manual credential verification works:
The text was updated successfully, but these errors were encountered: