mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #702] [Feature Request] sudoers support #252
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#252
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @SingingFrog7 on GitHub (Oct 8, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/702
Hey guys,
Is there any plan to support sudoers in the future?
I'd be migrating from my current LDAP server if it was supported as I use it to give sudo access to users on all my vms and containers
Thanks
@nitnelave commented on GitHub (Oct 8, 2023):
Hi! I had a look at the sudoers LDAP configuration, and it seems that it won't be compatible with LLDAP's simple structure of just groups and users.
However, once #67 is implemented, we'll have support for PAM authentication so you can assign Unix groups with LDAP. If you configure your sudoers the old fashioned way (with visudo) based on groups, you can then assign permissions to people by adding them to LLDAP's groups.
@SingingFrog7 commented on GitHub (Oct 13, 2023):
Hello,
Sorry for my late reply and thanks for looking at it. It definitively could work for me, in fact I tried to switch from OpenLDAP to different other LDAP servers and I always came back to OpenLDAP because I use the sudoers (which I could change to having a sudoer group but I would have to add that group to all machines, which is doable) and I also use Samba, which I know is another complicated beast
I'll keep an eye on #67 and test it in my environment once it's implemented
Thanks for your time!