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

Add user to organization based on LDAP group membership #873

New Issue
Closed
opened 2025-11-02 03:39:54 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 03:39:54 -06:00
Owner
Copy Link

Originally created by @tobias-- on GitHub (Jul 7, 2017).

  • Gitea version (or commit ref): 1.1.2

Description

It would be nice if users could be automatically added to an organization based on their LDAP group membership (e.g. using the "memberof" attribute).

Originally created by @tobias-- on GitHub (Jul 7, 2017). - Gitea version (or commit ref): 1.1.2 ## Description It would be nice if users could be automatically added to an organization based on their LDAP group membership (e.g. using the "memberof" attribute).
GiteaMirror added the type/featureissue/confirmed labels 2025-11-02 03:39:54 -06:00
GiteaMirror commented 2025-11-02 03:39:55 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Jul 7, 2017):

Something I've wanted for a while. Also for OAuth and SMTP based on domain of email :)

@bkcsoft commented on GitHub (Jul 7, 2017): Something I've wanted for a while. Also for OAuth and SMTP based on domain of email :)
GiteaMirror commented 2025-11-02 03:39:55 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 14, 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 (Feb 14, 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 03:39:55 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 28, 2019):

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

@stale[bot] commented on GitHub (Feb 28, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
GiteaMirror commented 2025-11-02 03:39:56 -06:00
Author
Owner
Copy Link

@TwoTwenty commented on GitHub (Jun 5, 2019):

it would be nice to be able to add them to an organization based on the authentication source.. since gitea supports multiple auth sources/definitions. Both memberof and auth source would be best. These features would help my organization migrate to using gitea as a significant offering.

@TwoTwenty commented on GitHub (Jun 5, 2019): it would be nice to be able to add them to an organization based on the authentication source.. since gitea supports multiple auth sources/definitions. Both memberof and auth source would be best. These features would help my organization migrate to using gitea as a significant offering.
GiteaMirror commented 2025-11-02 03:39:56 -06:00
Author
Owner
Copy Link

@alexattws commented on GitHub (Nov 30, 2019):

We've implemented mapping LDAP groups to teams in (all) organizations (by group/team name) and published it here, if anyone is interested,
https://github.com/tws-inc/gitea-group-sync

@alexattws commented on GitHub (Nov 30, 2019): We've implemented mapping LDAP groups to teams in (all) organizations (by group/team name) and published it here, if anyone is interested, https://github.com/tws-inc/gitea-group-sync
GiteaMirror commented 2025-11-02 03:39:56 -06:00
Author
Owner
Copy Link

@pbodnar commented on GitHub (Feb 29, 2020):

Duplicate of #1395? Lets vote for this feature there...

@pbodnar commented on GitHub (Feb 29, 2020): Duplicate of #1395? Lets vote for this feature there...
GiteaMirror commented 2025-11-02 03:39:56 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 14, 2022):

Should be fixed with 832ce406ae.

@silverwind commented on GitHub (Feb 14, 2022): Should be fixed with https://github.com/go-gitea/gitea/commit/832ce406aefed0cceb30d42d1435f425a9aba279.
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/confirmed type/feature
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#873
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?