-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong error msg for incorrect password during login #5114
Comments
I'd like to work on this. Thanks :) |
Sure, go ahead @ananyaarun |
@gauravano , Can you tell me what This line exactly does ? to solve this issue i replaced it with a flash warning msg and then a redirect
that solved the issue but other cases of login functionality seem to break by this method not sure why. |
the line you referred take the control to here-
It behaves just as render template - https://stackoverflow.com/questions/5045222/difference-between-render-action-and-render-template I think "Password is not valid" message is default one shown by rails authlogic? |
I think flash message will not be that appropriate to inform/give message such as password validation or captcha fail, etc, as user can ignore flash message easily |
Hmm makes sense, But isnt this msg a bit unrelated ? As in why display "1 error prohibited this user session from being saved " to an external user ? |
That's how devise show errors |
Ok so if that's the case i assume we cant change it right ? So shall we let the error msg be then ? |
I think we can. Or, we can jump on it and implement our validation? @jywarren what do you think here? |
If its possible to change i definitely think "1 error prohibited user session from being saved" can be removed. |
Description
The issue of not allowing null fields either for username or password during login was taken care of in #5087 , But when a user enters a correct user name (ie present in db) followed by an incorrect password, Instead of a msg saying wrong password this pops up.

Solution
An error msg saying Pls enter correct password or incorrect password should pop up instead of this. I feel this error msg is misleading to a common user.
The text was updated successfully, but these errors were encountered: