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 1318169 - Tree-root domains in a trusted AD forest aren't marked as reachable via the forest root
Summary: Tree-root domains in a trusted AD forest aren't marked as reachable via the f...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Alexander Bokovoy
QA Contact: Kaleem
Aneta Šteflová Petrová
URL:
Whiteboard:
Depends On: 1375269
Blocks: 1366991 1369103
TreeView+ depends on / blocked
 
Reported: 2016-03-16 08:32 UTC by Sudhir Menon
Modified: 2016-11-04 05:52 UTC (History)
7 users (show)

Fixed In Version: ipa-4.4.0-9.el7
Doc Type: Bug Fix
Doc Text:
Tree-root domains in a trusted AD forest are now marked as reachable through the forest root When an Active Directory (AD) forest contained tree-root domains (a separate DNS domain), Identity Management (IdM) sometimes failed to correctly route authentication requests to the tree-root domain's domain controllers. Consequently, users from a tree-root domain failed to authenticate against services hosted in IdM. This update fixes the bug, and users from a tree-root domain can authenticate as expected in this situation.
Clone Of:
: 1369103 (view as bug list)
Environment:
Last Closed: 2016-11-04 05:52:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
trust console log (6.46 KB, text/plain)
2016-03-16 08:32 UTC, Sudhir Menon 		no flags Details
idrange-sssd logs (23.55 KB, text/plain)
2016-03-16 08:33 UTC, Sudhir Menon 		no flags Details
error log (185.65 KB, text/plain)
2016-09-12 13:57 UTC, Sudhir Menon 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Sudhir Menon 2016-03-16 08:32:15 UTC 
Created attachment 1136927 [details]
trust console log

Description of problem: Tree-root domains in a trusted AD forest aren't marked as reachable via the forest root


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

