Learn more about these different git repos.
Other Git URLs
Stef found this corner case while preparing for the test day. If the SSSD is not running, for instance because the machine has left the domain, the memory cache files are still around and the processes that started before the machine left the domain can still query users from the domain.
The memcache can't even be invalidated with sss_cache, because sss_cache only sends a signal to the NSS responder.
This is how we should fix it:
1. make the API to invalidate the cache public
2. in the sss_cache tool, carefully detect if the sss_nss process is running, for example by checking for the responder socket or the PID.
3. if the sss_nss process is running, proceed with sending the signal
4. if the sss_nss process is not running, invalidate the memcache.
We should also check if all of the above works with SELinux.
milestone: NEEDS_TRIAGE => SSSD 1.9.3
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=867933
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=867933 867933]
owner: somebody => mzidek
design_review: => 0
patch: 0 => 1
status: new => assigned
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.9.3
to comment on this ticket.