Hide Forgot
Description of problem: The SSSCTL utility should act like other unix commands like (id, getent) and should not be case sensitive when searching for userids and groups in the cache. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Setup SSSD against AD, (realm join $domain) 2. Edit sssd.conf to contain ifp 3. Login as user that contains lower case and upper case characters or a group, i.e. "Domain Users" 4. Use SSSCTL to search for the user in the cache Actual results: [root@ibm-dx360m4-01 ~]# sssctl group-show "domain users" Group domain users is not present in cache. Expected results: [root@ibm-dx360m4-01 ~]# sssctl group-show "domain users" Name: Domain Users Cache entry creation date: 09/28/16 19:03:34 Cache entry last update time: 09/28/16 19:03:34 Cache entry expiration time: 09/28/16 20:33:34 Cached in InfoPipe: No Additional info: The search currently is case sensitive, searching for "Domain Users" does reply the object in the cache.
Hi Michal, can you take a look, please? Feel free to clone the bug when it's confirmed to be a bug or just close it when it's certain it's not.
Hi, I will take a look at it.
Upstream ticket: https://fedorahosted.org/sssd/ticket/3235
Easy enough, but not too critical. for 7.4. If we have time and there is a patch, we'll include the patch by all means
* 35ecfab87a24031e55798b22975e02832ee0f2ad * 715abb607540945cc82355e94712da7ac9746a67 * d6e875c49d6be650a03fc14f00a680734b23ef66 * 867bb85ecc8117aa8bdde9add0df8857cf87236e
Verified against sssd-1.15.2-33.el7.x86_64 [root@beast ~]# sssctl group-show "domain users" Name: domain users Cache entry creation date: 05/31/17 16:54:53 Cache entry last update time: 05/31/17 16:54:53 Cache entry expiration time: 05/31/17 18:24:53 Cached in InfoPipe: No
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2294