Smart Token Security Pipeline: Sign, Verify, Expire, Revoke

Token Issuance

Token lifetime (TTL) 8 s

Issue rate 1.5 / s

Threat & Response

Attacker tamper probability 15%

Admin revocation rate 0.4 / s

Gate Order

Gate 1 — HMAC signature check Gate 2 — expiry (exp claim) check Gate 3 — revocation deny-list check All passed → access granted

Live Readouts

In flight

Granted

Bad signature

Expired

Revoked (blocked)

Grant rate

100%

How it works

A smart access token (JWT-style) is three parts joined by dots: header.payload.signature. The signature is a keyed hash over the first two parts:

sig = HMAC(secretKey, base64url(header) + "." + base64url(payload))

Each token launched here carries a simplified signature computed the same way (a keyed checksum over its payload). Three independent gates decide whether it is honoured:

Gate 1 — Signature. The verifier recomputes the checksum over the payload it actually received and compares it to the stored signature. If an attacker tampered with the payload (e.g. escalated a role) without the secret key, the recomputed value can never match — tamperProbability below controls how often this is attempted.
Gate 2 — Expiry. Every token embeds exp = issuedAt + TTL. The gate simply checks now > exp. Short TTLs are safer (a stolen token is useless sooner) at the cost of more re-issuance traffic — that trade-off is exactly what the TTL slider lets you feel.
Gate 3 — Revocation. Signed tokens are stateless, so the only way to kill one early (a logout, a compromised account) is a server-side deny-list keyed by token ID, checked on every request. The admin-revocation slider simulates security ops adding still-valid tokens to that list mid-flight.

A token must clear all three gates to reach the green platform. Failing any one immediately routes it into the red quarantine trough with the failing reason recorded — exactly how a real API gateway short-circuits on the first failed check.

Sign Expiry Revoke Granted

⚠ Couldn't load the 3D engineThree.js failed to load from the CDN. Check your connection and reload.