#2568 RFE: sss_cache, allow invalidating by UID/GID
Closed: wontfix 8 months ago by pbrezina. Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1185794

Description of problem:

Currently sss_cache -u -g options expect a user or group name. It would be nice
if one could additionally use a UID or GID. Say, if the argument is an integer,
invalidate by UID/GID, otherwise by name.

Version-Release number of selected component (if applicable):

1.11.6

How reproducible:

Always.

Steps to Reproduce:
1. sss_cache -g some_gid

Actual results:

Output of command:
No cache object matched the specified search

Expected results:

Group with GID some_gid removed from the cache.

Additional info:

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => preichl
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

keywords: => easyfix
milestone: NEEDS_TRIAGE => SSSD 1.14 beta

Fields changed

priority: major => trivial
sensitive: => 0

This ticket is not important enough to make the 1.14 release. In the meantime, patches are welcome.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD Future releases (no date set yet)

3 years ago

Metadata Update from @jhrozek:
- Assignee reset
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: easyfix

3 years ago

Metadata Update from @thalman:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: Canditate to close

8 months ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

8 months 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/3610

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