Learn more about these different git repos.
Other Git URLs
See https://bugzilla.redhat.com/show_bug.cgi?id=882425. Deleting the user might be beneficial to work around cases the SSSD itself can't deal with such as UID change.
Fields changed
description: See https://bugzilla.redhat.com/show_bug.cgi?id=882425. Deleting the user might be beneficial to work around cases the SSSD itself can't deal with such as UID change.
See also https://bugzilla.redhat.com/show_bug.cgi?id=882425 for a more detailed discussion. => See https://bugzilla.redhat.com/show_bug.cgi?id=882425. Deleting the user might be beneficial to work around cases the SSSD itself can't deal with such as UID change.
Also think about a way to centrally control which users can be removed from cache. This would be useful for the cases when environment is migrating from on UID/GID scheme to another.
milestone: NEEDS_TRIAGE => SSSD 1.12 beta summary: RFE: add a sss_cache option to completely remove the user from cache, not just invalidate => [RFE] add a sss_cache option to completely remove the user from cache, not just invalidate type: defect => enhancement
rhbz: => todo
milestone: SSSD 1.12 beta => SSSD 1.13 beta
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
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/2733
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.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.