-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1603
### Original Reporter: KristinaYasuda
The Use-case is the following; the verifier wants to request the wallet…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/2052
### Original Reporter: peppelinux
In “[6.3.1. ](https://openid.bitbucket.io/connect/openid-4-verifiable-prese…
-
A client does a `/internal/auth/v2/create-access-token` request (part of other issue/pr). The node will request authorization via `GET /identity//authorize`. We currently only support getting an acces…
-
Section 6 only defines 3 response_types that return VP tokens:
whereas 'A.4. Combining this specification with SIOPv2' says that `response_type=id_token` can also return a VP token:
It s…
jogu updated
8 months ago
-
The PID Presentation Definition paths must be updated as per: https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#name-presentation-request-4
Reference: https://github.com/eu-digita…
-
Based on what verifier is able to specify what credential it needs: any piece of data in a credential, or a common list of parameters (current list is format, type, specific claims, verifier's intenti…
-
Currently, it is not supported to send multiple VPs in the authorization repsonse, if the request only contained a single presentation definition. The number of VPs must match the number of PDs.
Ho…
-
Please explain how credential issuer accepts the key provided in proof parameter - should any public key be accepted? Lets assume that the authorization server and credential issuer are separate entit…
-
Both on the original (outer) and OpenID4VP (inner) requests.
-
Depends on #2359
This issue describes requirements for the openid4vp authorization response. It provides support for a client to respond to the request as defined in #2357.
This issue only descr…