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 1190566 - Manual IPA - AD Trust validation issue from AD
Summary: Manual IPA - AD Trust validation issue from AD
Keywords:
Status: CLOSED DUPLICATE of bug 1345975
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2015-02-09 07:20 UTC by Deepak Das
Modified: 2018-10-19 13:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-19 13:46:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Deepak Das 2015-02-09 07:20:19 UTC 
Description of problem:

When validating IPA domain trust from AD, following error is observed.

------------------------------------------------------------------------------
The secure channel (SC) verification on Active Directory Domain Controller \\adserver.addomain.com of domain addomain.com to domain ipadomain.com failed with error: Access is denied.

The secure channel (SC) reset on Active Directory Domain Controller \\adserver.addomain.com of domain addomain.com to domain ipadomain.com failed with error: Access is denied.

The secure channel (SC) verification on Active Directory Domain Controller \\ipaserver.ipadomain.com of domain ipadomain.com to domain addomain.com failed with error: The specified domain either does not exist or could not be contacted.

The secure channel (SC) reset on Active Directory Domain Controller \\ipaserver.ipadomain.com of domain ipadomain.com to domain addomain.com failed with error: The specified domain either does not exist or could not be contacted.
------------------------------------------------------------------------------- 


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

ipa-server-trust-ad-3.3.3-28.el7_0.3.x86_64
ipa-server-3.3.3-28.el7_0.3.x86_64

How reproducible:

Always

Steps to Reproduce:

1) Create IPA - AD Trust.
2) Login into AD Server.
3) Open "Active Directory Domains and Trust" -> Right Click on AD Domain -> Properties -> Trusts -> Select the IPA Domain (Incoming/Outgoing) -> Properties -> Validate 

Actual results:

Error is observed mentioned in the  description.

Expected results:

Validation is succeed. 

Additional info:
Comment 2 Martin Kosek 2015-02-09 07:54:48 UTC 
CCign Alexander. But to me, this sounds like IPA DNS SRV records are not seen from AD.
Comment 3 Deepak Das 2015-02-09 08:10:06 UTC 
Hi Martin,

As per check, IPA DNS records are fetched correctly from AD. Snapshot from AD server is given below.

--------------------------------------------------------------------------------
PS C:\> nslookup
Default Server:  localhost
Address:  127.0.0.1

> set type=srv

> _ldap._tcp.ipadomain.com
Server:  localhost
Address:  127.0.0.1

DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
_ldap._tcp.ipadomain.com        SRV service location:
          priority       = 0
          weight         = 100
          port           = 389
          svr hostname   = ipaserver.ipadomain.com

ipaserver.ipadomain.com internet address = 192.168.122.2


> _kerberos._udp.ipadomain.com
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
_kerberos._udp.ipadomain.com    SRV service location:
          priority       = 0
          weight         = 100
          port           = 88
          svr hostname   = ipaserver.ipadomain.com

ipaserver.ipadomain.com internet address = 192.168.122.2

> _kerberos._tcp.ipadomain.com
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
_kerberos._tcp.ipadomain.com    SRV service location:
          priority       = 0
          weight         = 100
          port           = 88
          svr hostname   = ipaserver.ipadomain.com

ipaserver.ipadomain.com internet address = 192.168.122.2

> _kpasswd._udp.ipadomain.com
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
_kpasswd._udp.ipadomain.com     SRV service location:
          priority       = 0
          weight         = 100
          port           = 464
          svr hostname   = ipaserver.ipadomain.com

ipaserver.ipadomain.com internet address = 192.168.122.2

> _kpasswd._tcp.ipadomain.com
Server:  localhost
Address:  127.0.0.1

Non-authoritative answer:
_kpasswd._tcp.ipadomain.com     SRV service location:
          priority       = 0
          weight         = 100
          port           = 464
          svr hostname   = ipaserver.ipadomain.com

ipaserver.ipadomain.com internet address = 192.168.122.2

--------------------------------------------------------------------------------
Comment 4 Sumit Bose 2015-02-09 08:16:14 UTC 
I took a look at the issue last week and compared an IPA version from RHEL-6.5 where validation is working with a current Fedora installation where validation fails as well.

I found a failure in netr_ServerAuthenticate3() on Fedora which is not present in the working RHEL version. I'll try to dig deeper here.
Comment 5 Alexander Bokovoy 2015-02-09 08:39:07 UTC 
Right now we don't support validation via Windows UI. You are supposed to use IPA CLI: 'ipa trust-add ...' which will force validation as one of last steps.

See also https://fedorahosted.org/freeipa/ticket/4114

You also need to be able to resolve SRV records in the _msdcs namespaces.
Comment 6 Martin Kosek 2015-02-13 09:16:17 UTC 
(In reply to Sumit Bose from comment #4)
> I found a failure in netr_ServerAuthenticate3() on Fedora which is not
> present in the working RHEL version. I'll try to dig deeper here.

(In reply to Alexander Bokovoy from comment #5)
> Right now we don't support validation via Windows UI. You are supposed to
> use IPA CLI: 'ipa trust-add ...' which will force validation as one of last
> steps.

Is there a bug to fix in IPA after all or rather not?
Comment 7 Alexander Bokovoy 2015-02-13 10:17:34 UTC 
There is a bug in either Samba proper or ipasam module that prevents us to allow validating from Windows side. We mitigate it by forcing validation from IPA side when adding trust with AD admin credentials.
Comment 9 Martin Kosek 2015-02-13 10:55:33 UTC 
Linking to upstream ticket https://fedorahosted.org/freeipa/ticket/4114.
Comment 12 Florence Blanc-Renaud 2018-10-19 13:46:32 UTC 
This issue is a duplicate of BZ #1345975  [RFE] Support One-Way Trust authenticated by trust secret

*** This bug has been marked as a duplicate of bug 1345975 ***
Note You need to log in before you can comment on or make changes to this bug.