Red Hat Bugzilla – Bug 870505
sss_cache: Multiple domains not handled properly
Last modified: 2013-06-05 13:17:22 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/sssd/ticket/1608 If no objects for deletion were found in the currently searched sysdb database/domain, the other sysdb databases/domains were not searched at all. How to reproduce: 1. configure sssd with two or more domains 2. get info about user/group that is not in the first domain (e.g. getent passwd user1@domain2.com) 3. remove the entry from cache using sss_cache tool (e.g. sss_cache -u user1) Results: sss_cache does not find the entry in the first domain and exits. Expected result: sss_cache should remove the entry from domain2 properly
Verified the BZ on SSSD version: sssd-1.9.2-27.el6 As part of testing, multiple domains LDAP1 and LDAP2 were setup in the sssd.conf file. sss_cache cmd was executed against the cached user from domain LDAP2 and as expected, the user got invalidated. # sss_cache -u ssc_tempuser1 No such user named ssc_tempuser1 in domain LDAP1, skipping # ldbsearch -H /var/lib/sss/db/cache_LDAP2.ldb name=ssc_tempuser1 dataExpireTimestamp asq: Unable to register control with rootdse! # record 1 dn: name=ssc_tempuser1,cn=users,cn=LDAP2,cn=sysdb dataExpireTimestamp: 1 # returned 1 records # 1 entries # 0 referrals
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0508.html