#750 attributes aren't being deleted from cache
Closed: Fixed None Opened 13 years ago by ossman.

Spawned off ticket #672:

It seems sssd doesn't notice attributes being deleted, so an expired account that gets the expiration removed doesn't result in sssd letting the user in.

(Workaround is to set the expiration to something <= 0, but it seems that there is no good consensus on a value meaning "no expiration", meaning such an ldap setting might cause a fuss with other LDAP clients.)

I've verified using ldbsearch that the attribute is indeed still there. I also see dataExpireTimestamp updating, so it isn't fiddling with the cache.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.1
owner: somebody => sgallagh
priority: major => blocker

Fields changed

component: SSSD => SysDB

Fields changed

status: new => assigned
upgrade: => 0

Fixed by c625728

resolution: => fixed
status: assigned => closed

Works like a charm now. Thanks. :)

Fields changed

rhbz: => 0

Metadata Update from @ossman:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.5.1

7 years ago

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/1792

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata