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

gitea deactivate LDAP users #7126

New Issue
Closed
opened 2025-11-02 07:16:24 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 07:16:24 -06:00
Owner
Copy Link

Originally created by @dvgoyeneche on GitHub (Apr 7, 2021).

We have our Gitea instance using Active Directory as our LDAP server, but the exact same thing occurs whenever a directory sync is performed, all existing users lose their activated status. The only fix is to go in and manually edit every account to set them as activated.

Version: v1.14.0-rc2

Originally created by @dvgoyeneche on GitHub (Apr 7, 2021). We have our Gitea instance using Active Directory as our LDAP server, but the exact same thing occurs whenever a directory sync is performed, all existing users lose their activated status. The only fix is to go in and manually edit every account to set them as activated. Version: v1.14.0-rc2
GiteaMirror added the topic/authenticationissue/needs-feedback labels 2025-11-02 07:16:24 -06:00
GiteaMirror commented 2025-11-02 07:16:25 -06:00
Author
Owner
Copy Link

@m0rtalis commented on GitHub (May 27, 2021):

Can confirm. Same issue.

I try to debug it more tomorrow.

Gitea Authenticationsource

Edit: Add settings authenticationsource

@m0rtalis commented on GitHub (May 27, 2021): Can confirm. Same issue. - Gitea version (or commit ref): 1.14.2 - Git version: 2.25.1 - Operating system: Ubuntu 20.04.2 LTS - Installed via: `wget -O gitea https://dl.gitea.io/gitea/1.14.2/gitea-1.14.2-linux-amd64` - Started with: systemd - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - Log gist: https://gist.github.com/m0rtalis/87f3e1f2b6715ebe4661783f36c65cba I try to debug it more tomorrow. ![Gitea Authenticationsource](https://user-images.githubusercontent.com/20595780/119935949-a8992b80-bf88-11eb-8d16-d51fde83bfc6.png) Edit: Add settings authenticationsource
GiteaMirror commented 2025-11-02 07:16:25 -06:00
Author
Owner
Copy Link

@m0rtalis commented on GitHub (May 28, 2021):

Ok tried reproducing it with the docker image version 1.14.2 which has a completely different behaviour.

In Docker every user account (http://localhost:3000/admin/users) is created as soon as I refresh the external users. In my binary installation on the docker the user account ist created only when the user actually logs in.
Not sure why though. In http://localhost:3000/admin/config the string Gitea-Version is:
binary: "1.14.2 built with GNU Make 4.1, go1.16.4 : bindata, sqlite, sqlite_unlock_notify"
docker: "1.14.2 built with GNU Make 4.3, go1.16.4 : bindata, timetzdata, sqlite, sqlite_unlock_notify"

Not sure if that makes a difference. Where can I find the commit ref, gitea was build with maybe they are different?

Will update this when I find more.

@m0rtalis commented on GitHub (May 28, 2021): Ok tried reproducing it with the docker image version 1.14.2 which has a completely different behaviour. In Docker every user account (http://localhost:3000/admin/users) is created as soon as I refresh the external users. In my binary installation on the docker the user account ist created only when the user actually logs in. Not sure why though. In http://localhost:3000/admin/config the string Gitea-Version is: binary: "1.14.2 built with GNU Make 4.1, go1.16.4 : bindata, sqlite, sqlite_unlock_notify" docker: "1.14.2 built with GNU Make 4.3, go1.16.4 : bindata, timetzdata, sqlite, sqlite_unlock_notify" Not sure if that makes a difference. Where can I find the commit ref, gitea was build with maybe they are different? Will update this when I find more.
GiteaMirror commented 2025-11-02 07:16:25 -06:00
Author
Owner
Copy Link

@m0rtalis commented on GitHub (May 31, 2021):

Ok found a workaround, at least on a fresh installation.

Set the authentication source and then go to monitoring -> Sync external user data, which should import all users into Gitea, as explained above with the docker version. Then those are not going to get deactivated on a new sync.

Which means best bet to reproduce the issue is setting the auth source, login with one of the allowed user and wait 24h (or try manual syncing) which should deactivate the user again. If after the sync all users from ldap are in gitea the bug was not reproduced.

@lafriks Could be interesting in relation to #7949

@m0rtalis commented on GitHub (May 31, 2021): Ok found a workaround, at least on a fresh installation. Set the authentication source and then go to monitoring -> Sync external user data, which should import all users into Gitea, as explained above with the docker version. Then those are not going to get deactivated on a new sync. Which means best bet to reproduce the issue is setting the auth source, login with one of the allowed user and wait 24h (or try manual syncing) which should deactivate the user again. If after the sync all users from ldap are in gitea the bug was not reproduced. @lafriks Could be interesting in relation to #7949
GiteaMirror commented 2025-11-02 07:16:25 -06:00
Author
Owner
Copy Link

@Samachi commented on GitHub (May 31, 2024):

1.21.4, 1.22.0, the bug is still exists

@Samachi commented on GitHub (May 31, 2024): 1.21.4, 1.22.0, the bug is still exists
GiteaMirror commented 2025-11-02 07:16:25 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 31, 2024):

I can't really replicate this problem, even with multiple auth sources using MS AD I have no such behavior. Could be that this is because username field is not set? This is only thing I can think of

@lafriks commented on GitHub (May 31, 2024): I can't really replicate this problem, even with multiple auth sources using MS AD I have no such behavior. Could be that this is because username field is not set? This is only thing I can think of
GiteaMirror commented 2025-11-02 07:16:26 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Jul 1, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jul 1, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
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/needs-feedback topic/authentication
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#7126
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?