You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you create a new account through normal sign-up, and immediately try to log in, this will fail due to the account not being authorized yet, but the error message will read "Invalid username or password". That gives users an incorrect idea about why they are unable to login and may lead to frustration.
It would be better if failed login attempts would distinguish between "correct credentials but no authorization" and "wrong credentials" and displayed an appropriate error message.
The text was updated successfully, but these errors were encountered:
It might be worth another think if this exposes (the correctness of) login credentials, maybe check for authorization before checking correctness.
I've decided that this is a negligible concern, since this only has any effect if a would-be attacker knows or correctly guesses the user's password. Normally, that would just lead to login, which is equally unfortunate. If this is too risky for anyone, they can default to the n-attempts-to-ban mechanic.
Currently, if you create a new account through normal sign-up, and immediately try to log in, this will fail due to the account not being authorized yet, but the error message will read "Invalid username or password". That gives users an incorrect idea about why they are unable to login and may lead to frustration.
It would be better if failed login attempts would distinguish between "correct credentials but no authorization" and "wrong credentials" and displayed an appropriate error message.
The text was updated successfully, but these errors were encountered: