Cascadia Freight Identity Control Tower
Sign in
Okta Workforce Identity · live demo

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.

01Recommended

Dispatcher Console

Authorization Code + client secret

Dispatchers on the server-rendered web portal

Run flow →
02Recommended

Driver Web App (SPA)

Authorization Code + PKCE (browser)

Drivers on a pure browser app, no backend secret

Run flow →
03Recommended

Driver Mobile (native)

Authorization Code + PKCE (public client)

iOS/Android driver app, simulated as a native public client

Run flow →
04Service

Rate Engine API

Client Credentials + client secret

Pricing service calling the internal Rates API

Run flow →
05Input-constrained

Dock Kiosk

Device Authorization Grant

Shared loading-dock screen with no keyboard

Run flow →
06Legacy – avoid

Legacy Yard Terminal

Resource Owner Password

Old green-screen terminal that can only POST a password

Run flow →
07Legacy – avoid

Old Customs Portal

Hybrid + Implicit (form_post)

Pre-2019 portal still using front-channel tokens

Run flow →
08Most secure M2M

Partner EDI Gateway

Client Credentials + private_key_jwt

Ocean-carrier partner, no shared secret on the wire

Run flow →
09Tool

Token Inspector

Local JWT validation vs. introspection

Any engineer debugging a token

Run flow →
10Federation

Payroll & HR (SAML)

SAML 2.0 SP-initiated SSO

HR system that only speaks SAML

Run flow →
11Session

Sign Out Everywhere

OIDC RP logout + SAML SLO

Shift ends: kill every session at once

Run flow →
12Adaptive

Hazmat Approval

Step-up with acr_values / max_age

High-risk action needs phishing-resistant MFA

Run flow →