SECURITY · ACCESS INSPECTION DESK
Access control: identity before permission
Inspect credential claims, policy gates and the resource decision. Change a condition and follow the exact denial reason.
Your experiment
Compare a missing token, an untrusted issuer and a valid token without permission. Identify the first denying gate and distinguish 401 from 403.
Prediction is computed immediately; Play reveals each gate in order. A denial prevents every later gate from running. Capture a baseline before changing one field.
Illustrative claims
Decision trace
Offline policy exercise—not a JWT validator, OAuth server or production security boundary. Verification is an injected test result; no cryptography, real tokens, keys or records are used. Never rely on browser controls to enforce real authorization. Roles, gate order and strict same-tenant rules are application-specific assumptions, not universal OAuth requirements. Expiry is evaluated at a fixed instant; animation does not age the token. No revocation, clock skew or delegation is modeled. Bearer token reference · JWT claims reference.
Distinguish an identified caller from an allowed action
A present credential is not enough to open the resource vault. Authentication facts must pass before the application considers tenant, scope and role. This exercise makes the ordering visible so that a failed identity check cannot be mistaken for a role problem. The full claim card explains which fixture facts the gate sees; no real account or customer credential is used.
Supply the credential and resource facts
Bearer credential present and Trusted verification result control the first two authentication gates. The latter is an injected authenticator result, not an actual signature computation. Issuer selects a trusted or unknown issuer; Audience chooses this agent API or another API. Seconds until expiry is evaluated at a fixed instant, with zero already expired. Principal tenant and Resource tenant define the boundary. Role selects viewer, operator or admin; Requested action chooses read, write or delete. The read, write and delete scope checkboxes represent independently granted token scopes. Changing a fact resets inspection of the same ordered policy.
Compare three distinct denials
At defaults, a verified team-a viewer with read scope can read a team-a resource and receives HTTP 200. Remove the bearer credential and the first gate returns 401; all later checks remain not-run. Restore it and select another API as audience: authentication still fails, but now at the audience gate. Restore this API and request write without write scope: authentication passes and the request receives 403 at the scope gate. Enable write scope while retaining viewer role; the denial moves to role permission instead of disappearing.
Inspect first denial and later gates
The desk evaluates token presence, verification, issuer, audience, expiry, tenant, required scope and role in that order. The first denial determines the displayed HTTP result. Later gates are not-run, not additional failures or successful checks. The credential JSON and policy preview describe the complete selected scenario before animation finishes. Play reveals eight gates over thirty-two seconds at normal speed; Pause holds progress, Step advances one gate, Restart rewinds and Speed chooses half, normal or double inspection pace. Edits start playback unless reduced motion is requested. The resource vault opens only after inspection reaches the final decision and every required policy has passed.
Keep the security boundary explicit
This is a deterministic application authorization policy over fixture claims. It does not parse a JWT, retrieve a JWK, verify a cryptographic signature, issue an OAuth token, run a real identity provider or contact a protected endpoint. The verification checkbox is evidence supplied to the policy, not a way to bypass real cryptography. Expiry is not a live countdown; no clock skew, refresh flow, revocation, multiple audiences or scope hierarchy is implemented. Admin privileges are tenant-local in this fixture. HTTP 401 and 403 are the chosen teaching policy outcomes, not a claim that every provider uses this exact gate order or error text.