Add session support about passport-ldapauth HOT 4 CLOSED

Thanks, but no thanks. I'm pretty sure one shouldn't use Passport internal stuff, and I haven't seen any strategy do so (see eg. passport-local, one of the strategies implemented by the author of Passport.js).

Sessions are handled with session middleware, eg.

var express       = require('express'),
    session       = require('express-session'),
    cookieParser  = require('cookie-parser'),
    passport      = require('passport'),
    LdapStrategy  = require('passport-ldapauth').Strategy;

passport.serializeUser(function(user, cb) {
  cb(null, user.id);
});

passport.deserializeUser(function(id, cb) {
  yourDb.fetchDbCachedUser(id, cb);
});

passport.use(new LdapStrategy(opts, function(user, cb) {
  yourDb.storeUserToLocalDb(user, function(err, dbUser) {
    if (err) return cb(err);
    cb(null, dbUser);
  });
}));

var app = express();

app.use(express.cookieParser());
app.use(express.session({ secret: 'keyboard cat' }));
app.use(passport.initialize());
app.use(passport.session());

from passport-ldapauth.

hmmm, I'm using sessions but they are passing the deserialized user on to the ldapauth strategy, rather than successfully authing the user, I suppose I may still be holding it wrong.

from passport-ldapauth.

Or it could be designed to allow the ldap strategy to optionally verify the user is still valid?

from passport-ldapauth.

Just a quick question:

Instead of storing the user fetched from the LDAP into a local db and refetching this user in deserializeUser, is it good to directly fetch the user again in the deserializeUser?

from passport-ldapauth.