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

LDAP user sync does not work (here) #2047

New Issue
Closed
opened 2025-11-02 04:22:17 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:22:17 -06:00
Owner
Copy Link

Originally created by @cklabautermann on GitHub (Jul 12, 2018).

  • Gitea version (or commit ref): 1.4.0, 1.4.2,1.4.3,1.5.0RC2
  • Git version: 2.7.4-0ubuntu1.4
  • Operating system: Ubuntu Server 16.04.4 AMD64
  • 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:

Description

my auth setup includes

  • bind to a ms-AD unencrypted
  • with a RO userid
  • a user search base where the users are
  • a user filter pointing to a group in a completely different OU
  • user synchronisation activated (at least marked)

Things that work:

  • manually adding a user and authenticating them via LDAP. If a user is not member in the filter group, they can not login.

Things that do not work:

  • users in my filter group being automatically synchronized

Additionally all users authenticating via ldap get deactivated if I dare to execute a manual user synchronisation via web frontend.

Can anybody tell me what I am doing wrong?
Not sure if screenshots could help here but I can upload some on demand.

Thanks,
Claudio

Originally created by @cklabautermann on GitHub (Jul 12, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.4.0, 1.4.2,1.4.3,1.5.0RC2 - Git version: 2.7.4-0ubuntu1.4 - Operating system: Ubuntu Server 16.04.4 AMD64 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description my auth setup includes - bind to a ms-AD unencrypted - with a RO userid - a user search base where the users are - a user filter pointing to a group in a **completely different** OU - user synchronisation activated (at least marked) Things that work: - manually adding a user and authenticating them via LDAP. If a user is not member in the filter group, they can not login. Things that do not work: - users in my filter group being automatically synchronized Additionally all users authenticating via ldap **get deactivated** if I dare to execute a manual user synchronisation via web frontend. Can anybody tell me what I am doing wrong? Not sure if screenshots could help here but I can upload some on demand. Thanks, Claudio
GiteaMirror added the issue/staletype/bug labels 2025-11-02 04:22:17 -06:00
GiteaMirror commented 2025-11-02 04:22:18 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 18, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 18, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:22:18 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 7, 2019):

@cklabautermann is this still a problem?

@lunny commented on GitHub (Feb 7, 2019): @cklabautermann is this still a problem?
GiteaMirror commented 2025-11-02 04:22:18 -06:00
Author
Owner
Copy Link

@cklabautermann commented on GitHub (Feb 7, 2019):

@lunny yes, unfortunately it still does not work. Can you help?
Thanks in advance

@cklabautermann commented on GitHub (Feb 7, 2019): @lunny yes, unfortunately it still does not work. Can you help? Thanks in advance
GiteaMirror commented 2025-11-02 04:22:18 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 8, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 8, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:22:18 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 22, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Apr 22, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
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 issue/stale 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#2047
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?