Accessing a single Express app can result in the session being terminated in another app on the same server

Question

Accessing a single Express app can result in the session being terminated in another app on the same server

On a single server machine, I have two Express 4.x applications running on different ports but sharing the same MongoDB instance. Each app uses its own database and session secret.

When logging into either application A or B individually, everything works fine - the session is maintained without any issues. However, if I am logged into A and then try to log into B, my session in A gets destroyed (and vice versa).

Both applications have similar local authentication setups with simple serializeUser and deserializeUser functions that closely follow the Passport documentation.

It appears that when switching from logging into A to B, the req.session.passport data is somehow being lost, causing req.user not to serialize correctly in app A, leading to an invalid session.

I suspect that this issue might be related to both apps running on the same machine and domain, only differing by the port number.

node.js session express passport.js connect-mongo

Answer 1

Answer №1

express-session: A straightforward session middleware designed for Express in Node.js. To incorporate this functionality, the package must be included as follows:

var session = require('express-session');

To add this package, execute the following command:

$ npm install express-session

If you want to implement this in Express, refer to the code snippet below:

app.use(session({
  secret: 'secretkey',
  resave: false,
  saveUninitialized: true,
  cookie: { secure: true }
}));

The default name of the session ID cookie set in the response (and accessed from the request) is connect.sid. If you wish to change this, use the following configuration:

app.use(session({
  name: 'cookiename',
  secret: 'secretkey',
  resave: false,
  saveUninitialized: true,
  cookie: { secure: true }
}));

For additional information, please visit this link - https://www.npmjs.com/package/express-session

Note: Insert your express-session statement into your application's app.js file before the app.use(passport.session()) statement.

We trust this guidance will aid in resolving your query!

Answer 2

express-session: A straightforward session middleware designed for Express in Node.js. To incorporate this functionality, the package must be included as follows:

var session = require('express-session');

To add this package, execute the following command:

$ npm install express-session

If you want to implement this in Express, refer to the code snippet below:

app.use(session({
  secret: 'secretkey',
  resave: false,
  saveUninitialized: true,
  cookie: { secure: true }
}));

The default name of the session ID cookie set in the response (and accessed from the request) is connect.sid. If you wish to change this, use the following configuration:

app.use(session({
  name: 'cookiename',
  secret: 'secretkey',
  resave: false,
  saveUninitialized: true,
  cookie: { secure: true }
}));

For additional information, please visit this link - https://www.npmjs.com/package/express-session

Note: Insert your express-session statement into your application's app.js file before the app.use(passport.session()) statement.

We trust this guidance will aid in resolving your query!

Answer 3

Answer №2

const mongoose   = require('mongoose'),
    timestamps = require('mongoose-timestamp');

var Schema = mongoose.Schema;
const Usersession = new mongoose.Schema({
    expiration : {
        type : String,
        default : ""
    },
    sessionData : {
        type : Schema.Types.Mixed,
        default : {}
    }
}, { collection: 'usersessions' })

Usersession.plugin(timestamps)

module.exports =  mongoose.model('usersessions', Usersession);

//require schema
const Usersession = require('usersessions');

//delete user session by id
Usersession.remove({"sessionData.user._id":user._id}
).exec(console.log)

Answer 4

const mongoose   = require('mongoose'),
    timestamps = require('mongoose-timestamp');

var Schema = mongoose.Schema;
const Usersession = new mongoose.Schema({
    expiration : {
        type : String,
        default : ""
    },
    sessionData : {
        type : Schema.Types.Mixed,
        default : {}
    }
}, { collection: 'usersessions' })

Usersession.plugin(timestamps)

module.exports =  mongoose.model('usersessions', Usersession);

//require schema
const Usersession = require('usersessions');

//delete user session by id
Usersession.remove({"sessionData.user._id":user._id}
).exec(console.log)

Answer 5

Answer №3

It's important to specify distinct session names for each project when running on different ports. The default name is connect.sid for all projects.

For instance:- Project A on port 3000 -
Project B on port 5000 -

When these projects are simultaneously run, they will use the same session name by default, resulting in authentication clashes. Therefore, it's crucial to assign different session names to each project.

Answer 6

It's important to specify distinct session names for each project when running on different ports. The default name is connect.sid for all projects.

For instance:- Project A on port 3000 -
Project B on port 5000 -

When these projects are simultaneously run, they will use the same session name by default, resulting in authentication clashes. Therefore, it's crucial to assign different session names to each project.

Accessing a single Express app can result in the session being terminated in another app on the same server

Answer №1

Answer №2

Answer №3

Similar questions

Guide on obtaining Loopback 3 conditional 'datasources' and 'model-config': adhering to the provided steps does not yield results

How can you transform a nested array into a flat JavaScript map?

Node cannot be updated because npm is not compatible with Node.js version 5.3.0

An API request was successfully completed with security measures in place; if not

Adding an image to a PDF file using NodeJS and Pdfmake

Create a Mongoose model that includes a field containing an array of ObjectID's

Commitments and incorporating items from an array into objects nested within a separate array

Is Exposing Database Passwords on Github a Potential Security Concern?

Combining Summernote images with Node.js using Express.js

When a node using express encounters :id, it is directed to a specific location

Guide to ordering objects within an array by their createdAt property in mongoose

Update Mongoose data conditionally using an array of objects

The internal cjs loader in node threw an error at line 1078

sharing functions across distinct components in react without directly passing between parent and child

Evaluating server functionality within Koa framework

Unable to locate "Gruntfile.js" Node module for task execution

Retrieve information from various MongoDB collections

Executing MySQL queries synchronously in Node.js

Validating forms in express.js

Transferring data from URL straight to S3 in Lambda with an excessive memory consumption