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 873143

Summary: Unable to lookup groups with use_fully_qualified_names=true
Product: Red Hat Enterprise Linux 6 Reporter: Kaushik Banerjee <kbanerje>
Component: sssdAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED DUPLICATE QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: grajaiya, jgalipea, pbrezina
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Regression
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-06 13:49:49 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:
Attachments:
Description Flags
sssd_LDAP.log while looking up the group none

Description Kaushik Banerjee 2012-11-05 09:05:46 UTC
Created attachment 638427 [details]
sssd_LDAP.log while looking up the group

Description of problem:
Unable to lookup groups with use_fully_qualified_names=true

Version-Release number of selected component (if applicable):
sssd-1.9.2-5.el6

How reproducible:
Always

Steps to Reproduce:
1. Create a user(puser1) and group(Group1) in ldap

2. Configure sssd with the following domain section:
debug_level = 0xFFF0
id_provider = ldap
ldap_uri = ldap://ldapserver
ldap_search_base = dc=example,dc=com
use_fully_qualified_names = TRUE

3. Lookup the user:
# getent passwd puser1@LDAP
puser1@LDAP:*:2001:2001:Posix User1:/home/puser1:

4. Lookup the group:
# getent group Group1@LDAP
# echo $?
2

Actual results:
Fails to return the group

Expected results:
Group lookup should work

Additional info:

Comment 2 Jakub Hrozek 2012-11-05 10:20:32 UTC
I suspect it is the same root cause as https://bugzilla.redhat.com/show_bug.cgi?id=871576. I will build packages for Kaushik today so that he can test.

Comment 3 Jakub Hrozek 2012-11-06 10:53:09 UTC
Kaushik, I just built a new version that also includes a fix for https://bugzilla.redhat.com/show_bug.cgi?id=871576

Can you test it out and if this case works for you, mark this bug as a duplicate of #871576 ?

Comment 4 Kaushik Banerjee 2012-11-06 13:49:49 UTC
Able to lookup users and groups with fully qualified names with sssd-1.9.2-6.

# getent group Group1@LDAP
Group1@LDAP:*:2001:puser1@LDAP

#  getent passwd puser1@LDAP
puser1@LDAP:*:2001:2001:Posix User1:/home/puser1:

Marking this bug as a dupe of bug 871576

*** This bug has been marked as a duplicate of bug 871576 ***