ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Architecture guide for integrating Passport.js Local Strategy into a Node.js REST API, covering requirements, minimal design, trust boundaries, failure checks, and when to reconsider the approach.
Architecture note on the minimal Passport.js design for first-party login: passport-local strategy with express-session backed by Redis, covering trust boundaries, operational checks, failure modes, and when to switch to token-based auth.
Learn how to separate authentication from session persistence using Passport.js and the Local Strategy to build secure, scalable Node.js user sessions.
Shows how to configure Passport.js with the Local strategy, keep session data minimal, define trust boundaries, and add operational checks for secure Node.js authentication.
Learn what serializeUser and deserializeUser do, see a working local‑strategy example, and understand why you might keep them when switching to a stateless JWT approach.
Session Termination Behavior Updating a Node.js application to Passport.js version 0.6.0 introduces a breaking change to the req.logout() method. In previous versions, this method operated synchronously, allowing developers to call it without a callback function before redirecting the user. Starting with version 0.6.0, req.logout() is asynchronous and requir
I'm designing authentication for an Express app that will run behind a load balancer configured with sticky sessions (cookie-based affinity). Passport supports both approaches I'm weighing: the classic serializeUser / deserializeUser hooks backed by express-session , and the passport-jwt strategy with session: false so no server-side state is kept at all. My
nodejs
passport