EAA ConformanceETSI TS 119 472-1 (v1.2.1) clause 5.2.1.2
EAA-5.2.1.2-01:SD-JWT VC EAA must include the vct claim
- shall
- Ordinary EAA
- QEAA
- PuB-EAA
- SD-JWT VC
- Issuer
- Verifier
Spec text
A SD-JWT VC EAA shall include the vct claim as specified in IETF SD-JWT VC, which shall implement the semantics specified in clause 4.2.1.2 of the present document, and that shall be associated to the SD-JWT VC Type Metadata.
ETSI TS 119 472-1 (v1.2.1), clause 5.2.1.2, page 27.
In plain English
Every SD-JWT VC EAA must carry a vct claim. This is the credential-type identifier; verifiers use it to look up the SD-JWT VC Type Metadata document and learn the shape of the payload. Without vct, the EAA cannot be parsed as anything more specific than a generic SD-JWT.
Why it matters
vct is how the rest of the SD-JWT VC machinery (Type Metadata, schema validation, status type lookup) is bootstrapped. A verifier cannot evaluate the EAA against any EUDI rule until it knows which credential type it is looking at.
Common mistakes
- Omitting vct entirely and treating the EAA as a generic SD-JWT.
- Setting vct to a private string with no published Type Metadata.
- Using a vct value that points to a metadata document the verifier cannot dereference.
Conformance check
Auto-tested. Use the action in the sidebar to run a Self-Assessment for this control.