Passport.Js not able to get session from client for some browsers - works perfectly on localhost but not when deployed

user_14489427 0
Viewed 267

Heyyo, this issue is driving me nuts.

I have an issue where Passport.Js seems to not be getting a user session sent back from the user. Everything else seems to work fine, and there is no problem serializing or deserializing the user.

When deployed, it seems to work fine on Firefox, but not on Chrome. It works on Chrome when I am testing on my local machine using http://localhost:PORT, but just not when deployed.

Because it works fine on my local machine, I was wondering if it might be an https/http issue?

Does anyone have any idea what the issue could be? Thank you.

Middleware:

app.use(cookieParser());
app.use(expressSession({ 
  resave: true,
  saveUninitialized: true,
  secret: process.env.REACT_APP_SESSION_SECRET,
}))
app.use(passport.initialize());
app.use(passport.session())
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(cors({
  origin: "https://example.url",
  methods: "GET,HEAD,PUT,PATCH,POST,DELETE",
  credentials: true,
}));
app.use(express.static('public'));

Example of request to server:

fetch(`https:example.url/sync/`, { credentials: 'include'})
    .then({ // ... })

Thanks in advance.

passport.js express session cookies javascript
1 Answers

After hours spent figuring out an answer, I've found out what the issue is. Posting so that others may see.

Firstly, there was definitely an http/https issue. I had to implement the following middleware in my Express server to ensure that my requests to google auth were being sent securely via https.

app.enable('trust proxy')

Secondly, Chrome browser had set a cookie but was not sending it back to the server because of missing security settings for the cookies. This was required as of February 2020. The following options resolved this issue:

app.use(expressSession({

  // .. other settings ..

  cookie: {
    sameSite: 'none',
    secure: true
  }
}))

The requirement is outlined here: https://blog.chromium.org/2019/10/developers-get-ready-for-new.html

Hope this helps anyone stuck on this problem.

user_144894270
Related