10:35 p.m.
Right now, if there is a timeout between actions when logging in, we
show an error page. I think I'd rather we just reset the ClientSession
and start over from the beginning. Might be a bit more user friendly.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
10:44 p.m.
The current behavior is less than ideal and not a good user experience, but what happens
if the session on client times out? It’s not going to be able to reconcile the state on
redirect after login. Maybe the behavior should be configurable? Maybe I’m missing
something. What do you mean by reset the ClientSession and start over from the beginning?
Where is the beginning?
~ Scott
On Jun 18, 2015, at 4:35 PM, Bill Burke <bburke(a)redhat.com>
wrote:
Right now, if there is a timeout between actions when logging in, we
show an error page. I think I'd rather we just reset the ClientSession
and start over from the beginning. Might be a bit more user friendly.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
10:47 p.m.
We have a timeout between login actions. For example, you enter your
username password, get redirected to OTP form, wait 5 minutes, then a
timeout happens. You are currently booted out with an Error page. The
ClientSession can still exist as it may not have been reaped by the
reaper thread yet.
On 6/18/2015 4:44 PM, Scott Rossillo wrote:
The current behavior is less than ideal and not a good user
experience, but what happens if the session on client times out? It’s not going to be able
to reconcile the state on redirect after login. Maybe the behavior should be configurable?
Maybe I’m missing something. What do you mean by reset the ClientSession and start over
from the beginning? Where is the beginning?
~ Scott
> On Jun 18, 2015, at 4:35 PM, Bill Burke <bburke(a)redhat.com> wrote:
>
> Right now, if there is a timeout between actions when logging in, we
> show an error page. I think I'd rather we just reset the ClientSession
> and start over from the beginning. Might be a bit more user friendly.
>
> --
> Bill Burke
> JBoss, a division of Red Hat
> http://bill.burkecentral.com
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
9:47 a.m.
+1 Just replied the same in a separate email ;)
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 18 June, 2015 10:35:18 PM
Subject: [keycloak-dev] auth timeout behavior change
Right now, if there is a timeout between actions when logging in, we
show an error page. I think I'd rather we just reset the ClientSession
and start over from the beginning. Might be a bit more user friendly.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
9:03 a.m.
+1, we hit this problem on our site, users are not happy seeing the
error page, we had to customize it to give them some meaningful flow.
Some info message should be shown to the user to inform him that timeout
occurred not to be too surprised what is going on.
Vl.
On 18.6.2015 22:35, Bill Burke wrote:
Right now, if there is a timeout between actions when logging in, we
show an error page. I think I'd rather we just reset the ClientSession
and start over from the beginning. Might be a bit more user friendly.
--
Vlastimil Elias
Principal Software Engineer
jboss.org Development Team
3224
days inactive
3228
days old
4 comments
4 participants
participants (4)
-
Bill Burke -
Scott Rossillo -
Stian Thorgersen -
Vlastimil Elias