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
When a user, who authenticated using any other authentication mechanism except OAuth 2.0, clicks on "Logout" button, the user is actually logged out but it is never redirected back to the login page.
The reason is because the logout logic is calling the function go_to_home which is not defined.
Maybe this issue goes unnoticed because the majority of users opt for the default refresh value of "Refresh every 5 seconds". After 5 seconds, the login page is loaded. But if the user chose the option "Do not refresh" then the user is not redirected back to the login page until it clicks on any part of the management ui or refreshes the page.
This has been reproduced in RabbitMQ 3.13.2.
Note: It was a change not back-ported from 3.11.
Reproduction steps
login using username+password
2.click on logout
3.the user stays in the management ui. Only when the user refreshes the page, the new loaded page is the login page.
...
Expected behavior
when the user clicks on logout, the user's authentication state is cleared and is redirected back to the login page.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
When a user, who authenticated using any other authentication mechanism except OAuth 2.0, clicks on "Logout" button, the user is actually logged out but it is never redirected back to the login page.
The reason is because the logout logic is calling the function
go_to_home
which is not defined.Maybe this issue goes unnoticed because the majority of users opt for the default refresh value of "Refresh every 5 seconds". After 5 seconds, the login page is loaded. But if the user chose the option "Do not refresh" then the user is not redirected back to the login page until it clicks on any part of the management ui or refreshes the page.
This has been reproduced in RabbitMQ 3.13.2.
Note: It was a change not back-ported from 3.11.
Reproduction steps
2.click on logout
3.the user stays in the management ui. Only when the user refreshes the page, the new loaded page is the login page.
...
Expected behavior
when the user clicks on logout, the user's authentication state is cleared and is redirected back to the login page.
Additional context
No response
The text was updated successfully, but these errors were encountered: