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

I’ve been using cookie-session in conjunction with passport successfully. But passport-0.6.0 now calls session.regenerate(), which is part of the API for express-session, but not for cookie-session.

I’m not sure exactly how all this works together, but should regenerate() be added to cookie-session or should passport be checking for existence before attempting to use it?

[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]

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 https://github.com/jaredhanson/passport/issues/904#issuecomment-1135119308

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.