RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1185794 - RFE: sss_cache, allow invalidating by UID/GID
Summary: RFE: sss_cache, allow invalidating by UID/GID
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: 7.2
Assignee: SSSD Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-26 10:07 UTC by Janne Blomqvist
Modified: 2020-05-02 17:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-18 15:03:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3610 0 None None None 2020-05-02 17:56:22 UTC

Description Janne Blomqvist 2015-01-26 10:07:43 UTC
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:

Comment 2 Jakub Hrozek 2015-01-26 10:21:45 UTC
Sounds like a reasonable RFE to me, will clone upstream.

Comment 3 Jakub Hrozek 2015-01-26 10:22:29 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2568

Comment 4 Jakub Hrozek 2015-01-30 16:37:50 UTC
Reproposing for 7.2 as this is not critical for upstream.

Comment 5 Jakub Hrozek 2016-01-11 15:29:26 UTC
Makes sense, but not too urgent for 7.3

Comment 6 Jakub Hrozek 2016-11-23 14:24:48 UTC
Thank you for filing this bug report.

Since fixing this bug requires work in the upstream SSSD project which is not scheduled for the immediate future, I added a conditional development nack, pending upstream availability.

Comment 7 Jakub Hrozek 2017-08-08 10:09:58 UTC
Thank you for filing this bug report.

Since fixing this bug requires work in the upstream SSSD project which is not scheduled for the immediate future, I added a conditional development nack for RHEL-7.5, pending upstream availability.

Comment 8 Jakub Hrozek 2018-04-18 15:03:41 UTC
We don't have plans to address this issue in RHEL in the immediate future. Therefore I'm closing this request with the UPSTREAM resolution.

Please reopen if you disagree.


Note You need to log in before you can comment on or make changes to this bug.