Open robdefeo opened 2 months ago
I think this issue relates to issue #357 where the POST /credentials/issue
and POST /presentations
endpoints were modified to allow return of an EnvelopedVerifiableCredential
or an EnvelopedVerifiablePresentation
respectively.
However #357 didn't change the request schemas for the POST /credentials/verify
and POST /presentations/verify
, which I think should also be done. My initial thought is that adding EnvelopedVerifiableCredential and EnvelopedVerifiablePresentation as possible schemas for the verify endpoint request schema would be a good step.
As per https://www.w3.org/TR/vc-jose-cose/#securing-vps-with-jose I can see that the request is valid for
/presentations/verify
However for
credentials/verify
the format is a JWT which does not appear to be acceptable according toverifier.yml
. https://www.w3.org/TR/vc-jose-cose/#securing-with-joseexample secured credential, which has no envelope, however it would be valuable to be able verify
Also there are use cases when it would be helpful to verify
application/vc-ld+jwt
andapplication/vp-ld+jwt
directly, can the spec be adjusted to acceptstring
also