On Fri, Jul 10, 2020 at 09:26:46AM -0400, Lawrence Kearney wrote: > Hello and I hope all is well for everyone and everyone is staying healthy. > > The issue being experienced is actually a bug in another application being > resolved by turning enumeration on. Specifically some versions of SLURM. > > https://bugs.schedmd.com/show_bug.cgi?id=9318 > https://bugs.schedmd.com/show_bug.cgi?id=9374 > > The job owner on the compute does end up going to "nobody" and turning > enumeration on does resolve it. Obviously the solution is for the SLURM > developers to fix the bug. In the interim I wanted to know if there was a > way to control the scope of enumeration for the SSSD. I'm assuming the > search base used is irrelevant in the context of enumeration.
Hi, no, ldap_user_search_base and ldap_group_search_base should be respected. Please have a look at the sssd-ldap man page where it is explained how you can even add extra filters to the search bases. HTH bye, Sumit > > Thank you to everyone as always, > > > -- lawrence > _______________________________________________ > sssd-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/[email protected] _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected]
