Skip to main content

EAA ConformanceETSI TS 119 472-1 (v1.2.1) clause 5.2.10.1

EAA-5.2.10.1-04:Status JSON Object must include the type member

  • shall
  • Ordinary EAA
  • QEAA
  • PuB-EAA
  • SD-JWT VC
  • Issuer
  • Verifier

Spec text

The status JSON Object shall have the type member.

ETSI TS 119 472-1 (v1.2.1), clause 5.2.10.1, page 32.

In plain English

If the EAA carries a status component, the status JSON object must include a type member naming the status mechanism in use, e.g. TokenStatusList. The type tells the verifier which dereferencing and decoding routine to apply when fetching status.

Why it matters

The status component is polymorphic: there is more than one way to express revocation (Token Status List today, future mechanisms later). Without type, a verifier cannot tell which it is looking at, and may either fail open (skip the check) or fail closed (reject every credential).

Common mistakes

  • Including a status object without a type field.
  • Putting the status mechanism name in a non-standard place such as inside purpose.
  • Using a type value outside the registered set.

Conformance check

Auto-tested. Use the action in the sidebar to run a Self-Assessment for this control.

Last reviewed against ETSI TS 119 472-1 v1.2.1 on 2026-05-01.

iGrant.io’s EAA Issuer SDK handles this control out of the box. Talk to our team about closing your conformance gaps.