Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1153510

Summary: netgroup lookups returned in lowercase with case_sensitive=preserving
Product: Red Hat Enterprise Linux 7 Reporter: Kaushik Banerjee <kbanerje>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED CANTFIX QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: grajaiya, jgalipea, lslebodn, mkosek, mzidek, pbrezina, preichl
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-30 10:23:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kaushik Banerjee 2014-10-16 06:19:01 UTC
Description of problem:
netgroup lookups returned in lowercase with case_sensitive=preserving

Version-Release number of selected component (if applicable):
sssd-1.12.1-3.el7

How reproducible:
Always

Steps to Reproduce:
1. Add the following ldif to ldap server:
dn: cn=NetGroup_CS1,ou=Netgroups,dc=example,dc=com
objectClass: nisNetgroup
cn: NetGroup_CS1_Alias
cn: NetGroup_CS1
nisNetgroupTriple: (Host1.example.com,User1,example.com)

2. Confiure sssd with case_sensitive=false

3. Lookup netgroup
getent netgroup netgroup_cs1


Actual results:
# getent netgroup netgroup_cs1
netgroup_cs1          (Host1.example.com,User1,example.com)

Expected results:
Should not be lowercased.

Additional info:

Comment 2 Jakub Hrozek 2014-10-16 09:02:54 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2459

Comment 3 Michal Zidek 2014-10-23 20:43:12 UTC
Hi,

I looked into this and I see this as NOTABUG. The reason is that we do not control the format of netgroup name in the getnetgr response packet. The packet only contains netgroup triples. The name of netgroup printed on the screen is always in the same case as the name entered by user when invoking getent.

So there is not much we can do about this, preserve and false will always behave the same with netgroups.

Michal

Comment 4 Jakub Hrozek 2014-10-30 10:23:28 UTC
Sorry I confused two bugzillas when asking for the ack.

As Michal said, the netgroup protocol is a bit odd from libc point of view. The case-sensitiveness is only used to select the netgroup with setnetgrent. The name that we print is completely under libc control.

Therefore, I'm closing this bug as CANTFIX.