Course contentsShow
← Security
Lesson 1094 of 3,05222. Web Security - Client-Side and SPA SecurityFree lesson

Session Management in Stateless SPAs

Implementing proper logout, handling token expiration, and synchronizing authentication state across browser tabs.

Session Management in Stateless SPAs

You'll learn how to properly handle user sessions in single-page applications where tokens replace traditional server-side sessions.

The Challenge of Stateless Sessions

In traditional web apps, the server remembers who you are through session cookies. SPAs flip this model: they use stateless authentication with JWT tokens stored client-side. Think of it like holding your own access badge instead of the security desk keeping your ID—you're responsible for keeping it safe and knowing when it expires.

This creates three critical challenges: ensuring logout truly ends access, gracefully handling expired tokens, and keeping authentication state synchronized when users have multiple tabs open.

Proper Logout Implementation

Logout in SPAs must be multi-layered:

  • Delete tokens from storage (localStorage.removeItem('accessToken'))
  • Clear any in-memory state (Redux/Vuex/etc.)
  • Optionally call a backend logout endpoint to revoke refresh tokens
  • Redirect to login page

Without backend revocation, your token remains valid until expiration—like a key that still works even after you "returned" it.

Handling Token Expiration

Before making authenticated requests, check token expiration:

if (tokenIsExpired(accessToken)) {
  await refreshAccessToken(); // Use refresh token
}

Implement automatic refresh flows silently or prompt re-authentication when refresh tokens expire. Always handle 401 responses gracefully by clearing state and redirecting.

Cross-Tab Synchronization

Use the Storage Event API to detect authentication changes across tabs:

window.addEventListener('storage', (e) => {
  if (e.key === 'accessToken' && !e.newValue) {
    // Token removed in another tab - logout here too
    redirectToLogin();
  }
});

Or use BroadcastChannel for explicit cross-tab messages about login/logout events.

Key Takeaway: Stateless SPA sessions require explicit logout cleanup, proactive token expiration handling, and cross-tab synchronization to prevent security gaps that traditional session cookies handled automatically.