Updating from 1.11.4 to 1.12.1 broke ldap auth #5681

New Issue

GiteaMirror · 2025-11-02T06:32:56-06:00

GiteaMirror commented

2025-11-02 06:32:56 -06:00

Originally created by @dalito on GitHub (Jul 3, 2020).

Gitea version (or commit ref): gitea-1.12.1-windows-4.0-amd64
Git version: Git-2.25.0
Operating system: Windows Server 2008 SP2
Database):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

2020/07/02 20:19:54 ...s/graceful/server.go:55:NewServer() [I] Starting new server: tcp:0.0.0.0:3000 on PID: 3852
2020/07/02 20:20:27 routers/user/auth.go:176:SignInPost() [I] Failed authentication attempt for user12 from 192.168.24.59
2020/07/02 20:20:54 cmd/web.go:206:runWeb() [I] HTTP Listener: 0.0.0.0:3000 Closed

After this update users which authenticated via ldap can no longer login via the Web interface and can also not commit/push to the git-repos from command line. I can still login with a (gitea-)local admin account.

I can exclude that something changed in our ActiveDirectory setup. The "user12" from the log can still login to other services using ldap auth. The log was generated with level=Trace but does not contain helpful information.

I would appreciate hints on how to better debug this issue and on which code changes may be related.

Originally created by @dalito on GitHub (Jul 3, 2020). - Gitea version (or commit ref): gitea-1.12.1-windows-4.0-amd64 - Git version: Git-2.25.0 - Operating system: Windows Server 2008 SP2 - Database): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ``` 2020/07/02 20:19:54 ...s/graceful/server.go:55:NewServer() [I] Starting new server: tcp:0.0.0.0:3000 on PID: 3852 2020/07/02 20:20:27 routers/user/auth.go:176:SignInPost() [I] Failed authentication attempt for user12 from 192.168.24.59 2020/07/02 20:20:54 cmd/web.go:206:runWeb() [I] HTTP Listener: 0.0.0.0:3000 Closed ``` After this update users which authenticated via ldap can no longer login via the Web interface and can also not commit/push to the git-repos from command line. I can still login with a (gitea-)local admin account. I can exclude that something changed in our ActiveDirectory setup. The "user12" from the log can still login to other services using ldap auth. The log was generated with level=Trace but does not contain helpful information. I would appreciate hints on how to better debug this issue and on which code changes may be related.

GiteaMirror closed this issue

2025-11-02 06:32:56 -06:00

GiteaMirror commented

2025-11-02 06:32:57 -06:00

@dalito commented on GitHub (Jul 3, 2020):

Solved. It finally turned out that it was a local problem related to AD.

@dalito commented on GitHub (Jul 3, 2020): Solved. It finally turned out that it was a local problem related to AD.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5681