I agree it should either show a page is no longer valid message or redirect
back to origin as you're suggesting. The latter is the best, but we need to
be able to identify that's actually what should be done. I tried with
Google and it actually didn't work for me, it showed me the password page
again.
On 7 April 2016 at 13:47, Libor Krzyzanek <lkrzyzan(a)redhat.com> wrote:
Hi,
when user successfully logs in (either after registration or login) then
hitting back button shows KC page (login/registration) again.
This looks to be a bug to me because user is logged in and should be
allowed to do only logout. No login or registration.
I tried how
google.com behaves and when you successfully logs in then
hitting back button is handled correctly - their sso realize that you’re
logged in and then user is redirected to requested page. No login page.
I think KC should follow same behavior.
Jira for login flow:
https://issues.jboss.org/browse/KEYCLOAK-2768
Jira for reg. flow:
https://issues.jboss.org/browse/KEYCLOAK-2740
Thanks,
Libor Krzyžanek
Principal Software Engineer
Red Hat Developers | Engineering
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev