-
As per https://www.rfc-editor.org/rfc/rfc9101#name-cross-jwt-confusion it is a strong recommendation to use the `Content-Type` HTTP Header `application/oauth-authz-req+jwt` and set the `typ` claim to …
-
The example from Token Request at the current spec: https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#section-6.1-9
```
POST /token HTTP/1.1
Host: server.e…
-
[RFC9449](https://www.rfc-editor.org/rfc/rfc9449.html#name-concept) defines `DPoP JWT` as a way to:
- Ensure that an issued `access_token` is used by the client (wallet) that requested it, and
- …
-
we need to add the presentation part of the SD-JWT VC profile to OID4VP (https://openid.github.io/oid4vc-haip-sd-jwt-vc/draft-oid4vc-haip-sd-jwt-vc.html#name-presentation-definition) before we can rem…
-
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1744
### Original Reporter: KristinaYasuda
in VCI, we have user\_pin\_required feature. given pin is a useful feat…
-
In the current version of the Credential data model, we have a selective disclosable `evidence` field. We need to clarify the sub-claims included in the `evidence`. We don't enable nested SDs. Then th…
-
According to
https://github.com/openid/OpenID4VCI/pull/86#issuecomment-1777155395
the structure of credentials_supported is going to change, please provide your position for that
-
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…
-
Selective-Disclosure enabled credential formats give the inherent mechanism for data minimization.
Therefore, the need to specify the claims that shall be in a credential (done in authorization_det…
-
The current Digital Credential Data Model, draws from the OpenID Identity Assurance Profile [OIDC.IDA], needs the changes described below:
- The verified_claims parameter be capable of holding an A…