On Thu, 18 Apr 2013, steve wrote:
Hi
Unfortunately that only works for the first login after the change e.g.
Change uidNumber for steve2
steve2 logs in and id shows his new uid
log out
change the number back to what it was
steve2 logs in again but the uidNumber has not changed
Also, for groups:
sss_cache -g group
does not flush when primaryGroupID has been changed in AD
/var/lib/sss/db/* must be removed for this to happen
Eh? Would you expect to need to clear user not group information to force
primaryGroupID changes to get noticed?
I have workarounds for all this but they involve going to each
client,
logging in as root and either issuing the sss_cache commands or removing
the db and starting again.
Can I just query one thing? Why on earth are you changing user attributes for
users so frequently?
Forget the effect sssd has, you're completely hanging out to dry any running
processes of these users everytime you do this.
jh