Project

General

Profile

Actions

Bug #21725

open

API token appears expired while it is not due to timezone

Added by François ARMAND over 2 years ago. Updated 6 months 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

Related issues 1 (1 open0 closed)

Is duplicate of Rudder - Bug #25725: API account expiration timezone should be explicitNewActions
Actions #1

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.2.0 to 7.2.1
Actions #2

Updated by François ARMAND about 2 years ago

  • Assignee set to Elaad FURREEDAN
Actions #3

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.2.1 to 7.2.2
  • Priority changed from 124 to 123
Actions #4

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.2.2 to 7.1.8
  • Priority changed from 123 to 122
Actions #5

Updated by Elaad FURREEDAN about 2 years ago

  • Status changed from New to In progress
Actions #6

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.1.8 to 7.1.9
  • Priority changed from 122 to 121
Actions #7

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 7.1.9 to 7.1.10
  • Priority changed from 121 to 119
Actions #8

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 7.1.10 to 1016
  • Priority changed from 119 to 117
Actions #9

Updated by Alexis Mousset almost 2 years ago

  • Status changed from In progress to New
  • Priority changed from 117 to 114
Actions #10

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from 1016 to 7.2.5
Actions #11

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 7.2.5 to 7.2.6
  • Priority changed from 114 to 113
Actions #12

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.6 to 7.2.7
  • Priority changed from 113 to 111
Actions #13

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.7 to 7.2.8
  • Priority changed from 111 to 110
Actions #14

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.8 to 7.2.9
  • Priority changed from 110 to 107
Actions #15

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.9 to 7.2.10
  • Priority changed from 107 to 106
Actions #16

Updated by Alexis Mousset over 1 year ago

  • Target version changed from 7.2.10 to 7.2.11
  • Priority changed from 106 to 104
Actions #17

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 7.2.11 to 1046
  • Priority changed from 104 to 103
Actions #18

Updated by Alexis Mousset about 1 year ago

  • Target version changed from 1046 to 7.3.8
Actions #19

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.8 to 7.3.9
Actions #20

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.9 to 7.3.10
Actions #21

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 7.3.10 to 7.3.11
Actions #22

Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 7.3.11 to 7.3.12
Actions #23

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.12 to 7.3.13
Actions #24

Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 7.3.13 to 7.3.14
Actions #25

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 7.3.14 to 7.3.15
Actions #26

Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 7.3.15 to 7.3.16
Actions #27

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 7.3.16 to 7.3.17
Actions #28

Updated by Clark ANDRIANASOLO 2 months ago

  • Related to Bug #25725: API account expiration timezone should be explicit added
Actions #29

Updated by Clark ANDRIANASOLO 2 months ago

  • Related to deleted (Bug #25725: API account expiration timezone should be explicit)
Actions #30

Updated by Clark ANDRIANASOLO 2 months ago

  • Is duplicate of Bug #25725: API account expiration timezone should be explicit added
Actions

Also available in: Atom PDF