Calling GET /api/v2/token results in already expired token #1739
Unanswered
KMConnectTeam
asked this question in
Q&A
Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
thanks Sir ! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello the title says it all, but i want to provide additional information about the setup.
Setup is as follows:
When i call GET /api/v2/token, then i get an already expired token. More detailed: i live in Germany its CEST 15:34 but the token has expire date of 2024-08-30T13:54:58Z
I checked Docker container time, time of Postgresql in postgresql.conf. And no matter where i do changes the result is always the same.
I think the token is created to be valid for 20 minutes. For some reason it uses GMT (which is 2 hours behind). Then it can be calculated as follows: CEST 15:34 - 2 hours + 20 min = 13:54
Has anybody an idea ? Or am i the only one who faced this problem ?
Beta Was this translation helpful? Give feedback.
All reactions