#663 LDAP cleanup task deletes nested groups
Closed: Invalid None Opened 13 years ago by sgallagh.

Currently, the ldap cleanup task checks whether a group has any member users before removing it, but it doesn't take into account the possibility of groups that contain only other groups.


Fields changed

status: new => assigned

This is actually functioning exactly right. We ARE handling nested groups (because of the full memberOf history).

The only place it breaks down is if the group contains a group that has no direct members, only users with that group as their primary GID. But since POSIX can't handle this anyway, there's nothing we can really do about it.

If this group needs to be here, then the sysadmin should just make a direct membership of the user to the child group, and it will percolate back up the chain correctly.

resolution: => worksforme
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.5.0

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1705

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata