Project

General

Profile

Actions

Bug #39300

closed

Bug #39294: mgr/dashboard: Time handling

mgr/dashboard: Can't login with a bigger time difference between user and server or make auth token work with UTC times only

Added by Stephan Müller about 5 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
General
Target version:
% Done:

0%

Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
2 - major
Reviewed:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

With the time difference of -7h to the backend, I couldn't log in. The log throw the error `AMT: user info changed after token was issued, iat=%s lastUpdate=%s` which can be found in line 150 in `dashboard/services/auth.py`. I removed as a quick fix line 146 in the same document which said that `user.lastUpdate <= token['iat']` has to be true in order to login.


Related issues 3 (0 open3 closed)

Related to Dashboard - Bug #38600: mgr/dashboard: dashboard giving 401 unauthorized.Duplicate

Actions
Related to Dashboard - Bug #38428: mgr/dashboard: dashboard giving 401 unauthorizedResolved

Actions
Copied to Dashboard - Backport #39524: nautilus: mgr/dashboard: Can't login with a bigger time difference between user and server or make auth token work with UTC times onlyResolvedLenz GrimmerActions
Actions

Also available in: Atom PDF