Security
Security decisions happen on the server.
ToastyHub is designed to minimize browser exposure. Frontend code renders data and submits requests, but
session validation, authorization, claim mapping, provider credentials, and data access checks remain in
backend functions only.
Session-first auth
Authorization Code Flow with PKCE, HttpOnly cookies, CSRF validation, and session rotation controls.
Minimal claims
Only the required claims from Authentik are mapped locally: subject, email, display name, and groups.
Least data exposure
Provider tokens stay backend-only, and the dashboard receives sanitized summaries instead of raw API payloads.