EAA ConformanceETSI TS 119 472-1 (v1.2.1) clause 4.2.11.1
EAA-4.2.11.1-03:shortLived and status service are mutually exclusive
- shall
- Ordinary EAA
- QEAA
- PuB-EAA
- SD-JWT VC
- mdoc
- Issuer
- Verifier
Spec text
An EAA that incorporates the EAA short-lived component (clause 4.2.13 of the present document), shall not incorporate the EAA status service.
ETSI TS 119 472-1 (v1.2.1), clause 4.2.11.1, page 23.
In plain English
An EAA can either be short-lived (briefly valid, re-issued on demand) or use a status service (longer-lived, with revocation state published separately), but never both. Pick one revocation strategy per credential.
Why it matters
The two mechanisms are alternative answers to the same question: how does a verifier know whether the credential is still good? Combining them creates ambiguity (which signal wins?) and forces verifiers to do more work than needed; the spec resolves this at issuance time by making them mutually exclusive.
Common mistakes
- Issuing a long-lived EAA with both a status claim and a shortLived marker.
- Treating shortLived as a quality flag rather than a revocation strategy choice.
- Forgetting that shortLived removes the verifier's need to consult any status list.
Conformance check
Auto-tested. Use the action in the sidebar to run a Self-Assessment for this control.