Organization/Team membership for new users #3462

New Issue

GiteaMirror · 2025-11-02T05:13:32-06:00

GiteaMirror commented

2025-11-02 05:13:32 -06:00

Originally created by @stertingen on GitHub (Jun 13, 2019).

Gitea version (or commit ref): 1.8.2
Git version: 2.20.1
Operating system: Docker on Debian
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

I'm using Gitea for a pretty small organization (20-30 members, but continuously changing) with LDAP (simple auth) login. When a new user logs in for the first time, I want them to have full access to all repositories owned by a organization ('MyOrga').

Is there a way to add any user to a team (for example 'Developers' in organization 'MyOrga') on first login?

(Alternative, more general approach: Map LDAP groups to teams in organizations. This would be nice to grant extra permissions based on the LDAP group; a default team membership would be realized using a filter returning true. Already proposed: https://github.com/go-gitea/gitea/issues/2121, https://github.com/go-gitea/gitea/issues/2212)

Originally created by @stertingen on GitHub (Jun 13, 2019).   - Gitea version (or commit ref): 1.8.2 - Git version: 2.20.1 - Operating system: Docker on Debian - 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: ## Description I'm using Gitea for a pretty small organization (20-30 members, but continuously changing) with LDAP (simple auth) login. When a new user logs in for the first time, I want them to have full access to all repositories owned by a organization ('MyOrga'). Is there a way to add any user to a team (for example 'Developers' in organization 'MyOrga') on first login? (Alternative, more general approach: Map LDAP groups to teams in organizations. This would be nice to grant extra permissions based on the LDAP group; a default team membership would be realized using a filter returning true. Already proposed: https://github.com/go-gitea/gitea/issues/2121, https://github.com/go-gitea/gitea/issues/2212)

GiteaMirror added the issue/duplicate label 2025-11-02 05:13:32 -06:00

GiteaMirror closed this issue

2025-11-02 05:13:32 -06:00

GiteaMirror commented

2025-11-02 05:13:32 -06:00

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

I also need this/these feature/features.

@TwoTwenty commented on GitHub (Jun 24, 2019): I also need this/these feature/features.

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@guillep2k commented on GitHub (Jul 8, 2019):

Yes, a perfect scenario would be for this to be a dynamic feature: gitea could get group membership externaly and there would be a group <---> team relationship on each organization, and users will be added/removed automatically when there are any changes. For unix/linux environments a general solution could be the command "id -Gn user" (there is a -z flag to force the separator to be \0 to support group names with spaces on them); this would be nice because it's just a system configuration and doesn't depend on the technology. For windows, there are other methods (like get-aduser in powershell).

The problem is to generalize this feature to something already supported by gitea (pam, ldap, etc.) and make it consistent. Ideally this could be some kind of plugin or extension linked to the organization.

@guillep2k commented on GitHub (Jul 8, 2019): Yes, a perfect scenario would be for this to be a dynamic feature: gitea could get group membership externaly and there would be a group <---> team relationship on each organization, and users will be added/removed automatically when there are any changes. For unix/linux environments a general solution could be the command "id -Gn user" (there is a -z flag to force the separator to be \0 to support group names with spaces on them); this would be nice because it's just a system configuration and doesn't depend on the technology. For windows, there are other methods (like get-aduser in powershell). The problem is to generalize this feature to something already supported by gitea (pam, ldap, etc.) and make it consistent. Ideally this could be some kind of plugin or extension linked to the organization.

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@guillep2k commented on GitHub (Jul 17, 2019):

Yes, a perfect scenario would be for this to be a dynamic feature: gitea could get group membership externaly and there would be a group <---> team relationship on each organization, and users will be added/removed automatically when there are any changes. For unix/linux environments a general solution could be the command "id -Gn user" (there is a -z flag to force the separator to be \0 to support group names with spaces on them); this would be nice because it's just a system configuration and doesn't depend on the technology. For windows, there are other methods (like get-aduser in powershell).

The problem is to generalize this feature to something already supported by gitea (pam, ldap, etc.) and make it consistent. Ideally this could be some kind of plugin or extension linked to the organization.

Well, digging deeper in the documentation I now realize that we can use the API for such level of customization. Kudos to the Gitea team.

@guillep2k commented on GitHub (Jul 17, 2019): > > > Yes, a perfect scenario would be for this to be a dynamic feature: gitea could get group membership externaly and there would be a group <---> team relationship on each organization, and users will be added/removed automatically when there are any changes. For unix/linux environments a general solution could be the command "id -Gn user" (there is a -z flag to force the separator to be \0 to support group names with spaces on them); this would be nice because it's just a system configuration and doesn't depend on the technology. For windows, there are other methods (like get-aduser in powershell). > > The problem is to generalize this feature to something already supported by gitea (pam, ldap, etc.) and make it consistent. Ideally this could be some kind of plugin or extension linked to the organization. Well, digging deeper in the documentation I now realize that we can use the API for such level of customization. Kudos to the Gitea team.

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@maxguru commented on GitHub (Aug 4, 2019):

I would find this useful too.

@maxguru commented on GitHub (Aug 4, 2019): I would find this useful too.

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@jfint commented on GitHub (Sep 20, 2019):

I would really like for this to stay alive.

@jfint commented on GitHub (Sep 20, 2019): I would really like for this to stay alive.

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@dorbeus commented on GitHub (Sep 25, 2019):

In gitlab this function works like this.
https://youtu.be/HPMjM-14qa8

@dorbeus commented on GitHub (Sep 25, 2019): In gitlab this function works like this. https://youtu.be/HPMjM-14qa8

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@IntelligentesTierMaulApollo13 commented on GitHub (Oct 25, 2019):

Could this enhancement in gogs help here?
gogs/gogs#662

@IntelligentesTierMaulApollo13 commented on GitHub (Oct 25, 2019): Could this enhancement in gogs help here? gogs/gogs#662

GiteaMirror commented

2025-11-02 05:13:33 -06:00

@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 05:13:34 -06:00

@KaiMartin commented on GitHub (Dec 2, 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

We run gitea for about 200 people in a research institute. The ability to map LDAP groups to teams and organizations would reduce day-to-day administration significantly. I will try to adapt your approach to our needs. Will report on the progress - but don't hold your breadth...

@KaiMartin commented on GitHub (Dec 2, 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 We run gitea for about 200 people in a research institute. The ability to map LDAP groups to teams and organizations would reduce day-to-day administration significantly. I will try to adapt your approach to our needs. Will report on the progress - but don't hold your breadth...

GiteaMirror commented

2025-11-02 05:13:34 -06:00

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

Sure, the gitea-group-sync looks promising and easily adaptable approach for any company.
This issue describes de-facto the same requirement as #2121 or even earlier #1395. Close it as a duplicate then?

@pbodnar commented on GitHub (Feb 29, 2020): 1. Sure, the _gitea-group-sync_ looks promising and easily adaptable approach for any company. 2. This issue describes de-facto the same requirement as #2121 or even earlier #1395. Close it as a duplicate then?

GiteaMirror referenced this issue

2025-11-02 12:22:49 -06:00

[PR #3462] [CLOSED] API Endpoint to add a member to an organisation #16950

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3462