Repository navigation
Password Visibilty Toggle
#13369
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone,
a short while ago we (my project team) started to use Keycloak and during the implementation and testing our Stakeholder expressed some concerns or wishes for customization. Because we don't want to build to much of Keycloak our self and maintain our own version, we thought it would be a good idea to propose those changes here and see what’s the general feedback. Also, since we might contribute a lot in the future, any information’s, or tips on how to do so more efficient are appreciated. But now to the topic.
In the UI, more specific in all templates where the user must type his password (for example the update password page) there is currently no way to show the password in cleartext. We learned in the past that a simple button (for example in the form of an eye) to toggle between cleartext and hidden state, improves the usability quite a lot, since many users are struggling with typing the password completely blind. For us it has reduced the amount of service tickets we gained quite a lot.
For security reasons the password could/should only be displayed for a fixed amount of time, let’s say 30 seconds, before automatically switching back to hidden state.
Since we only use a few of the features Keycloak provides I am not completely sure of all the places a password input field exists, but as far as I can see it should be in the register, login-update-password and the login-password pages of the login template. Please correct me if I missed one here.
Also, I found an stale PR from November last year concerning such an feature:
https://github.com/keycloak/keycloak/pull/8689/files
I am not sure if there were reasons why it went stale other than that it seems incomplete in its implementation, since there are no further discussions there.
So, for the whole discussion part, are there any reasons such a feature hasn’t been implemented or do you see any other problems this would cause?
Should this feature be enabled by default, or should there be an option to choose in the admin console, whether to use it or not?
Do you have any other thoughts or ideas that could be important for realizing that feature?
All reactions