One freight company.
Twelve ways to prove who's at the door.
Every card is a real app at Cascadia Freight, wired to Okta with the protocol that job actually needs. Run any flow and the Flow Recorder draws every redirect, back-channel call and validation step as it happens.
Dispatcher Console
Authorization Code + client secret
Dispatchers on the server-rendered web portal
Run flow →Driver Web App (SPA)
Authorization Code + PKCE (browser)
Drivers on a pure browser app, no backend secret
Run flow →Driver Mobile (native)
Authorization Code + PKCE (public client)
iOS/Android driver app, simulated as a native public client
Run flow →Rate Engine API
Client Credentials + client secret
Pricing service calling the internal Rates API
Run flow →Dock Kiosk
Device Authorization Grant
Shared loading-dock screen with no keyboard
Run flow →Legacy Yard Terminal
Resource Owner Password
Old green-screen terminal that can only POST a password
Run flow →Old Customs Portal
Hybrid + Implicit (form_post)
Pre-2019 portal still using front-channel tokens
Run flow →Partner EDI Gateway
Client Credentials + private_key_jwt
Ocean-carrier partner, no shared secret on the wire
Run flow →Token Inspector
Local JWT validation vs. introspection
Any engineer debugging a token
Run flow →Payroll & HR (SAML)
SAML 2.0 SP-initiated SSO
HR system that only speaks SAML
Run flow →Sign Out Everywhere
OIDC RP logout + SAML SLO
Shift ends: kill every session at once
Run flow →Hazmat Approval
Step-up with acr_values / max_age
High-risk action needs phishing-resistant MFA
Run flow →