SecurityEventTokenValidationStates Enum
The facts a validation pipeline has established so far about the token in flight. Each step records what it proved, and a step whose safety depends on an earlier proof declares that through Require(SecurityEventTokenValidationStates) - which is what turns a mis-ordered pipeline into a loud first-run failure instead of a silently skipped check.
public enum SecurityEventTokenValidationStatesFields
None 0
Nothing established yet: the token is an opaque string.
Parsed 1
The compact serialization was taken apart and its header and claims parsed. The parsed values are NOT yet trustworthy - parsing establishes shape, only a verified signature establishes authorship.
TypVerified 2
The "typ" header names a SET (RFC 8417 Section 2.3).
ExpAbsenceVerified 4
The claims carry no "exp" - the marker whose absence separates a SET from the ID and access tokens it could be confused with (RFC 8417 Sections 4.1 and 4.2).
EventsPresent 8
The "events" claim is present, is a JSON object, and holds at least one statement (RFC 8417 Section 2.2).
IssuerAccepted 16
The "iss" claim names an issuer this receiver accepts events from.
SignatureVerified 32
The signature was verified against the issuer's keys. From here on the claims are the issuer's words, not just well-formed JSON.
AudienceVerified 64
The "aud" claim names this receiver.
IssuedAtVerified 128
The "iat" claim is present and within the receiver's freshness window.
PayloadsDeserialized 256
Every event payload was deserialized through the registry - into its registered model or the raw passthrough.