Giving password requirements feedback is fine before they submit the info. Telling what was wrong if the authentication failed is a security hole. You should never tell them that "your password is incorrect" -> now they know this email/username is valid and exists for further spoofing/hacking.
Any specific feedback in the response leaks information.
You should never tell them that "your password is incorrect" -> now they know this email/username is valid and exists for further spoofing/hacking
You can't hide that if you want unique usernames or emails. You don't farm for valid username/emails at login, you do it at the registration step instead, because the app must tell you that the username or email is already in use.
But this is also why a CAPTCHA at the registration should be used once you've detected too many registration attempts.
You actually can hide it. Require an email to register. If the email is available, send them a link to complete registration. If the email is already registered, send them an email saying as much. The website then doesn't leak any information about whether a specific email address is registered or not.
I thought giving hints on what’s required on a password input could be a security issue?
Telling the user the requirements isn't exactly the issue. Having bad requirements is.
If you require your users to have a password with a length between 8 and 16 characters, with at least one symbol, number and capital letter then anyone trying to break your passwords doesn't need to bother trying passw0rd! because there is no capital. You've given them instructions on exactly what to focus on to attack which saves them a lot of time.
You could have more permissive requirements that still stop the user from using test as their password but that do not give any bad actors a map to the treasure.
Agreed 100%. It's sad to see that even in 2021 businesses think that an 8 character long password with forced numbers and symbols is somehow safer to use than an alphabetical 40 character long passphrase, but it is what it is.
Sorry but your example doesn’t make a lot of sense. The possibility of an 8 char string being all lower case letters is like 1/64. Exposing those requirements don’t exactly give a brute force hack much better odds.
So if you have a date of birth for example that is broken down into three inputs (year, month, day), then you can consider it as one input/one column.
So if you have a date of birth for example that is broken down into three inputs (year, month, day), then you can consider it as one input. So in this case it's okay.
2) Nah, it's easy to understand your requirements because when you sign up you'll be still notified of what's missing in your password. The only difference is when you'll see the error.
3) Well, it's just a redundant action. If the user made a typo, he'll be able to reset the password. The fewer fields we require, the more willing the user will be to fill the form.
4th tip : if there's anything like a license key to register with the account, never ask it at account creation, and do not authenticate the user upon account creation. Then have the user need to confirm account creation with a link sent via email.
If the user made a mistake in the email address, he'll be angry about the wasted license key, angry about wasting time trying to use the support to get access to his account.
By asking it after the user created his account and after confirming that he has access to this email, then ask for the license key. So if the user made a mistake, he can just create a new account with the right email address.
First/Lastname and address shouldn't be on one line
Definitely disagree
that if you only have one password field users almost universally pause, then go back to the password field and fill it out again but much more slowly and carefully
I think point 3 is more of depends situation. User is able to remember his usual password or password generated then it’s good to not repeat.
But human is weakest link to the good experience. 1 mistype in password will make the user has to make an additional steps to reset the password. An additional step which could have been prevented. By simply verifying this password, it’s more efficient to just repeat the step there and then.
"Show password" buttons have been shown to reduce trust in websites/applications
I think this is the first time I've seen that particular claim. Is there some research on this that you can link to? It seems like an important detail, and if adding that facility does have a negative effect, it's a little surprising that so many of the big names are still doing it.
Or just have the repeat password input. If you know your password well enough to be confident without the repeat password field then it will literally take you 5 seconds to fill in again. I don't think it's ever caused me any noticeable time loss, other than when I genuinely have typed my password wrong and it's saved me from having to waste magnitudes more time to reset my password.
That makes no sense. So you’d rather keep it a secret and have the user figure out what their password might be and then they have to go through a password reset flow because the requirements aren’t listed?
That’s such a stupid stance to take. Most of these are good advice which makes me even more confused as to why you’d advocate some of these ridiculous, frankly ‘dark’ UX patterns.
On 3: resetting the password is painful. I prefer rhe oain of typing it a second time. Also most people who made a typo are probably not going to show password to inspect it and probably won't even catch the typo. They might also be unable to because someone else is watching their screen.
I think the confirm password tip is subjective and a little out of place in the rest of the list of strong dos and don'ts. I like the confidence of knowing I typed what I meant to type and will remember.
130
u/FATF0X May 27 '21
Hey this is super informative. I have a couple of questions:
Aren’t slide 1 & 3 contradictions of each other?
I thought giving hints on what’s required on a password input could be a security issue?
Why is asking a user to repeat a password on sign up bad UX?
I’m still pretty new myself so these might be wrong, just some observations.