Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
SSSD provides the ability to set a filter as part of the LDAP search bases. This is often used to speed up logins and user and group lookups in large AD environments where the Linux clients only care about a subset of groups anyway.
But it is not obvious for many admins that the group filter must also include the primary group, otherwise the user lookups on the clients will fail completely, because the client requires that all the groups, including the primary one are resolvable.
We should make this requirement more visible. Possible options include:
- fail the user resolution completely if the primary group can't be resolved and log a very loud debug message. The failure to resolve the user would force the admin to go look at the logs and find the message with the hint why the user can't be resolved
- autogenerate some funky name for the primary group that can't be resolved. This might work better out of the box, but might break HBAC