#1520 [RFE] Allow explicietely removing user from the SSSD cache
Closed: Invalid None Opened 11 years ago by dpal.

There is a way to expire users in the cache but not to remove them. This means that if the system is offline the user can still log in indefinitely. This is a corner case but still can happen and might be a security issue.

The problem was discussed on the sssd list and a solution was proposed to allow removing users from the cache.

https://lists.fedorahosted.org/pipermail/sssd-users/2012-September/000178.html

May be just having a special new switch that would allow removing user from SSSD cache. It should also remove user from the fast cache.


I would prefer if the SSSD never completely deleted the cached entry (unless an online lookup returned that it had been deleted). However, it would probably be beneficial to offer a flag to specify "delete cached credentials".

This way, the user's ID and group information would remain available while offline in case it was needed, but the user will not be able to log in.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.0
rhbz: => todo

Fields changed

cc: => myllynen@redhat.com

Fields changed

milestone: SSSD 1.10.0 => SSSD 1.10 beta

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 1

Fields changed

cc: myllynen@redhat.com => myllynen@redhat.com, dstoykov@uni-ruse.bg
changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
review: => 0

We already provide a way to remove cached credentials. This ticket is invalid.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: minor => trivial

Mass-moving tickets not planned for any immediate release and re-setting priority.

milestone: SSSD 1.13 backlog => SSSD Deferred
priority: trivial => major

The cleanup task can do this for years, we should close this ticket.

review: 0 => 1
sensitive: => 0

Fields changed

resolution: => worksforme
status: new => closed

Metadata Update from @dpal:
- Issue set to the milestone: SSSD Patches welcome

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

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