SSSD / sssd

#3381 Per-subdomain LDAP filter is not applied for subsequent subdomains
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

Even with the fix from https://github.com/SSSD/sssd/pull/233, it appears that putting a filter into subdomain sections of sssd.conf running on an IPA server with a trust against an AD domain only has an effect for the first domain in the list.

After some investigation it looks like https://github.com/SSSD/sssd/pull/233 helps partially because the base is initially set correctly, but we must reset it in some subsequent call.

For the first domain, creating and using the filter works fine.

Why do we have this ticket? https://github.com/SSSD/sssd/pull/233 has not been merged yet. So the fix is not complete.
Edited by lslebodn

Metadata Update from @lslebodn:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Because it's not caused by that PR (I just thought that PR might help) and there are users running RHEL-7.4 bits that are hitting the issue, so I filed a ticket to let them know about the progress.

Metadata Update from @jhrozek:
- Issue status updated to: Open (was: Closed)

OK, but in future try to be more verbose in ticket description or at leas provide more details about but. It was really confusing.

https://docs.pagure.org/sssd-test2/Reporting_sssd_bugs.html
:-) :-) :-)

Hi Jakub,

What do you mean by the "first domain"? The scenario that I tested with PR 233 was forest root + child domain. Both were working with the patch (I could set the search base for both). What was the scenario that did not wotk for you? Do you have more child domains?

Yes, I do. I have:

[domain/ipa.test/win.trust.test]
ldap_group_search_base = CN=Users,DC=win,DC=trust,DC=test?sub?(samaccountname=foo)

[domain/ipa.test/child.win.trust.test]
ldap_group_search_base = CN=Users,dc=child,DC=win,DC=trust,DC=test?sub?(samaccountname=foo)

But the filter only works in the first domain. After applying PR #233 from github, I see the filter is first set, but then when the search is issued, I don't see the filter being there anymore.

We spent some time with Michal debugging this bug interactively and now know where the issue is, therefore I'm filing it into the 1.15.3 release.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.3

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue priority set to: critical
  • master: 21f3d6124ea28218d02e1e345d38e2b948e4ec23

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @lslebodn:
- Custom field version adjusted to 1.15.1

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/4409

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
Low
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.