We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/259
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.
Comment from simo at 2009-11-06 15:08:54
ok I see where's the problem.
Comment from simo at 2009-11-07 18:10:34
Fixed in: 5efef2a
resolution: => fixed status: new => closed
Comment from sgallagh at 2009-11-09 14:45:45
Fields changed
fixedin: => 1.0.0rc
Comment from jgalipea at 2009-11-11 22:01:17
tests: 1 => 0 testsupdated: 0 => 1
Comment from dpal at 2012-01-19 02:27:43
rhbz: => 0
Comment from sgallagh at 2017-02-24 15:02:56
Metadata Update from @sgallagh:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/259
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:
This should return nothing.
Next do a user lookup.
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.
Comments
Comment from simo at 2009-11-06 15:08:54
ok I see where's the problem.
Comment from simo at 2009-11-07 18:10:34
Fixed in:
5efef2a
resolution: => fixed
status: new => closed
Comment from sgallagh at 2009-11-09 14:45:45
Fields changed
fixedin: => 1.0.0rc
Comment from jgalipea at 2009-11-11 22:01:17
Fields changed
tests: 1 => 0
testsupdated: 0 => 1
Comment from dpal at 2012-01-19 02:27:43
Fields changed
rhbz: => 0
Comment from sgallagh at 2017-02-24 15:02:56
Metadata Update from @sgallagh:
The text was updated successfully, but these errors were encountered: