Specification conformance for Verifiable Credentials
The following table describes key options and their supported status:
| OpenID for VC feature | Supported? |
|---|---|
| Authorization code flow | Yes |
| Pre-Authorized code flow | Partial (is support by IBM® Verify OIDC provider only) |
|
Pre-Authorized code flow with out-of-band transaction code |
Yes (via IBM Verify OIDC provider) |
| Credential offer | Yes (authorization code flow) |
| Multiple credentials per offer | No |
| Authorize endpoint | Yes (via IBM Verify OIDC provider) |
| Authorize endpoint – additional parameters | Yes (via IBM Verify OIDC provider) |
| Authorize endpoint – rich authorization request | Yes (via IBM Verify OIDC provider) |
| Authorize endpoint – pushed authorization request | Yes (via IBM Verify OIDC provider) |
| Authorize endpoint – dynamic credential request | No |
| Token Endpoint | Yes (via IBM Verify OIDC provider) |
| Token Endpoint – pre-authorized code and transaction code |
Yes (via IBM Verify OIDC provider)
|
| Token Endpoint – authorization_details parameter |
Yes (via IBM Verify OIDC provider)
|
| Credential Endpoint | Yes |
| Nonce Endpoint | Yes |
| Bind VC to Identifier of holder | Yes (di_vp and jwt proof types only) |
| Deferred Credential Endpoint | No |
| Batch Credentials | No |
| Notification Endpoint | No |
| Client metadata | No |
| Credential Issuer metadata | Yes |
| VC Format ldp_vc – JSONLD with a Proof Suite | Yes (Ed25519Signature2020, BbsBlsSignature2020, bbs-2023 and eddsa-rdfc-2022) |
| VC Format mso_mdoc | Yes |
| VC Format jwt_vc_json | No |
| VC Format jwt_vc_json-ld | No |
| VC Format dc+sd-jwt | Yes |