-
Notifications
You must be signed in to change notification settings - Fork 516
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
[Question] Verifying presentations with the /vc/ldp/verify
endpoint
#2693
Comments
Can you add the VP you provided? I’m guessing it did have those fields? |
Note that a VP embeds an array of VCs in it, so it is not surprising that is expects a VC. Might not be the issue, but hard to tell without seeing the data. |
Here's a presentation. It can be verified with the uni verifier but aca-py returns the previous errors
|
Definitely looks like the validation is expecting a VC, not a VP. In the embedded VC, all of the “missing items” are present, so it is not checking that. A bit weird that the issuer is also presenting the credential, but I suppose anything is permitted. |
I just signed a random presentation of a VC I issued to test the feature, I agree this is a bit redundant. |
They seem to use the same code so that would make sense: |
It's the de-serialization step, it currently uses the VerifiableCredential class for both the vc and vp de-serialization. Looking at the VerifiablePresentation class, it could use some love and add some assertions to bring it up to par with the VerifiableCredential class and de-serialize properly. I can take this on. I think down the line it would be great to decouple vc and vp into their own respective routes (adding /vp/ldp/issue+verify and limiting the /vc/ldp/issue+verify for vc exclusively). I would also not get rid of the jsonld routes until issuance of a vp is enabled since the jsonld route can do that currently. |
Thanks @PatStLouis . Agree on the |
closing since #2710 was merged |
The endpoint accepts a "vp" in the body, so I'm assuming it can verify presentations. However, when I provide a vp it returns the following errors:
It looks like its still expecting a vc, is this the intended behavior?
The text was updated successfully, but these errors were encountered: