Bug #3460
Update token from cookie
| Status: | Assigned | Start date: | 03/19/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | Kostas Papadimitriou | % Done: | 0% |
|
| Category: | Cyclades UI | Spent time: | - | |
| Target version: | 0.13.1 |
Description
UI should always use the current cookie value whenever a token based action/request is invoked. This way cookie changes that are made in the current browser session (e.g. logout from another tab/window) will always be propagated on each ui app instance.
Associated revisions
UI. Always extract user info from current cookie contents
Refs #3460
Token value set in api action/request is always retrieved from the
current cookie contents. When cookie contents change is detected ui
redirects user to log in.
Cookie changes are detected each time the app tries to use the user
uuid/token information. A window interval (hardcoded to 10 seconds) was added
to access this information to ensure that cookie change logic will be
applied even when ui app gets idle (no api calls are made).
History
#1 Updated by Vangelis Koukis about 10 years ago
A suggestion in the same spirit:
The UI knows the UUID of the current user, from the token.
When a running UI detects a token change, it requests the associated UUID.
If it has changed, the token is for another user, a logout/login procedure has happened,
so the UI should refresh completely, to avoid the visual mix-up of information.