Bug 1118670 - Trusted AD users are not resovable in netgroups
Summary: Trusted AD users are not resovable in netgroups
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-11 08:52 UTC by Steeve Goveas
Modified: 2018-12-05 19:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-12-05 19:57:16 UTC

Attachments (Terms of Use)

Description Steeve Goveas 2014-07-11 08:52:54 UTC
Description of problem:
AD uesrs in posix group, added to a netgroup are not resolvable in that netgroup

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Add Trust with an AD server

2. Create an external group and add AD users to that group
# ipa group-add adusers_ext --external
# ipa group-add-member adusers_ext --external=aduser1@adtest.qe,aduser1@pune.adtest.qe

3. Create a Posix groups and add external group as member
# ipa group-add adusers_grp --desc "internal grp"
# ipa group-add-member adusers_grp --groups=adusers_ext

4. Create a netgroup and add the posix group as member
# ipa netgroup-add ng001 --desc="testing ng"
# ipa netgroup-add-member --group=adusers_grp ng001

5. Add a ipa user as a memeber of the netgroup
# ipa netgroup-add-member --user=ipahttpuser1 ng001

6. Do getent for that netgroup
# service sssd stop; rm -rf /var/lib/sss/{db,mc}/*; service sssd start
Redirecting to /bin/systemctl stop  sssd.service
Redirecting to /bin/systemctl start  sssd.service
# getent netgroup ng001
ng001                 (-,ipahttpuser1,steeve06171722.test)

Actual results:
AD users are not resolved when getent netgroup is rung. IPA user is resovled.
[root@hp-ms-01-c40 ~]# getent netgroup ng001
ng001                 (-,ipahttpuser1,steeve06171722.test)

Expected results:
AD users should also be resolved

Additional info:

Comment 2 Dmitri Pal 2014-07-11 18:56:04 UTC
Upstream ticket:

Comment 7 Rob Crittenden 2018-12-05 19:57:16 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.

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