Not able to override current connect.sid with samesite: none without losing session

currently, I have connect.sid with no samesite value, want to override it with samesite as none without losing the session.

let cookieObj = {
    maxAge: 180000,
    expires: new Date(new Date().getTime()+180000),
    secure: true
}

app.use(session({
    cookie: cookieObj,
    secret: 'abcdefght',
    resave: true,
    rolling: true,
    saveUninitialized: true,
    store: new redisStore({client: client}) // redis client
}));

this is my current session manager, in cookieObj i have added samesite now,

let cookieObj = {
    maxAge: 180000,
    expires: new Date(new Date().getTime()+180000),
    secure: true,
    sameSite: "none"
}

this is not updating the current cookie, for new sessions it is working properly. I tried updating cookie by res.cookie() new object from * route, its updating the cookie but after redirecting from payment page session is getting remove.

Help me to update the current cookie without losing session

[dougwilson]

The unfortunate part is that it is too late to fix your existing sessions, AFAIK. Because all those cookies that were from before users who upgraded to Chrome 80 won’t have the change, and so Chrome will not send them back to the server here for this module to even “fix” them after the fact… if Chrome does not send the cookie, this module doesn’t know the session ID in order to provide an updated cookie.

[ghinks]

I have looked into how the chrome 80 change would impact you

For pre-existing users that default to the sameSite lax it looks like the cookie will not be sent to your third party. This would result in the symptoms you describe. This is not a common change you are encountering and I do not expect you to have to do so again. Alas it does look like the sameSite setting will remain unset until a new cookie is dropped and you loose session.