JWT Token Flow Tech Architecture Infographic | dfd network

Tech architecture infographic titled "JWT Token Flow" using archetype PROTOCOL HANDSHAKE, designed for a non-technical executive audience. Show a clear left-to-right numbered exchange with labeled boxes connected by directional arrows: User Browser, API Gateway, Auth Service, Token Cache, Application API, User Database, Background Queue, and Generic Cloud Network. Each box must include a simple icon, the component name in canonical English-tech form, and a one-line English role description. Example box roles: Browser — 'User client sending login and API requests'; API Gateway — 'Routes HTTPS requests and enforces access rules'; Auth Service — 'Validates credentials and issues JWT'; Token Cache — 'Stores session metadata or revoked token IDs'; Application API — 'Verifies JWT and serves protected data'; User Database — 'Stores user records and password hashes'; Background Queue — 'Processes async audit or notification jobs'; Generic Cloud Network — 'Represents external network boundary'. Show arrows with precise English labels for what crosses: 'HTTPS POST /login', 'Credentials', 'SELECT user', 'User record', 'JWT access token', '200 OK + JSON', 'Authorization: Bearer JWT', 'JWT verification', 'Protected resource JSON', 'Revoke token ID', 'Audit event'. Include trust boundaries or dashed zones for Client, Edge/API, Identity, Application, Data, and Async Processing. Add small protocol callouts where accurate: HTTPS, REST, JWT, TCP. Do not overstate security; present as an explanatory flow, not an audited reference architecture. Add a numbered legend 1-7 in English walking through lifecycle: 1. User submits credentials from Browser over HTTPS. 2. API Gateway forwards login request to Auth Service. 3. Auth Service checks user data in User Database. 4. Auth Service returns signed JWT access token in a 200 OK JSON response. 5. Browser calls protected REST endpoint with Authorization: Bearer JWT. 6. Application API verifies JWT signature and optional revocation state using Token Cache, then returns protected data. 7. Optional logout or security event writes revocation or audit work to Queue and Cache. Visual style: retro 1980s computing, blueprint cyan palette, glowing cyan lines on deep navy background, technical grid, CRT terminal accents, subtle scanline texture, geometric UI panels, crisp vector shapes, clean spacing, high contrast for executive readability. Overall mood: trustworthy, technical, explanatory, nostalgic computing schematic. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).