An expiration date sets a predictable limit on how long a credential remains valid. A credential can still be cryptographically valid after its claims become inaccurate, so expiration alone cannot catch unexpected changes such as lost employment or certification. section 16.4
Authorization systems also assign time-to-live (TTL) values to cached signals. Shorter TTLs refresh changing information sooner; different signals can use different durations according to how quickly they change and the risks of stale data. For credentials that become invalid unexpectedly, check issuer-published revocation information as well as expiration. section 12.4.2 section 16.4
Different validity windows
An employment credential might last one year, while an on-call status cache lasts five minutes and an employment-status cache lasts 24 hours. The differing windows reflect distinct freshness needs; revocation checks address unexpected invalidation. section 12.4.2 section 16.4
const onCall = await cache.getOrFetch(
`oncall:${employeeId}`,
{ ttl: "5m" },
() => pagerDuty.isOnCall(employeeId)
);
const employmentStatus = await cache.getOrFetch(
`employee:${employeeId}:status`,
{ ttl: "24h" },
() => hr.getEmploymentStatus(employeeId)
);
Compare the five-minute on-call cache with the 24-hour employment-status cache. section 12.4.2




