Adding Username/Password Login to an Express App with Passport.js Local Strategy
Step‑by‑step guide to add username/password login with Passport.js local strategy, session handling, and route protection in a Node.js Express app.
Loading…
ReadMeFeed / Community knowledge
#passportjs
Real questions. Useful conversations. Find the people who know your stack.
expressPassport Session Serialization: How serializeUser and deserializeUser Keep Users Authenticated
Passport's serializeUser and deserializeUser bridge the gap between login and subsequent requests. Here is how they work, a minimal example, and the trade-offs.
nodejsPassport.js Local Strategy: Why serializeUser and deserializeUser Matter for Session State
Learn how Passport.js splits user data between the session cookie and your data store, and how to tune this trade‑off for scalability and security.
Passport.js Local Strategy with Server-Side Sessions: An Architecture Note
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.
Using Passport.js LocalStrategy with Custom Form Fields in Express
Learn how to configure Passport.js LocalStrategy to work with custom login field names while keeping authentication secure.
Passport.js serializeUser/deserializeUser lacks built‑in schema‑version guard
Goal Define a reliable strategy to keep existing sessions valid or safely invalidate them when the user model changes (fields added, removed, or renamed). Constraints Passport.js stores only what serializeUser returns; deserializeUser receives that opaque payload on every request. No core hook exists to attach a schema version, run a migration, or automatica
passportUnresolved strategy choice for Passport.js unit tests without live credentials?
Goal Test a Passport.js authentication flow in a local test environment while avoiding any calls to external OAuth providers. The test must simulate the provider’s token exchange, user profile retrieval, and session handling without using real production credentials. Constraints To keep the tests deterministic, the OAuth endpoints must be intercepted (e.g.,
Passport.js session serialization: configuring serializeUser to store minimal user identifier
Goal: Configure Passport.js's serializeUser callback so that the session store holds only the essential identifier needed to reconstruct the user object, thereby reducing memory usage and I/O latency in high‑traffic Node.js applications. Uncertainty: It is unclear what minimal payload serializeUser should return (e.g., just the user ID, a signed token, or a