[keycloak-dev] Issues with the first login flow
Gabriel Cardoso
gcardoso at redhat.com
Wed May 21 10:46:05 EDT 2014
The problem I see is that people don’t read these messages. They assume that it is an error or something.
I think the text above (some different from a feedback message) is more effective, and the extra field (username) helps on the differentiation. It could be plain text instead of an input.
I don’t believe this solution will solve the problem.
Gabriel
On May 21, 2014, at 4:37 AM, Stian Thorgersen <stian at redhat.com> wrote:
> I added it the way you said, and to me it doesn't stand out at all. How about moving the notification bubble we already have to be in-line with the form? That would also make all other notifications, such as invalid username/password stand out more as well. See attached screenshot for how that would look like.
>
> Adding a disabled input field for username doesn't make sense at all to me. An input field is not informative, it's an input field and hence something users expect to fill in.
>
> ----- Original Message -----
>> From: "Gabriel Cardoso" <gcardoso at redhat.com>
>> To: "Stian Thorgersen" <stian at redhat.com>
>> Cc: "Bill Burke" <bburke at redhat.com>, keycloak-dev at lists.jboss.org
>> Sent: Tuesday, 20 May, 2014 7:11:20 PM
>> Subject: Re: [keycloak-dev] Issues with the first login flow
>>
>>> He's not logged-in, those are actions that the user are required to do
>>> prior to be logged-in. The user will however have to identify himself with
>>> username/password (and totp if configured) prior to being permitted to do
>>> those actions. The actions a user can be asked to do as part of a login is
>>> not just limited to updating the password. These can include:
>>>
>>> * Configure TOTO
>>> * Update password
>>> * Verify email
>>> * Update profile
>>>
>>> And, possible more to come in the future.
>>
>> Thanks for the clarification.
>>
>>> Text above we already have in a notification thing, but I don't have a
>>> problem with moving that above the form. The username input field doesn't
>>> make sense at all, as the user is not able to change that at this stage.
>>
>> Cool, so please put the text inside a <p class=“form-info”></p>.
>>
>> The username field is to differentiate more this page from the login page (3
>> fields are different than 2 :) I don’t see it as a problem, it is
>> informative and the user can’t change it (no danger). So now it is up to
>> you.
>>
>> Thanks,
>> Gabriel
>>
>>>
>>>>
>>>> Gabriel
>>>>
>>>> ---
>>>> Gabriel Cardoso
>>>> User Experience Designer @ Red Hat
>>
>> ---
>> Gabriel Cardoso
>> User Experience Designer @ Red Hat
>>
> <login-notification.png>
---
Gabriel Cardoso
User Experience Designer @ Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-dev/attachments/20140521/b8333836/attachment.html
More information about the keycloak-dev
mailing list