Description
When users attempt to login with valid credentials, they occasionally receive a 'Session Expired' error immediately after authentication. This happens approximately 30% of the time and seems to be related to timezone differences between the server and client.
Steps to Reproduce
- Navigate to the login page
- Enter valid username and password
- Click 'Login'
- Observe that sometimes you get redirected back with 'Session Expired' error
Expected Behavior
Users should be successfully logged in and redirected to the dashboard.
Actual Behavior
Users receive a 'Session Expired' error and must try logging in multiple times.
Environment
- Browser: Chrome 120.0.6099.129
- OS: Ubuntu 22.04
- Server: Node.js 18.x
- Timezone: User in PST, Server in UTC
Additional Context
This started happening after the recent deployment last week. The issue is more frequent during business hours.
Possible Solution
It might be related to how we're calculating session tokens with timestamps. The timezone conversion might be causing tokens to be created with past expiration times.
Description
When users attempt to login with valid credentials, they occasionally receive a 'Session Expired' error immediately after authentication. This happens approximately 30% of the time and seems to be related to timezone differences between the server and client.
Steps to Reproduce
Expected Behavior
Users should be successfully logged in and redirected to the dashboard.
Actual Behavior
Users receive a 'Session Expired' error and must try logging in multiple times.
Environment
Additional Context
This started happening after the recent deployment last week. The issue is more frequent during business hours.
Possible Solution
It might be related to how we're calculating session tokens with timestamps. The timezone conversion might be causing tokens to be created with past expiration times.