I figured it out! First of all you need to implement the correct strategy. In my case LocalStrategy, and you need to provide your validation logic. For example sake let’s use the one in passport-local. var passport = require(‘passport’) , LocalStrategy = require(‘passport-local’).Strategy; passport.use(new LocalStrategy( function(username, password, done) { User.findOne({ username: username }, function(err, user) … Read more
That particular error occurs whenever you try to send more than one response to the same request and is usually caused by improper asynchronous code. The code you show in your question does not appear like it would cause that error, but I do see code in a different route here that would cause that … Read more
There’s a passReqToCallback option that you can enable, like so: passport.use(new LocalStrategy( {usernameField: ’email’, passReqToCallback: true}, function(req, email, password, done) { // now you can check req.body.foo } )); When, set req becomes the first argument to the verify callback, and you can inspect it as you wish.
In your ensureAuthenticated method save the return url in the session like this: … req.session.returnTo = req.originalUrl; res.redirect(‘/login’); … Then you can update your passport.authenticate route to something like: app.get(‘/auth/google/return’, passport.authenticate(‘google’), function(req, res) { res.redirect(req.session.returnTo || “https://stackoverflow.com/”); delete req.session.returnTo; });
If user is logged in, passport.js will create user object in req for every request in express.js, which you can check for existence in any middleware: if (req.user) { // logged in } else { // not logged in } You can create simple express.js middleware for that, that will check if user is logged … Read more
Follow the example to avoid the out-of-order middleware hell that express makes it so easy to enter. Straight from the docs. Note how yours does not match this exactly. var app = express(); app.use(require(‘serve-static’)(__dirname + ‘/../../public’)); app.use(require(‘cookie-parser’)()); app.use(require(‘body-parser’).urlencoded({ extended: true })); app.use(require(‘express-session’)({ secret: ‘keyboard cat’, resave: true, saveUninitialized: true })); app.use(passport.initialize()); app.use(passport.session()); Docs cookieParser session … Read more
Chiming in with my two cents, as the developer of Passport. Before developing Passport, I evaluated everyauth and determined that it didn’t meet my requirements. So, I set about implementing a different solution which would. The major points I wanted to address are: Idiomatic Node.js everyauth makes extensive use of promises, instead of Node’s approach … Read more
passport.session() acts as a middleware to alter the req object and change the ‘user’ value that is currently the session id (from the client cookie) into the true deserialized user object. Whilst the other answers make some good points I thought that some more specific detail could be provided. app.use(passport.session()); is equivalent to app.use(passport.authenticate(‘session’)); Where … Read more
There are many questions asked here, and it seems that even though the questions are asked in the context of Node and passport.js the real questions are more about workflow than how to do this with a particular technology. Let’s use @Keith example setup, modified a bit for added security: Web server at https://example.com serves … Read more
It looks like you didn’t implement passport.serializeUser and passport.deserializeUser. Try adding this: passport.serializeUser(function(user, done) { done(null, user); }); passport.deserializeUser(function(user, done) { done(null, user); });