Skip to main content

VC Knots Coverage

The following tables are organized based on OpenID for Verifiable Credential Issuance 1.0 and OpenID for Verifiable Presentations - draft 24, and describe the current implementation scope of this repository.

means that the feature is implemented for the relevant role. means that it is not implemented or is not available end to end. Conditions for configuration-dependent features are described in the notes column.

OpenID for Verifiable Credential Issuance 1.0

Specification sectionFunctional areaSpecification role / featureIssuerWalletNotes
3.5Issuance FlowPre-Authorized Code FlowSince v0.6.0
Current standard flow.
3.4Issuance FlowAuthorization Code FlowNot supported end to end.
4.1Credential Offercredential_offer (Pre-Authorized Code)Since v0.6.0
✅ Generate
✅ ParseReference-based credential_offer_uri is not supported.
3.5Transaction Codetx_codeSince v0.6.0
✅ Issue / validate
✅ SendUsed in the Pre-Authorized Code Flow.
A.1Credential Formatjwt_vc_jsonSince v0.6.0
✅ Issue
✅ Receive
A.3Credential Formatdc+sd-jwt (SD-JWT VC)Since v0.6.0
✅ Issue
✅ Receive
A.2Credential Formatmso_mdoc
6Token EndpointAccess Token issuanceSince v0.6.0
Supports the Pre-Authorized Code Flow.
13.2Client Authenticationprivate_key_jwtSince v0.6.0
✅ Validate
✅ SendClient authentication method for registered OAuth clients at the Token Endpoint. The wallet defaults to anonymous (none); it sends a client assertion only when the wallet is configured for private_key_jwt and the Authorization Server Metadata advertises both private_key_jwt and the configured signing algorithm. Related section: 6.1
6.1Client AuthenticationAnonymous Pre-Authorized Token RequestSince v0.6.0
✅ Conditional
✅ SendAvailable only when pre-authorized_grant_anonymous_access_supported is true in the Authorization Server Metadata. Related section: 12.3
13.2Sender ConstraintDPoP sender-constrained Access TokenSince v0.6.0
Configurable as off, optional, or required. Applied to the Token Endpoint and Credential Endpoint. Related sections: 6.1, 7.2, 8.2. External spec: RFC 9449
8Credential EndpointCredential Request / ResponseSince v0.6.0
8.2Credential ProofJWT ProofSince v0.6.0
✅ Validate
✅ GenerateProof of possession of the key for the Credential. Only a single Proof is currently supported.
7.2NonceOpenID4VCI c_nonceSince v0.6.0
✅ Issue
✅ Retrieve / useCredential Proof nonce returned in the JSON body of POST /nonce.
7.2NonceDPoP-NonceSince v0.6.0
✅ Conditional
✅ ConditionalResponse header used for the DPoP challenge. It is a different value from c_nonce. External spec: RFC 9449
12.2MetadataCredential Issuer MetadataSince v0.6.0
✅ Unsigned JSON
✅ RetrieveSigned Metadata is not supported.
6.1.1Credential Selectionauthorization_detailsNot supported end to end in Token Requests / Responses.
3.3.4Credential Selectioncredential_identifierPartialcredential_identifiers integration in the Token Response is not supported. Related section: 6.2
3.3.2Credential IssuanceBatch Credential Issuance
9Credential IssuanceDeferred Credential Endpoint
10EncryptionCredential Request encryption
10EncryptionCredential Response encryption
11NotificationNotification Endpoint

OpenID for Verifiable Presentations - draft 24

Specification sectionFunctional areaSpecification role / featureVerifierWalletNotes
5Authorization RequestAuthorization RequestSince v0.6.0
request_uri, URL-encoded parameters
request, request_uri, URL-encoded parameters
6Credential QueryDCQL
5.4Credential QueryPresentation ExchangeSince v0.6.0
External spec: DIF Presentation Exchange
5Authorization RequestSigned Authorization Request (JAR)Since v0.6.0
Uses a Request Object. External spec: RFC 9101
5Authorization RequestEncrypted Authorization Request (JAR)External spec: RFC 9101
5.6Credential QueryAuthorization Request using scope
5.10.4Client IdentificationClient Identifier SchemeSince v0.6.0
redirect_uri, x509_san_dns
redirect_uri, x509_san_dns
5.11Request URIRequest URI MethodSince v0.6.0
✅ GET
✅ GET, POST
10MetadataWallet Metadata
8.1Authorization ResponseAuthorization ResponseSince v0.6.0
8.5Authorization ResponseAuthorization Error Response
8.3Authorization ResponseEncrypted Authorization Response
8.2Response ModeResponse ModeSince v0.6.0
direct_post
direct_post
8.4Transaction DataTransaction DataSince v0.6.0
12Client AuthenticationVerifier Attestation JWT
Appendix ADigital Credentials APIDigital Credentials API / DC API
Appendix B.4Credential FormatSD-JWT VC format (dc+sd-jwt)Since v0.6.0
Appendix B.4.5Holder BindingSD-JWT VC Key Binding / KB-JWTSince v0.6.0
Appendix B.1.1Credential Formatjwt_vc_json formatSince v0.6.0