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