github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-25 07:56:03 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

After Update to 1.17.4 LDAP Login is not working anymore #10096

New Issue
Open
opened 2025-11-02 08:58:06 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 08:58:06 -06:00
Owner
Copy Link

Originally created by @phatair on GitHub (Jan 13, 2023).

Description

Hello,
we updated our Gitea Server to 1.17.4 and after the Update one user can not login anymore.
We use LDAP Authentication and other Users can login without any problem. The user could login with the old version without any problems.
In the Log i can see the following error

2023/01/13 07:28:40 ...s/context/context.go:220:HTML() [D] [63c0fa18] Template: home 2023/01/13 07:29:02 ...s/context/context.go:220:HTML() [D] [63c0fa2e] Template: user/auth/signin 2023/01/13 07:29:08 ...dap/source_search.go:98:findUserDN() [D] [63c0fa34] Failed search using filter[(&(objectCategory=Person)(memberOf=CN=Sec_Gitea-Users,OU=Sicherheitsgruppen,OU=xxx,DC=our,DC=internal,DC=domain)(sAMAccountName=<username removed>@domain.com)(!(UserAccountControl:1.2.840.113556.1.4.803:=2)))]: <nil> 2023/01/13 07:29:08 ...s/context/context.go:220:HTML() [D] [63c0fa34] Template: user/auth/signin 2023/01/13 07:29:08 ...ers/web/auth/auth.go:200:SignInPost() [I] [63c0fa34] Failed authentication attempt for <username removed> from xxx.xxx.xxx.xxx:57540: user does not exist [uid: 0, name: <username removed>@domain.com, keyid: 0]

The strange thing is this this information in the Log -> (sAMAccountName=@mail.com)
The sAMAccountName is not @domain.com, this is normally the userprincipalname.

Does everyone has the same problem or can help me with this problem?
Thanks a lot.

Gitea Version

1.17.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Ubuntu 20.04.3

How are you running Gitea?

Gitea is running on Ubuntu 20.04.3
Installed with the official binarys.

Database

MySQL

Originally created by @phatair on GitHub (Jan 13, 2023). ### Description Hello, we updated our Gitea Server to 1.17.4 and after the Update one user can not login anymore. We use LDAP Authentication and other Users can login without any problem. The user could login with the old version without any problems. In the Log i can see the following error `2023/01/13 07:28:40 ...s/context/context.go:220:HTML() [D] [63c0fa18] Template: home 2023/01/13 07:29:02 ...s/context/context.go:220:HTML() [D] [63c0fa2e] Template: user/auth/signin 2023/01/13 07:29:08 ...dap/source_search.go:98:findUserDN() [D] [63c0fa34] Failed search using filter[(&(objectCategory=Person)(memberOf=CN=Sec_Gitea-Users,OU=Sicherheitsgruppen,OU=xxx,DC=our,DC=internal,DC=domain)(sAMAccountName=<username removed>@domain.com)(!(UserAccountControl:1.2.840.113556.1.4.803:=2)))]: <nil> 2023/01/13 07:29:08 ...s/context/context.go:220:HTML() [D] [63c0fa34] Template: user/auth/signin 2023/01/13 07:29:08 ...ers/web/auth/auth.go:200:SignInPost() [I] [63c0fa34] Failed authentication attempt for <username removed> from xxx.xxx.xxx.xxx:57540: user does not exist [uid: 0, name: <username removed>@domain.com, keyid: 0]` The strange thing is this this information in the Log -> (sAMAccountName=<username removed>@mail.com) The sAMAccountName is not @domain.com, this is normally the userprincipalname. Does everyone has the same problem or can help me with this problem? Thanks a lot. ### Gitea Version 1.17.4 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Ubuntu 20.04.3 ### How are you running Gitea? Gitea is running on Ubuntu 20.04.3 Installed with the official binarys. ### Database MySQL
GiteaMirror added the topic/authenticationtype/bug labels 2025-11-02 08:58:06 -06:00
GiteaMirror commented 2025-11-02 08:58:07 -06:00
Author
Owner
Copy Link

@phatair commented on GitHub (Jan 13, 2023):

Found the problem. For this User the username for authentictaion in the Gitea Local user was set to username@domain.com and not to username
So Gitea searches for username@domain.com in the sAMAccountName and that was wrong.

We didnt changed anything on the LDAP/Gitea Account. So i think maybe there was changed something in the 1.17.4 version (or ealier, we used befor a version from 1.16.x).

Maybe this help someone.

@phatair commented on GitHub (Jan 13, 2023): Found the problem. For this User the username for authentictaion in the Gitea Local user was set to username@domain.com and not to username So Gitea searches for username@domain.com in the sAMAccountName and that was wrong. We didnt changed anything on the LDAP/Gitea Account. So i think maybe there was changed something in the 1.17.4 version (or ealier, we used befor a version from 1.16.x). Maybe this help someone.
GiteaMirror commented 2025-11-02 08:58:07 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Mar 17, 2023):

Maybe this PR is related?
https://github.com/go-gitea/gitea/pull/18789

@yp05327 commented on GitHub (Mar 17, 2023): Maybe this PR is related? https://github.com/go-gitea/gitea/pull/18789
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/authentication type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10096
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?