URL:
https://github.com/SSSD/sssd/pull/259
Title: #259: RESPONDER: Also populate cr_domains when initializing the responders
sumit-bose commented:
"""
Thank you, the patch improves the situation (no DBus error returned) and works reliable
for the configured domain.
But if I run a test where SSSD is not running before and the cache is empty results from
sub-domains are not returned:
[root@f25 ~]# date; dbus-send --system --print-reply
--dest=org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe/Users
org.freedesktop.sssd.infopipe.Users.ListByName string:"tu*" uint32:10
Mi 3. Mai 09:47:18 CEST 2017
method return time=1493797638.880557 sender=:1.2086 -> destination=:1.2085 serial=5
reply_serial=2
array [
]
[root@f25 ~]# date; dbus-send --system --print-reply
--dest=org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe/Users
org.freedesktop.sssd.infopipe.Users.ListByName string:"tu*" uint32:10
Mi 3. Mai 09:47:20 CEST 2017
method return time=1493797640.727085 sender=:1.2086 -> destination=:1.2087 serial=7
reply_serial=2
array [
object path
"/org/freedesktop/sssd/infopipe/Users/ad_2edevel/1367201104"
object path
"/org/freedesktop/sssd/infopipe/Users/ad_2edevel/1367201105"
]
(ad.devel is a sub-domain in my setup)
Iirc, in other responders we make sure a subdomain request is send to the backend before
the first request is handled. Maybe something similar is needed here as well.
"""
See the full comment at
https://github.com/SSSD/sssd/pull/259#issuecomment-298844280