Security Architecture
- Protocol Standard
- OAuth 2.1 + OIDC 1.0 with PKCE S256
- Token Storage
- Encrypted HTTP-only BFF cookies — never exposed to page scripts
- Step-Up Protection
- 5-minute recent authentication required for sensitive edits & exports
- Cookie Usage
- Strictly functional session & CSRF cookies — zero ad trackers
01
Zero-Exposure Single Sign-On
Every Cladik web application authenticates through Cladik SSO (auth.cladik.com) using authorization codes with Proof Key for Code Exchange (PKCE). Passwords are verified only on the central SSO server and are never stored in browser localStorage or forwarded to third-party apps.
- HTTP-Only Encrypted Sessions: session cookies carry HttpOnly, Secure, and SameSite protections at the Backend-for-Frontend layer.
- Cladik One-Tap & Silent OAuth Handoff: when signed in on auth.cladik.com, the browser-accounts endpoint returns only non-secret UI display hints for trusted Cladik apps. Selecting 'Continue as' still triggers a full server-verified OAuth 2.1 + PKCE authorization flow.
- Two-Step Verification & Recovery: add TOTP authenticator verification and recovery contacts to stop account takeovers.
