Steps to reproduce.
Set up a domain (DOMAIN) with an LDAP provider (it may also occur with proxy, but I did not test this)
Clear the cache file ({{{rm -f /var/lib/sss/db/cache_DOMAIN.ldb}}}) and start the sssd.
First, verify the clean state:
ldbsearch -H /var/lib/sss/db/cache_DOMAIN.ldb "objectclass=user"
This should return nothing.
Next do a user lookup.
getent passwd user1@DOMAIN
Now look at the user entry in the cache.
You should see the user entry, but no lastUpdate attribute.
Run the above {{{getent}}} command again, then {{{ldbsearch}}} again, and you will see the lastUpdate attribute.
ok I see where's the problem.
Fixed in: 5efef2a52ae0e07239942faa7b81c6b62a7be49d
resolution: => fixed status: new => closed
Fields changed
fixedin: => 1.0.0rc
tests: 1 => 0 testsupdated: 0 => 1
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to simo - Issue set to the milestone: SSSD 1.0
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/1301
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.