The authentication middleware deletes the data that were inside the session before authentication, verssion 0.6.0 about passport HOT 3 CLOSED

I've done some debugging with breakpoints on the internal code, comparing the sessions both from my own implemented functions and the strategy success complete function located internally in lib/middleware/authenticate.js, and I can see that upon logging in, it is generating a completely different session object.

I've tested this using:

• express version 4.18.2
• express-session version 1.17.3
• memorystore version 1.6.7
• passport version 0.6.0
• passport-local version 1.0.0
  Windows 10 OS, Node.JS V16.3.0, NPM V9.4.0

Changing the value of the session option saveUninitialized does not make any difference to this issue

from passport.

The solution is to pass the option keepSessionInfo: true to the authenticate method.

from passport.

Same problem- was able to workaround it with the following

router.get('/auth/google/callback',
  async (req, res, next) => {
    const redirectUrl: string = (req.session as any).afterLogin;
    await passport.authenticate('google', {})(req, res, next);
    res.redirect(redirectUrl);
    next();
  });

from passport.