Project

General

Profile

Actions

Bug #21725

open

API token appears expired while it is not due to timezone

Added by François ARMAND over 1 year ago. Updated 18 days ago.

Status:
New
Priority:
N/A
Category:
API
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
103
Name check:
To do
Fix check:
To do
Regression:
No

Description

We have a problem with timezone and API token expiration date.
I'm not sure exactly what the problem is, but see the result in screenshot:

- expiration date set to 11h46
- this is translated to 11h46 UTC
- but in the machine, it's only 9h46 UTC (and on the screenshot, 10h29, I tried for some time to understand what was going on)

=> the calendar and "token expired!" message must be base on UTC time, too, not on local time (or based on local time but correctly take the offset into account).
=> if the date is UTC, we must have some info that it is so (it can be in the date format for ex).

Discovered in 7.2, but it is likely in previous version, too.

I'm setting it in critical/security, because a token marked as expired can actually be non expired.


Files

clipboard-202209071239-jagvb.png (167 KB) clipboard-202209071239-jagvb.png François ARMAND, 2022-09-07 12:39
Actions

Also available in: Atom PDF