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
@ctron where this requirement is coming from? I don't think this is a user friendly thing to do. We are doing 2 steps thing for the user to go back to the login page once he log out.
I believe this is the approach taken in v1 and I think it was not an ideal way of doing things.
Benefits of redirecting to the login page
Clarity: it is clear the user is no longer logged in and it provides an immediate way of login if needed.
Convenience: the login page is the ONLY page where the user can go after log out. We do not expect the user to navigate to any other page as all pages are protected.
User experience: it creates a clear end to end session and the message of "You are logged out" is 100% clear.
What is being requested:
My expectation would be:
That the user is logged out
That the user gets a confirmation that the logout was successful
Maybe gets a button/link to "log in again"
But does NOT get automatically forwarded to the login screen again
It forces the user to do unnecessarily 2 steps for going back to the login page:
First step: user click on "Log out". He is redirected to a page that has a button/link to "log in again" (as suggested in this issue)
Second step: the user clicks on "Log in again". And he is redirected to the Keycloak login page
Third step: user enters his username/password to be logged in again.
So:
What problem are we solving forcing the user to do a 2 steps process?
Exactly how the user benefits from using the 2 steps process suggested that he can not have with the current 1 step process that we have?
Steps to reproduce:
My expectation would be:
The text was updated successfully, but these errors were encountered: