Active Directory authentication fails after upgrade from 1.7.0 to 1.7.1 #2843

New Issue

GiteaMirror · 2025-11-02T04:50:47-06:00

GiteaMirror commented

2025-11-02 04:50:47 -06:00

Originally created by @sorin-p on GitHub (Feb 1, 2019).

Gitea version (or commit ref): 1.7.1
Git version: 2.11.0
Operating system:
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

2019/02/01 10:18:25 [T] Dialing LDAP with security protocol (1) without verifying: true
2019/02/01 10:18:26 [T] LDAP will bind directly via UserDN template: CN=%s,CN=Users,DC=blabladomain,DC=com
2019/02/01 10:18:26 [T] Binding with userDN: CN=UserName,CN=Users,DC=blabladomain,DC=com
2019/02/01 10:18:26 [D] LDAP auth. failed for CN=UserName,CN=Users,DC=blabladomain,DC=com, reason: LDAP Result Code 200 "Network Error": ldap: response channel closed
2019/02/01 10:18:26 [D] Template: user/auth/signin
2019/02/01 10:18:26 [I] Failed authentication attempt for UserName from ...

Description

Logging in with users from Active Directory source does not work after upgrade to v1.7.1
Deleted, recreated the users and the same error persists. Some fragments from the log were replaced with dummy values.

Screenshots

Originally created by @sorin-p on GitHub (Feb 1, 2019). - Gitea version (or commit ref): 1.7.1 - Git version: 2.11.0 - Operating system: - Database (use `[x]`): - [ ] 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: ``` 2019/02/01 10:18:25 [T] Dialing LDAP with security protocol (1) without verifying: true 2019/02/01 10:18:26 [T] LDAP will bind directly via UserDN template: CN=%s,CN=Users,DC=blabladomain,DC=com 2019/02/01 10:18:26 [T] Binding with userDN: CN=UserName,CN=Users,DC=blabladomain,DC=com 2019/02/01 10:18:26 [D] LDAP auth. failed for CN=UserName,CN=Users,DC=blabladomain,DC=com, reason: LDAP Result Code 200 "Network Error": ldap: response channel closed 2019/02/01 10:18:26 [D] Template: user/auth/signin 2019/02/01 10:18:26 [I] Failed authentication attempt for UserName from ... ``` ## Description Logging in with users from Active Directory source does not work after upgrade to v1.7.1 Deleted, recreated the users and the same error persists. Some fragments from the log were replaced with dummy values. ## Screenshots

GiteaMirror added the type/bug label 2025-11-02 04:50:47 -06:00

GiteaMirror closed this issue

2025-11-02 04:50:47 -06:00

GiteaMirror commented

2025-11-02 04:50:48 -06:00

@lafriks commented on GitHub (Feb 1, 2019):

What OS are you run gitea on?

@lafriks commented on GitHub (Feb 1, 2019): What OS are you run gitea on?

GiteaMirror commented

2025-11-02 04:50:48 -06:00

@sorin-p commented on GitHub (Feb 1, 2019):

Linux armv7l

@sorin-p commented on GitHub (Feb 1, 2019): Linux armv7l

GiteaMirror commented

2025-11-02 04:50:48 -06:00

@nigeldixon commented on GitHub (Feb 1, 2019):

Same report, but different error:
ldap: recovered panic in processMessages: runtime error: invalid memory address or nil pointer dereference

I'm running in docker but also on armv7 with SQLite db

@nigeldixon commented on GitHub (Feb 1, 2019): Same report, but different error: `ldap: recovered panic in processMessages: runtime error: invalid memory address or nil pointer dereference` I'm running in docker but also on armv7 with SQLite db

GiteaMirror commented

2025-11-02 04:50:48 -06:00

@mootboy commented on GitHub (Feb 18, 2019):

Is this fixed by #6107?

@mootboy commented on GitHub (Feb 18, 2019): Is this fixed by #6107?

GiteaMirror commented

2025-11-02 04:50:49 -06:00

@lafriks commented on GitHub (Feb 19, 2019):

I think it should be, please reopen if it is not

@lafriks commented on GitHub (Feb 19, 2019): I think it should be, please reopen if it is not

GiteaMirror referenced this issue

2025-11-02 12:15:02 -06:00