To me it’s unnecessary. It’s not saving me any work. I have to write the configuration, the callback, and the user schema. To me, it’s just easier for me to just write a middleware for that. And I don’t see there is any security enforcement I am getting cuz I am writing my own verify … Read more
For anyone else who is having this issue, take a look at this: app.use(session({ secret: ‘something’, cookie: { secure: true }})); If you have cookie.secure set to true and you’re NOT using SSL (i.e. https protocol) then the cookie with the session id is not returned to the browser and everything fails silently. Removing this … Read more
Is the user now in a session on my server? No, You need to use the express-session middleware before app.use(passport.session()); to actually store the session in memory/database. This middleware is responsible for setting cookies to browsers and converts the cookies sent by browsers into req.session object. PassportJS only uses that object to further deserialize the … Read more
You can name your local strategies to separate them. // use two LocalStrategies, registered under user and sponsor names // add other strategies for more authentication flexibility passport.use(‘user-local’, new LocalStrategy({ usernameField: ’email’, passwordField: ‘password’ // this is the virtual field on the model }, function(email, password, done) { User.findOne({ email: email }, function(err, user) { … Read more
User.findOrCreate is a made-up function that represents whatever function you have to find a user by Facebook ID, or to create one if the user doesn’t exist. I think your first problem is that your callback URL is just going to your root, so you probably are never getting to that function. Your callback URL … Read more
I recently came across this problem and it can be caused by a number of things. First thing to check is ensuring that the bodyParser is set up for express, which I see that you have done. app.use(express.bodyParser()); The next thing is ensuring that the form you are submitting to the route contains both a … Read more
I do this exact thing using async/await in my games code here Assuming req.isLoggedIn() returns a boolean, it’s as simple as: const isLoggedIn = await req.isLoggedIn(); if (isLoggedIn) { // do login stuff } Or shorthand it to: if (await req.isLoggedIn()) { // do stuff } Make sure you have that inside an async function … Read more
Make sure these two things are in your code: passport.use(new FacebookStrategy({ clientID: ‘CLIENT_ID’, clientSecret: ‘CLIENT_SECRET’, callbackURL: “http://www.example.com/auth/facebook/callback” passReqToCallback : true, profileFields: [‘id’, ’emails’, ‘name’] //This }, and this: app.get(‘/connect/facebook’, passport.authorize(‘facebook’, { scope : [’email’] })); This gives you access to the following: profile.id profile.name.givenName profile.name.familyName profile.emails The last one being an array, so use profile.emails[0].value … Read more
I had a similar issue. Could be due to the express-session middleware needed for passport. Fixed it by using middlewares in the following order: (Express 4) var session = require(‘express-session’); // required for passport session app.use(session({ secret: ‘secrettexthere’, saveUninitialized: true, resave: true, // using store session on MongoDB using express-session + connect store: new MongoStore({ … Read more
Here is a solution using Socket.IO 1.0 and Express 4.0. It is similar in spirit to Patrick’s answer. The trick is that since Socket.IO 1.0 has a new middleware API, we can wrap Express’s middleware and put it into the Socket.IO pipeline without delving into the low-level implementation of the session stores. // Set up … Read more