MEAN.io Session Cookie parameters
Known for his open source and JavaScript security initiatives, Liran Tal is an award-winning software developer, security researcher, and open source champion in the JavaScript community. He's an internationally recognized GitHub Star, acknowledged for his open source advocacy, and has received the OpenJS Foundation's Pathfinder for Security for his work on Node.js security. His contributions to developer security education include leading OWASP projects, building supply chain security tools, participation in CNCF and OpenSSF initiatives, and authoring books such as O'Reilly's Serverless Security. He leads the developer advocacy team at Snyk.io and is on a mission to empower developers with better application security skills.
Jun 13, 2014 ~ 1 min read
MEAN.io Session Cookie parameters
share this story on
Continuing with my contribution to the MEAN.io (MongoDB, ExpressJS, AngularJS, and NodeJS) technology stack (or should we say framework by now with the progress it’s been making?) I’ve submitted another pull request to allow setting up MEAN.io session cookie parameters. It is often required for enterprise applications to set session cookie parameters and not rely on Express’s defaults. These parameters are for example the cookie expiration time, and whether the session cookie will require the website to run in an SSL-enabled environment.
This PR adds support for default parameters on the cookie session and allows developers to set them as required globally, or per environment (development, testing, and production). Description on the session cookie parameters themselves have been added as well to make this easy to configure.
