1. The Fragility of Centralized Monoliths
In distributed web architectures, maintaining session security across independent applications on distinct ports (e.g. apps/web on 3000, apps/dashboard on 3001, apps/taskm on 3002, apps/accounts on 3003, and apps/promptlab on 3004) introduces complex security considerations.
Legacy implementations often resort to insecure localStorage tokens or shared global cookies vulnerable to cross-site scripting and unauthorized telemetry extraction.
2. The Dual-Token Isolation Architecture
Wustenroze engineers an enterprise zero-trust model across its entire micro-frontend topology. Short-lived Access Tokens (15 minutes) remain strictly in memory, while secure 7-day Refresh Tokens reside in HttpOnly cookies set by our NestJS backend.
Edge middlewares across all micro-apps guard route boundaries silently. If a user attempts to access deep workspace URLs without authentication, they are redirected to our centralized Accounts gateway, returning seamlessly upon verification.
Multi-tab synchronization is achieved via native browser BroadcastChannel events (LOGIN_SUCCESS, LOGOUT, SESSION_EXPIRED), guaranteeing instant session coherence across every active viewport.
3. Absolute Privacy by Design
Your tasks, AI prompts, and architectural models remain encrypted and unmonitored. We maintain zero telemetry pipelines over user output.