Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1399304
Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.
Search filter should not be applied to automountmaps. Search filter should not be applied to automountmaps. They are global (e.g.: 'auto.home') From customers comments: The ldap search filter should not be applied to map entries, but SSSD does apply the filter!. E.g.: There is no benefit to limit maps like 'auto.home'. Search filter should not be applied to automountmaps. They are global (e.g 'auto.home') Filter is applied to automountmap. I am forced to apply "global" value to each automountmap to get over this behavior. SEARCH REQ conn=359 op=1 msgID=2 base="ou=automount,dc=example,dc=com" scope=wholeSubtree filter="(&(&(automountMapName=auto.home)(objectclass=automou ntMap))(|(myfilterattr=global)(myfilterattr=a6789)(myfilterattr=myhost.example.com)) )" attrs="objectClass,automountMapName" SEARCH RES conn=359 op=1 msgID=2 result=0 nentries=1 etime=1
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1399304
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/4503
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.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)