Currently, when AD backend is used, Domain Users (or any primary group of a user for that matter) is explicitly added as memberof of a user being added. In large environments, where everyone is a member of Domain Users, this can trash the memberof plugin.
We could add the group on the frontend side instead, special casing the Domain Users.
The frontend would also have to know when the domain is AD in order to not add any generic LDAP group that would be named Domain Users.
The Domain Users group could just carry a special flag in order to avoid leaking info which domain is AD and which is not.
Not every user has to be a member of 'Domain Users' the membership can be removed if the user has a different primary group.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1028049
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1028049 1028049]
Moving to 1.11.3 as per this week's SSSD meeting.
milestone: NEEDS_TRIAGE => SSSD 1.11.3
Moving tickets that didn't make 1.11.3 to 1.11.4
milestone: SSSD 1.11.3 => SSSD 1.11.4
I think we should close this ticket as won't-fix and think about either improving or removing the memberof plugin. Besides comment:2 we might also run into issues with group-nesting if the primary group of the user is handled special.
Fields changed
milestone: SSSD 1.11.4 => NEEDS_TRIAGE
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
mark: => 0
milestone: SSSD 1.13 beta => SSSD 1.13 backlog priority: major => trivial
Replying to [comment:6 sbose]:
OK, closing.
resolution: => wontfix status: new => closed
Mass-moving tickets not planned for any immediate release and re-setting priority.
milestone: SSSD 1.13 backlog => SSSD Deferred priority: trivial => major
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
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/3182
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.