[root@host2 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.2 (Maipo)

ipa-server-dns-4.2.0-15.el7_2.10.x86_64
ipa-server-trust-ad-4.2.0-15.el7_2.10.x86_64
ipa-server-4.2.0-15.el7_2.10.x86_64
sssd-1.13.0-40.el7_2.2.x86_64

How reproducible:Always

Steps to Reproduce:
1. Setup forest  i.e pne.qe
2. Setup child domain i.e chd.pne.qe
3. Setup a tree domain i.e test.qa
4. Installed IPA. ipa-adtrust-install
5. Setup two-way trust
6. Ensure child domain and tree-root domain is listed.
7. run id <username@tree-rootdomain> on IPA server

Actual results:
"id <username>" when executed on IPA server/client doesn't display users 
present in the tree domain.

[root@host2 ~]# id user5
id: user5: no such user
[root@host2 ~]# id user6
id: user6: no such user

Expected results:
id <username> output should display users present in the tree domain as well.

Additional info:
Attaching the console logs and sssd logs.
Comment 1 Sudhir Menon 2016-03-16 08:33:43 UTC 
Created attachment 1136929 [details]
idrange-sssd logs
Comment 3 Alexander Bokovoy 2016-03-16 09:12:52 UTC 
When analyzing trust topology we fill in ipanttrustpartner value to point to the forest root. Unfortunately, the code actually uses the domain's name, not the forest root domain's name here. It works fine with child domains but doesn't work for tree-root domains within the forest. A fix would be a one-line to change how ipanttrustpartner is filled in. ipaNTTrustPartner value is then used by SSSD in IPA server mode to identify which Kerberos principal to use to talk to the trusted domain's DC.
Comment 6 Petr Vobornik 2016-03-16 09:49:00 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5738
Comment 8 Martin Babinsky 2016-08-22 12:06:27 UTC 
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/62be554540e83e54c8cc06ebc2cb1253c2cebeca
https://fedorahosted.org/freeipa/changeset/a14ebbea895a20f5a68052e32ba65c4fd7fdf670

ipa-4-2:
https://fedorahosted.org/freeipa/changeset/0dfd5704e3e9c744e3a5fbf0d7ec5acf560bb371
https://fedorahosted.org/freeipa/changeset/ac6248430ce3358e75e6eebf01db5b9dfc55cac0
Comment 14 Sudhir Menon 2016-09-09 13:41:13 UTC 
Tree root domain is not listed even after having two-way trust established.
only child domains are listed.
Tried ipa trust-domain-find command as well, which says no trust

Verified on RHEL73 using
ipa-server-4.4.0-10.el7.x86_64
ipa-server-trust-ad-4.4.0-10.el7.x86_64
sssd-1.14.0-36.el7.x86_64


[root@master ~]# ipa trust-add --two-way=true
Realm name: pne.qe
Active Directory domain administrator: Administrator
Active Directory domain administrator's password: 
-----------------------------------------------
Added Active Directory trust for realm "pne.qe"
-----------------------------------------------
  Realm name: pne.qe
  Domain NetBIOS name: PNE
  Domain Security Identifier: S-1-5-21-3912719521-1967590360-1136226524
  Trust direction: Two-way trust
  Trust type: Active Directory domain
  Trust status: Established and verified
[root@master ~]# ipa trust-find
---------------
1 trust matched
---------------
  Realm name: pne.qe
  Domain NetBIOS name: PNE
  Domain Security Identifier: S-1-5-21-3912719521-1967590360-1136226524
  Trust type: Active Directory domain
  UPN suffixes: qa.in, qa.io, qa.pne, qa.test, qa.org, test.qa
----------------------------
Number of entries returned 1
----------------------------
[root@master ~]# ipa trustdomain-find
Realm name: pne.qe
  Domain name: chd.pne.qe
  Domain NetBIOS name: CHD
  Domain Security Identifier: S-1-5-21-725505228-2944741108-2454985349
  Domain enabled: True

  Domain name: chd2.pne.qe
  Domain NetBIOS name: CHD2
  Domain Security Identifier: S-1-5-21-1720992857-1892626802-862641562
  Domain enabled: True

  Domain name: pne.qe
  Domain NetBIOS name: PNE
  Domain Security Identifier: S-1-5-21-3912719521-1967590360-1136226524
  Domain enabled: True
----------------------------
Number of entries returned 3
----------------------------

[root@master ~]# ipa trustdomain-find
Realm name: test.qa
ipa: ERROR: test.qa: trust not found
Comment 16 Sudhir Menon 2016-09-12 13:57:58 UTC 
Created attachment 1200213 [details]
error log
Comment 18 Petr Vobornik 2016-09-13 15:10:37 UTC 
Moving back to ON_QA according to comment 17.
Comment 20 Sudhir Menon 2016-09-16 18:44:53 UTC 
Verified on RHEL73 using 

ipa-server-4.4.0-12.el7.x86_64
ipa-server-trust-ad-4.4.0-12.el7.x86_64
sssd-1.14.0-41.el7.x86_64

[root@master ~]# ipa trust-add --two-way=true 
Realm name: pne.qe
Active Directory domain administrator: Administrator
Active Directory domain administrator's password: 
-----------------------------------------------
Added Active Directory trust for realm "pne.qe"
-----------------------------------------------
  Realm name: pne.qe
  Domain NetBIOS name: PNE
  Domain Security Identifier: S-1-5-21-3912719521-1967590360-1136226524
  Trust direction: Two-way trust
  Trust type: Active Directory domain
  Trust status: Established and verified

[root@master ~]# ipa idrange-find
----------------
5 ranges matched
----------------
  Range name: CHD.PNE.QE_id_range
  First Posix ID of the range: 632800000
  Number of IDs in the range: 200000
  First RID of the corresponding RID range: 0
  Domain SID of the trusted domain: S-1-5-21-725505228-2944741108-2454985349
  Range type: Active Directory domain range

  Range name: CHD2.PNE.QE_id_range
  First Posix ID of the range: 1786200000
  Number of IDs in the range: 200000
  First RID of the corresponding RID range: 0
  Domain SID of the trusted domain: S-1-5-21-1720992857-1892626802-862641562
  Range type: Active Directory domain range

  Range name: PNE.QE_id_range
  First Posix ID of the range: 558000000
  Number of IDs in the range: 200000
  First RID of the corresponding RID range: 0
  Domain SID of the trusted domain: S-1-5-21-3912719521-1967590360-1136226524
  Range type: Active Directory domain range

  Range name: TEST-RELM.TEST_id_range
  First Posix ID of the range: 539000000
  Number of IDs in the range: 200000
  First RID of the corresponding RID range: 1000
  First RID of the secondary RID range: 100000000
  Range type: local domain range

  Range name: TEST.QA_id_range
  First Posix ID of the range: 330800000
  Number of IDs in the range: 200000
  First RID of the corresponding RID range: 0
  Domain SID of the trusted domain: S-1-5-21-4204873575-1158510886-1449965812
  Range type: Active Directory domain range
----------------------------
Number of entries returned 5
----------------------------

[root@master ~]# ipa trust-find
---------------
1 trust matched
---------------
  Realm name: pne.qe
  Domain NetBIOS name: PNE
  Domain Security Identifier: S-1-5-21-3912719521-1967590360-1136226524
  Trust type: Active Directory domain
  UPN suffixes: qa.org
----------------------------
Number of entries returned 1
----------------------------

[root@master ~]# ipa trustdomain-find
Realm name: pne.qe
  Domain name: chd.pne.qe
  Domain NetBIOS name: CHD
  Domain Security Identifier: S-1-5-21-725505228-2944741108-2454985349
  Domain enabled: True

  Domain name: chd2.pne.qe
  Domain NetBIOS name: CHD2
  Domain Security Identifier: S-1-5-21-1720992857-1892626802-862641562
  Domain enabled: True

  Domain name: pne.qe
  Domain NetBIOS name: PNE
  Domain Security Identifier: S-1-5-21-3912719521-1967590360-1136226524
  Domain enabled: True

  Domain name: test.qa
  Domain NetBIOS name: TEST
  Domain Security Identifier: S-1-5-21-4204873575-1158510886-1449965812
  Domain enabled: True
----------------------------
Number of entries returned 4
----------------------------

Users/Groups from tree-root domain are also resolved
[root@master ~]# id test1
uid=330801112(test1) gid=330801112(test1) groups=330801112(test1),330801110(group2),330800513(domain users)

[root@master ~]# getent group group2
group2:*:330801110:test1,test2,test3
Comment 24 errata-xmlrpc 2016-11-04 05:52:06 UTC 
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://rhn.redhat.com/errata/RHBA-2016-2404.html
Note You need to log in before you can comment on or make changes to this bug.