-
The spec says:
> expected_origins: REQUIRED when signed requests defined in [Appendix A.3.2](https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#signed_request) are u…
-
In the wallet invocation section ( https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html#section-7 ) this is one of the options:
> no specific authorization_endpoint, u…
jogu updated
9 months ago
-
While testing OpenID4VP with the Sphereon wallet, I noticed that the signer of the JWT (vp_token) is a `did:key` DID (from the mobile wallet), while the holder (`credentialSubject.id`) of the containe…
-
The BLE transport is still in its early stages. Discussions on the future trajectory of the project are held here, to be moved to a better location in the future if necessary.
-
I'm currently implementing the vc+sd-jwt credential format profile for OID4VC and not fully sure how the process of a presentation works.
As I understand SD-JWT-VC spec, you make a presentation of …
-
Hi, I believe having transaction data in SIOPv4 authentication flow, similarly to OID4VP, can greatly improve user experience. There are implementation when SIOPv2 is used as passwordless authenticati…
-
In this pr:
https://github.com/ForkbombEu/signroom/pull/795
Change **openid4vp://** to **openid-credential-offer://**
-
My proposal would be:
- Section 5: HTTP header based syntax as currently defined but make clear that is not only for the token endpoint (merge 4.1 and 4.4 into this)
- Section 6: Alternative repre…
-
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…
-
Hi, I happened to notice by sheer coincidence that you copied our SIOPv2/OpenID demo repo.
I have 2 remarks/suggestions and 1 more pressing question.
- We yesterday updated our develop branch, b…