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 1884688 - cn=views,cn=compat group lookup failure
Summary: cn=views,cn=compat group lookup failure
Keywords:
Status: CLOSED DUPLICATE of bug 1984010
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: slapi-nis
Version: ---
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Alexander Bokovoy
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-02 16:31 UTC by aheverle
Modified: 2022-08-19 15:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-19 15:44:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-6874 0 None None None 2021-09-21 18:16:11 UTC

Description aheverle 2020-10-02 16:31:33 UTC 
Description of problem:
Given: A view exists for an enrolled host. Within the view, the primary GID for a user is overridden. A group with the GID chosen as the override value does exist in IdM.

Observed behavior: When executing an LDAP query against the cn=compat tree with a view applied (e.g., cn=groups,cn=some_view_name,cn=views,cn=compat,...), a search for the overridden GID number within the cn=groups branch returns nothing.

Version-Release number of selected component (if applicable):
slapi-nis-0.56.0-13.el7.x86_64

How reproducible:
Every time

Steps to Reproduce:

A computer is enrolled in the IdM domain and is therefore an IdM client.

Domain: 
ipa.example.com

Client: 
client01.ipa.example.com



The computer is not running an OS where SSSD is supported, so direct LDAP interaction is required. (It's AIX.)

The view "view_client01.ipa.example.com" is applied to the IdM client "client01.ipa.example.com".

The IdM client OS expects an RFC2307-compliant schema, so LDAP lookups need to use the "cn=compat" branch.

The configured bind DN for these LDAP lookups is further constrained to the view for that particular computer, e.g. for users:

cn=users,cn=view_client01.ipa.example.com,cn=views,cn=compat,dc=ipa,dc=example,dc=com

The view overrides the primary GID (LDAP attribute gidNumber) for a user. The group corresponding to the override GID number does exist outside of the view. E.g.:

Group unixops exists with GID 300511.

Group unixadm exists with GID 12299.

User test_user exists with primary GID 300511.

View view_client01.ipa.example.com overrides the primary GID for test_user to 
12299 on client client01.ipa.example.com.


Subsequent LDAP searches for the group with GID 12299 from client01.ipa.example.com will fail to find the group.

Subsequent LDAP searches for a user with primary GID 12299 from client01.ipa.example.com will only find the user with the overridden GID (
test_user), and will not return other non-overridden users having primary GID 
12299.

RHEL clients using SSSD (which performs client-side application of ID Views) do not exhibit these failures.  Server-side application of ID Views under cn=compat should behave the same. The manual does not give any indication that views under cn=compat should behave differently.
Comment 7 Petr Čech 2021-02-19 12:33:25 UTC 
Thank you taking your time and submitting this request for Red Hat Enterprise Linux 7.
Red Hat Enterprise Linux 7 is in Maintenance Support 2 Phase. This bug was reevaluated and will be postponed to RHEL 8.
Thank you for understanding.
Red Hat Enterprise Linux Identity Management Team
Note You need to log in before you can comment on or make changes to this bug.