5:04 a.m.
I suggest we change the error message when a login times out or a code is
not valid to:
"This page is no longer valid, please retry login from the application" and
also include a link to the application if available.
I think that's more user friendly than "You took to long" and
"We're
sorry...".
5:11 a.m.
"Not long valid" is somewhat vague. To avoid confusion, I'd try to be as
clear as possible about what's going on and what should be done to resolve
the problem. At the same time, do not refer to the user ('you') directly,
to have a friendlier tone-of-voice:
"A timeout has occurred. Please reload this page."
On 6 April 2016 at 12:04, Stian Thorgersen <sthorger(a)redhat.com> wrote:
I suggest we change the error message when a login times out or a
code is
not valid to:
"This page is no longer valid, please retry login from the application"
and also include a link to the application if available.
I think that's more user friendly than "You took to long" and
"We're
sorry...".
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
5:21 a.m.
The page is no longer valid, that's really what's going on ;)
There's mainly three scenarios when this happens:
* User clicks link twice in an email (for example reset password)
* User clicks link in email after it has expired
* User spends to long on the login form(s)
Problem is that we don't know exactly which of the above is the problem as
the session details may be lost. So I believe "This page is no longer
valid" is generic and still gives the user an idea of what's happened.
Refreshing the page is not going to help as the page is no longer valid
(login details are either lost due to timeout, or login has already
happened), so to resolve the problem the user has to "try login again from
the application". We can replace "the application" with the name of the
client if we now it and also make it clickable if the client has a baseurl
set.
On 6 April 2016 at 12:11, Guus der Kinderen <guus.der.kinderen(a)gmail.com>
wrote:
"Not long valid" is somewhat vague. To avoid confusion,
I'd try to be as
clear as possible about what's going on and what should be done to resolve
the problem. At the same time, do not refer to the user ('you') directly,
to have a friendlier tone-of-voice:
"A timeout has occurred. Please reload this page."
On 6 April 2016 at 12:04, Stian Thorgersen <sthorger(a)redhat.com> wrote:
> I suggest we change the error message when a login times out or a code is
> not valid to:
> "This page is no longer valid, please retry login from the application"
> and also include a link to the application if available.
>
> I think that's more user friendly than "You took to long" and
"We're
> sorry...".
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
5:22 a.m.
Ah, I was only aware of that last scenario. Serves me right for butting in
on things I know next to nothing about. ;)
On 6 April 2016 at 12:21, Stian Thorgersen <sthorger(a)redhat.com> wrote:
The page is no longer valid, that's really what's going on
;)
There's mainly three scenarios when this happens:
* User clicks link twice in an email (for example reset password)
* User clicks link in email after it has expired
* User spends to long on the login form(s)
Problem is that we don't know exactly which of the above is the problem as
the session details may be lost. So I believe "This page is no longer
valid" is generic and still gives the user an idea of what's happened.
Refreshing the page is not going to help as the page is no longer valid
(login details are either lost due to timeout, or login has already
happened), so to resolve the problem the user has to "try login again from
the application". We can replace "the application" with the name of the
client if we now it and also make it clickable if the client has a baseurl
set.
On 6 April 2016 at 12:11, Guus der Kinderen <guus.der.kinderen(a)gmail.com>
wrote:
> "Not long valid" is somewhat vague. To avoid confusion, I'd try to be
as
> clear as possible about what's going on and what should be done to resolve
> the problem. At the same time, do not refer to the user ('you') directly,
> to have a friendlier tone-of-voice:
>
> "A timeout has occurred. Please reload this page."
>
>
>
> On 6 April 2016 at 12:04, Stian Thorgersen <sthorger(a)redhat.com> wrote:
>
>> I suggest we change the error message when a login times out or a code
>> is not valid to:
>> "This page is no longer valid, please retry login from the
application"
>> and also include a link to the application if available.
>>
>> I think that's more user friendly than "You took to long" and
"We're
>> sorry...".
>>
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>
5:22 a.m.
On 06.04.2016 12:04, Stian Thorgersen wrote:
I suggest we change the error message when a login times out or a
code
is not valid to:
"This page is no longer valid, please retry login from the application"
and also include a link to the application if available.
I think that's more user friendly than "You took to long" and
"We're
sorry...".
While I, as an user, would probably understand what went wrong with a
message like "You took too long" and would accept my fate, I would have
no idea what I did wrong to deserve a "This page is no longer valid".
Perhaps phrasing it in a way that is both informative and friendly?
- Juca.
5:47 a.m.
Suggestions are welcome ;)
That's the best I can come up with
On 6 April 2016 at 12:22, Juraci Paixão Kröhling <juraci(a)kroehling.de>
wrote:
On 06.04.2016 12:04, Stian Thorgersen wrote:
> I suggest we change the error message when a login times out or a code
> is not valid to:
> "This page is no longer valid, please retry login from the application"
> and also include a link to the application if available.
>
> I think that's more user friendly than "You took to long" and
"We're
> sorry...".
While I, as an user, would probably understand what went wrong with a
message like "You took too long" and would accept my fate, I would have
no idea what I did wrong to deserve a "This page is no longer valid".
Perhaps phrasing it in a way that is both informative and friendly?
- Juca.
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
5:57 a.m.
Is it an option to have distinct messages for each scenario?
"This page is no longer valid (the link you used to get to this page can
only be used once)."
"The link you used to get to this page has expired."
"This page has timed-out. Please reload the page and try again."
On 6 April 2016 at 12:47, Stian Thorgersen <sthorger(a)redhat.com> wrote:
Suggestions are welcome ;)
That's the best I can come up with
On 6 April 2016 at 12:22, Juraci Paixão Kröhling <juraci(a)kroehling.de>
wrote:
> On 06.04.2016 12:04, Stian Thorgersen wrote:
> > I suggest we change the error message when a login times out or a code
> > is not valid to:
> > "This page is no longer valid, please retry login from the
application"
> > and also include a link to the application if available.
> >
> > I think that's more user friendly than "You took to long" and
"We're
> > sorry...".
>
> While I, as an user, would probably understand what went wrong with a
> message like "You took too long" and would accept my fate, I would have
> no idea what I did wrong to deserve a "This page is no longer valid".
>
> Perhaps phrasing it in a way that is both informative and friendly?
>
> - Juca.
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev
6:09 a.m.
On 06.04.2016 12:47, Stian Thorgersen wrote:
Suggestions are welcome ;)
Taking the scenarios from your other email, an initial suggestion could be:
<<EOD
Unfortunately, we cannot securely log you in at this time. Please, go
back to the application and try to login again.
Reasons for this might include:
* You didn't promptly login when reaching the login page;
* The link you used to reach the login page has already been used;
* The link you received to reach the login page has expired.
EOD
3186
days inactive
3186
days old
7 comments
3 participants
participants (3)
-
Guus der Kinderen -
Juraci Paixão Kröhling -
Stian Thorgersen