Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=813059 (Red Hat Enterprise Linux 6)
Description of problem: sss_cache operates only on configured (active) domains in sssd.conf. The inactive domains which were either removed or commented out from sssd.conf and which also exist in the cache are not affected by any of the sss_cache operations. An error message should be returned when sss_cache is executed against the entities in inactive domains. Version-Release number of selected component (if applicable): sssd-1.8.0-22.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a domain, say LDAP1 in sssd.conf and cache a user from that domain. 2. Stop sssd service and remove LDAP1 domain from sssd.conf. 3. Create a new domain, say LDAP2 in sssd.conf and start the sssd service 4. Cache few users from LDAP2 domain as well. Now, this makes LDAP1 domain inactive. 5. Invalidate the user from inactive domain LDAP1 by running the below command: # sss_cache -d LDAP1 -u <user> Actual results: The LDAP1 <user> attributes remain unchanged in the cache and sss_cache returns no error messages. Expected results: sss_cache should return an error message. Additional info:
Fields changed
blockedby: => blocking: => coverity: => feature_milestone: => owner: somebody => jhrozek patch: 0 => 1 status: new => assigned tests: => 0 testsupdated: => 0 upgrade: => 0
Fixed in master: da0b829
I'll leave this ticket in NEEDS_TRIAGE until our weekly meeting so that we can decide whether we want to back port any of the error message related tickets to 1.8.x
milestone: NEEDS_TRIAGE => SSSD 1.9 beta
resolution: => fixed status: assigned => closed
Metadata Update from @dpal: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.9.0 beta 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/2348
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.