We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Analysing our gitea log files we see a lot of the following log messages:
routers/web/web.go:121:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
It looks like this is a log in web.go:
log.Error("Failed to verify user: %v", err)
Having an error in the logs for every wrong auth attempt could explode the log files and hide other important messages.
Additional question: is the OAUTH_USER a special user?
1.22.3
No
No response
Binary + MariaDb
MySQL/MariaDB
The text was updated successfully, but these errors were encountered:
What are the logs around it? Is there any one trying to use "OAUTH_USER" as user name to try to login?
Sorry, something went wrong.
I only got the error logs for this system and nearly the only output we get is this log message logged multiple times.
But while digging through some other issues i think this is a duplicate of the following issue:
#31470
No branches or pull requests
Description
Analysing our gitea log files we see a lot of the following log messages:
routers/web/web.go:121:func9() [E] Failed to verify user: user does not exist [uid: 0, name: OAUTH_USER]
It looks like this is a log in web.go:
log.Error("Failed to verify user: %v", err)
Having an error in the logs for every wrong auth attempt could explode the log files and hide other important messages.
Additional question: is the OAUTH_USER a special user?
Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Binary + MariaDb
Database
MySQL/MariaDB
The text was updated successfully, but these errors were encountered: