Forwarding to freeipa-users who have more knowledge on SSSD
-------- Forwarded Message --------
Subject: [389-users] How to invalidate local cache after user changed
their password
Date: Wed, 27 Feb 2019 19:22:19 +0000 (UTC)
From: xinhuan zheng <xhzheng2001(a)yahoo.com>
Reply-To: General discussion list for the 389 Directory server project.
<389-users(a)lists.fedoraproject.org>
To: 389-users(a)lists.fedoraproject.org
Hello,
I have been struggling with this problem for a while. When a user
changed their password, our 389 directory servers received new password
and saved into directory server. However, when user tries to login to a
server whose authentication is using 389 directory server, their new
password won't work for the first few minutes. There is a local cache
process, sssd, running on the server the user tries to login. Apparently
sssd is still using old password information, and does not know password
has changed on directory servers. I have set sssd to keep cache
information for 5 minutes only, and do pre-fetch prior to cache
information expiring. But I don't know how to tell sssd to ignore cache
completely when information has changed on 389 directory server side.
Is there a way to completely disable sssd local cache, and only use it
when 389 directory servers are not available?
Thank you,
- Xinhuan