Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support group and teams #257

Open
aymanbagabas opened this issue May 3, 2023 · 3 comments · May be fixed by #443
Open

feat: support group and teams #257

aymanbagabas opened this issue May 3, 2023 · 3 comments · May be fixed by #443

Comments

@aymanbagabas
Copy link
Member

Describe the solution you'd like
Add support for group and team based ACLs

Be able to specify repo ACLs for teams and users. Set the default to read-write for new repositories and read-only for public repositories.

Similar to what Gitolite ACLs offer but using SSH instead. Perhaps support importing Gitolite conf syntax

@jon4hz
Copy link

jon4hz commented May 5, 2023

Support for groups and teams is an amazing idea!

If you're already touching the authentication / authorization parts of soft-serve, what do you think about adding support for ldap auth, too?

@aymanbagabas
Copy link
Member Author

Hey @jon4hz! That's a fond idea. Soft Serve now can support new backends as long as they implement the interface. The idea I have in mind is to implement different backends as Go plugins.

This is still in the works and the API is subject to change. I would love to hear your thoughts on this 🙂

@jon4hz
Copy link

jon4hz commented May 19, 2023

Hi, sorry for getting back so late. To be honest, I never implemented ldap as backend myself so I'm not sure what the obstacles are. However I did self host gitlab for a short time and I think they are provisioning the ldap users in the same db as the "normal" users.

@aymanbagabas aymanbagabas linked a pull request Dec 11, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants