Skip to content
New issue

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

The first saving of a user to the cache does not set lastUpdate #1301

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

The first saving of a user to the cache does not set lastUpdate #1301

sssd-bot opened this issue May 2, 2020 · 0 comments
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/259

  • Created at 2009-11-06 14:58:27 by sgallagh
  • Closed as Fixed
  • Assigned to simo

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.

ldbsearch -H /var/lib/sss/db/cache_DOMAIN.ldb "objectclass=user"

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:

  • Issue assigned to simo
  • Issue set to the milestone: SSSD 1.0
@sssd-bot sssd-bot added the Closed: Fixed Issue was closed as fixed. label May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

1 participant