HAIP SD-JWT VC certificate-backed signer and status list references
OID4VCI 1.0 §11.2 and HAIP 6MUSTRoles: issuer
Requirement as recorded in the ProtocolSoup registry
HAIP SD-JWT VC metadata and credentials use an asymmetric certificate-backed signer, and issued credentials carry unique OAuth Status List references. URL-based vct values resolve to matching Type Metadata, and SD-JWT claims use the top-level claim model.
Read §11.2 and HAIP 6 in OID4VCI 1.0Self-test verdict
PassCommit 97df6a8Evaluated
This is ProtocolSoup's result against its own implementation at the commit shown. It is not a certification of ProtocolSoup or of any other product.
Tests
- TestSignedCredentialIssuerMetadataUsesTrustedX5CSigner
./internal/protocols/oid4vci
Pass - TestHAIPSDJWTCredentialUsesTrustedX5CSigner
./internal/protocols/oid4vci
Pass - TestHAIPStatusListAllocatesUniqueIndicesAndServesSignedToken
./internal/protocols/oid4vci
Pass - TestUniversityDegreeTypeMetadataMatchesAdvertisedVCT
./internal/protocols/oid4vci
Pass