Securing Express Apps with Passport Local Strategy: A Practical Walk‑through
Learn how to wire Passport’s LocalStrategy with bcrypt, express‑session, and route guards to build a minimal, production‑ready username/password login flow.
Loading…
ReadMeFeed / Community knowledge
#express-js
Real questions. Useful conversations. Find the people who know your stack.
passportManaging Cross‑Cutting Concerns with Express Middleware
Stop duplicating authentication and validation logic in your Express routes. Learn how to implement custom middleware to handle cross‑cutting concerns and keep your handlers lean.
express
nodejsManaging Request Flow with Express Middleware
Stop the 'hanging request' problem in Express.js. Learn how to implement global and route-level middleware, handle errors correctly, and pass data through the request pipeline.
Decoupling Auth Logic with Passport.js Strategies
Stop embedding authentication logic in your routes. Learn how Passport.js uses the Strategy pattern to decouple credential verification from application routing for scalable auth.
Decoupling Auth Logic with Passport.js Serialization
Learn how Passport.js uses the strategy pattern and session serialization to decouple authentication methods from session storage, reducing route bloat and improving maintainability.
Managing Express Error Middleware: Arity and Order
Express identifies error handlers by function arity (4 arguments) and executes them in registration order. Learn how to structure your middleware stack and handle async errors.
Architecting Credential-Based Auth with Passport.js Local Strategy
Learn how to implement a decoupled authentication architecture using Passport.js Local Strategy, focusing on the separation of credential verification and session persistence.
Passport.js local and JWT strategies: verify callback argument consistency
The goal is to clarify whether the verify callback supplied to a Passport.js strategy must always receive three arguments (err, user, info) or may receive only two arguments (err, user) when the strategy does not generate an info object. Current Passport documentation leaves this behavior unspecified, and individual strategies such as passport-local and pass