New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
express-session deprecated req.secret; provide secret option
: after adding connect-mongo
and configuring its receiver
#6810
Comments
@navicstein Thanks for posting! We'll take a look as soon as possible. In the mean time, there are a few ways you can help speed things along:
Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly. For help with questions about Sails, click here. |
Hey, @navicstein! Can you reproduce this error in a fresh Sails app and share the repo? Thanks! |
@MadisonHicks i have successfully reproduced #6810 it's at please i used pnpm as my package manager, but am pretty sure its not from it. |
Hello, i have resolved this issue by installing a lower version of connect-mongo pnpm install connect-mongo@2.0.3 --save-exact An after those, depreciation notice was gone, seems like the sails team @MadisonHicks @johnabrams7 @tedkulp @sailsbot needs to update sails to support |
Any solution for newer version of |
I have the same issues when using connect-mongo 3.2.0. Following it through on the debugger, it looks like its because connect-mongo deletes the |
I am reproducing this error, but I dont have any particular configuration with mongo-connect, in fact this is my package.json and my express config:
express:
|
I'm reproducing the error code. Please fix this, Team Sails. We are hoping to get it resolved ASAP.
I'm using Sails.js v.1.2.4 Thanks, |
I think this should be opened back. The issue is not solved. It is caused by a change in connect-mongo is deleting the session.secret variable from the object, thus, when creating the instance of app.config.session.store = new CustomStore(app.config.session); the app.config.session.secret no longer exists. So, when Options here:
|
I had a similar issue and my problem was I was missing the .env file. |
… 3.x.x breaks the sails expected configuration, see: balderdashy/sails#6810 (comment)
Hi sailors, any workaround besides downgrading connect-mongo??? |
Node version:
Sails version (sails): 1.2.3
ORM hook version (sails-hook-orm): 2.1.1
Sockets hook version (sails-hook-sockets): 2.0.0
Organics hook version (sails-hook-organics): 1.0.0
Grunt hook version (sails-hook-grunt): nil
Uploads hook version (sails-hook-uploads): 0.4.3
DB adapter & version (e.g. sails-mysql@5.55.5): 1.0.1
Skipper adapter & version (e.g. skipper-s3@5.55.5): nil
Hello, when i installed a fresh app, i encountered an error while trying to plug in the
sessions
adapter into it's receiverThe receivers config is as follows:
Error @sailsConsole
but then an error occurred while trying to render the page /
The text was updated successfully, but these errors were encountered: