-
Current draft lacks a clear specification for verifiable presentations using BBS signatures. The specification should clarify whether the verifiable presentation BBS proof value can only be signed, on…
-
In the current PEX matching we implicitly require all VCs to have te same subject.id, and we require the signature on the VP to be the same as the subject.id of the VCs. When moving to the Subject (in…
-
Based on commentary in this issue about the complexity in PeX and it being viewed as too complicated for a presentation request language (I agree):
https://bitbucket.org/openid/connect/issues/1917/…
-
After deleting (deactivating the DID documents) a subject, the discovery publisher keeps trying to publish the subject. Resulting in a spammy log:
```
nuts-node1-1 | time="2024-09-20T12:57:56Z" l…
-
Doc: https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#section-3.1
- the same device interaction flow
- cross device interaction flow, QR code application
-
OpenId4VP requires the presence of `vp_formats` to client/verifier metadata
> vp_formats:
REQUIRED. An object defining the formats and proof types of Verifiable Presentations and Verifiable Cr…
-
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Currently, the janssen project and fro…
-
This issue outlines gaps in testing of Verifiable Credentials and associated specs (JSON Schema, Status List, Verifiable Presentations). Tasks may have partial test coverage today (linked if true). If…
-
Following the research on the verifiable presentation, implement the support for presentation definitions, similar to the credential definition
-
The current definition of "Holder" in the OpenID4VP specifications states:
> Holder: An entity that receives Verifiable Credentials and has control over them to present them to the Verifiers as Ver…