You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user still looks logged in when a log out has been performed in another tab. Even if it's not possible to get data for protected resources, the UX is very confusing because the user believes to still be logged in.
An especially confusing case is the interactive environment page because the anonymous login is triggered on a 404 response from /servers, showing the content of an anonymous user in a page for logged user.
E.G. on a public project, a user may have launched a few environments. On log out, those disappear but the anonymous login is triggered, therefore the API succed and the following responses are valid. The user thinks the environments were closed but in fact he is now interacting as an anonymous user and the previous environments are still running but non accessible until the login.
Furthermore, if the user try to start new environments, he won't be able to push to the repository since the proper autentication tokens are missing.
Description
The user still looks logged in when a log out has been performed in another tab. Even if it's not possible to get data for protected resources, the UX is very confusing because the user believes to still be logged in.
An especially confusing case is the interactive environment page because the anonymous login is triggered on a 404 response from
/servers
, showing the content of an anonymous user in a page for logged user.E.G. on a public project, a user may have launched a few environments. On log out, those disappear but the anonymous login is triggered, therefore the API succed and the following responses are valid. The user thinks the environments were closed but in fact he is now interacting as an anonymous user and the previous environments are still running but non accessible until the login.
Furthermore, if the user try to start new environments, he won't be able to push to the repository since the proper autentication tokens are missing.
Reproduce
The text was updated successfully, but these errors were encountered: