-
Notifications
You must be signed in to change notification settings - Fork 20
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
Report when authentication fails #14
Comments
And I wonder if the /login page should really return 401 when accessed directly or when the login fails or if should be 200. |
IMHO you should provide your own login page if you want to show error message to the user. |
That's probably right, but I think it would be nice if it was there without extra work. It would certainly make it simpler to show it. (demo it) |
Actually there is support for |
I noticed this when I was doing my updates. I was going to fix it at the time, but thought I should keep it separate from my PR. It's a simple fix:
should read
Which also means that this line can be removed:
I'll do a PR if it's easier, but if you just search the code for |
I think this should be saved into the session so it can't be tampered with. |
I don't think it can be tampered with, as it's a |
Currently, as I can see, if the user types in an incorrect username/password pair the default /login page will be shown again without any explanation. IMHO it would be nicer if there was a default error message about the failed authentication.
The text was updated successfully, but these errors were encountered: