-
1.
According to OpenId4VCI specification authorization_details MUST be an array.
ref: https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-6.2
```
authorization_deta…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1936
### Original Reporter: KristinaYasuda
What if the Wallet sent the request to the credential endpoint, but the…
-
See https://github.com/openid/OpenID4VCI/pull/126
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1814
### Original Reporter: KristinaYasuda
currently we just say that any client metadata can go into a `client_me…
-
I suggest we should reference the current [draft 13 of OID4VCI](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-ietf-sd-jwt-vc) in this RFC, because it includes a creden…
ntsbs updated
6 months ago
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1759
### Original Reporter: danielfyes
The normal credential endpoint is really a specialized instance of the batc…
-
### Description
Implement the SIOPv2 protocol into the Agent. Similarly to the OpenID4VCI implementation, the agent must have a method to generating an `auth_request` that can be displayed by the "Fr…
-
According to this
https://github.com/openid/OpenID4VCI/pull/64/files
-
We should do something with the ISO mdoc section of VCI; it's not clear about various things - e.g. what exact CBOR object should be returned in the credential response.
It currently says:
> str…
-
Another breaking change is on the way
https://github.com/openid/OpenID4VCI/pull/199