Problem using with passport 0.6.0: session.regenerate is not a function

[showaltb]

Problem using with passport 0.6.0: session.regenerate is not a function

[dougwilson]

Cool. I don't want to close this for now as just want to see what is decided around. I forgot to mention as well that adding, even a dummy method, would end up as semver major, as it would now prevent the usage of the key regenerate in the user-set data. And it's a hard thing to work around with a client side store model like this, because you cannot just update the key in your db; the clients have the data blob :(

[dougwilson]

Hi @showaltb sorry about that! I took a look and it appears regenerate is meant to generate a new session ID for a session. But this module stores the session in the cookie directly, no session ID. I'm not sure what a regenerate would actually do if added to this module, though. Also adding something to req.session would be a backwards incompatible change, as right now someone could be storing data in that key.

[Ylianst]

Arg. Passport now assumes that a session has regenerate() and save() methods (see here). As a result, Password now throws an exception when used with cookie-session, (see here).

Would be great if dummy versions of these methods where implemented.

[dougwilson]

Yea, I thought about that too, but it seems like dummy methods would be misleading and then not actually perform what is intended. It likely makes more sense if, for example, Passport wants to use other modules that express-session, then it should probably have some sort of adapter so you can say what kind of session module you are using and it can use the appropriate APIs for that module.

[dougwilson]

It also would mean that if dummy regenerate method was added, then there would no longer be a way for something like passport to detect that the session is not capable of regenerating the session id.

[Ylianst]

Ok, filed with with Password: jaredhanson/passport#904

[dougwilson]

Ok, so I'm going to close this issue has it has been sitting here for a few months. I looked over the linked Passport.js issue and it seems the question was answered in jaredhanson/passport#904 (comment)

The author of Passport.js seems pretty clear that cookie-session was never a supported session to use, which makes sense why no issue was ever noticed in the Passport.js change before it was released. The author outlined their thoughts there about how to add cookie-session as a supported session system to Passport.js as well. I'm not sure if they have made any progress towards it, but if not, I'm sure they would be willing to accept someone who did contribute such a change to Passport.js.