06-authentication-flow

Manage SPA authentication state across reloads by scaffolding an auth repository and a global session store with unknown, authenticated, and guest states. Implement a centralized startup hydration routine to restore the session lifecycle on boot.

Centralize frontend session management by implementing a unified 401 handling path and a single logout routine reused by route guards and error handlers. This prevents scattered logout logic across your SPA or hybrid app.

Structure an auth repository for login and logout flows by defining login, logout, me, and refresh methods. Bind this repository to a global session store to orchestrate state transitions without leaking provider wiring into UI layers.

You can apply this session management approach across frameworks by maintaining strict boundary separation. Keep provider wiring and route protection in distinct modules to maximize portability for protected dashboards and startup hydration.

Hydrate an authenticated session on SPA startup by running a centralized initialization routine that calls the auth repository's me method. This updates the global session store from an unknown state to authenticated or guest before rendering.

Separate session state from route protection logic to maintain architectural boundaries and maximize portability. Keeping route protection distinct prevents leaking authentication provider wiring directly into your UI and navigation layers.