Closed jagga13 closed 11 months ago
I feel this is being caused due to the 'domain users' group coming from AD. Is there a way for me to ignore this group explicitly from my sssd.conf. Maybe in the ldap_group_search_base? Is there a way to update the following and add a not group domain users filter:
ldap_group_search_base = OU=Groups,OU=T2-Groups,OU=Tier2,OU=xxx,OU=xxx,DC=xxx,DC=com?subtree?(&(objectclass=group)(cn=*CloudHPC*))
Thanks!
I have seen identical errors after upgrading to 2.7.0 from 2.5.2. The issue exists in 2.6.3 as well. What version of sssd are you using? I haven't filed a bug report yet.
Can you try using the ad provider instead of ldap, ie *_provider=ad? It would simplify the configuration a lot and most probably resolve your issue.
Dear Contributor/User,
Recognizing the importance of addressing enhancements, bugs, and issues for the SSSD project's quality and reliability, we also need to consider our long-term goals and resource constraints.
After thoughtful consideration, regrettably, we are unable to address this request at this time. To avoid any misconception, we're closing it; however, we encourage continued collaboration and contributions from anyone interested.
We apologize for any inconvenience and appreciate your understanding of our resource limitations. While you're welcome to open a new issue (or reopen this one), immediate attention may not be guaranteed due to competing priorities.
Thank you once again for sharing your feedback. We look forward to ongoing collaboration to deliver the best possible solutions, supporting in any way we can.
Best regards, André Boscatto
Hello,
I have implemented sssd to integrate with our AD/LDAP instance to authorize users/groups on a linux system. It seems to have worked for the most part but when running the groups or id command, I see a rouge group id that is not resolvable via AD:
The 2100513 group is not coming from AD and not sure where locally it might be coming from. I have rm'd /var/lib/ss/db/* and did a sss_cache -E and restarted sssd but this issue still exists. Any help would be greatly appreciated. Here is my sssd.conf:
Thanks