Bug #39300
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
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
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
History
#1 Updated by Ricardo Dias almost 5 years ago
- Assignee set to Ricardo Dias
#2 Updated by Ricardo Dias almost 5 years ago
- Pull request ID set to 27604
#3 Updated by Lenz Grimmer almost 5 years ago
- Status changed from New to Fix Under Review
- Target version set to v15.0.0
- Backport set to nautilus
- Affected Versions v14.0.0, v14.2.0, v14.2.1 added
#4 Updated by Lenz Grimmer almost 5 years ago
- Related to Bug #38600: mgr/dashboard: dashboard giving 401 unauthorized. added
#5 Updated by Lenz Grimmer almost 5 years ago
- Related to Bug #38428: mgr/dashboard: dashboard giving 401 unauthorized added
#6 Updated by Lenz Grimmer almost 5 years ago
- Status changed from Fix Under Review to Pending Backport
#7 Updated by Nathan Cutler almost 5 years ago
- Copied to 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 only added
#8 Updated by Lenz Grimmer almost 5 years ago
- Status changed from Pending Backport to Resolved