-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Failed authentication attempt is logged with text 'user does not exist' even when the user exists #24498
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
Labels
Comments
Hitting the same on 1.20 running on RHEL8.4 where Gitea version 1.20.0+rc0-58-g28ed763f5 built with GNU Make 4.3, go1.20.5 : bindata, sqlite, sqlite_unlock_notify
|
I think |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Log entry:
...ers/web/auth/auth.go:206:SignInPost() [I] [645256b1] Failed authentication attempt for user from ip: user does not exist [uid: 2, name: user, keyid: 0]
Description
I tried to fail authentication by using wrong password and I looked at the log file. There is failed authentication attempt information log with additional text: 'user does not exist', however user exists and I can login when provided good password.
Expected Fix
Log authentication attempt fail log without text 'user does not exist' when user exists
Gitea Version
1.19.2
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.30.2
Operating System
Debian
How are you running Gitea?
Running binary gitea behind nginx proxy
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: