Chapter 10. Troubleshooting setting up a cross-forest trust

4. Create a separate trust object for each trust direction. Each of the objects get created on both sides (IdM and AD). If you are establishing a one-way trust, only one object is created on each side.

5. The IdM server uses the Samba suite to handle domain controller capabilities for Active Directory and creates a trust object on the target AD PDC:

   1. The IdM server establishes a secure connection to the IPC$ share on the target DC. Since RHEL 8.4, the connection requires at least the SMB3 protocol with Windows Server 2012 and above to ensure the connection is sufficiently secure with AES-based encryption used for the session.
   2. The IdM server queries for the presence of the trusted domain object (TDO) using an LSA QueryTrustedDomainInfoByName call.

   3. If the TDO is already present, remove it with an LSA DeleteTrustedDomain call.

      Note

      This call fails if the AD user account used to establish the trust does not have full Enterprise Admin (EA) or Domain Admin (DA) privileges for the forest root, such as members of the Incoming Forest Trust Builders group. If the old TDO is not automatically removed, an AD Administrator must manually remove it from AD.

   4. The IdM server creates a new TDO with an LSA CreateTrustedDomainEx2 call. The TDO credentials are randomly generated using a Samba-provided password generator with 128 random characters.

   5. The new TDO is then modified with an LSA SetInformationTrustedDomain call to make sure encryption types supported by the trust are set properly:

      1. The RC4_HMAC_MD5 encryption type is enabled, even if there are no RC4 keys in use, due to how Active Directory is designed.
      2. AES128_CTS_HMAC_SHA1_96 and AES256_CTS_HMAC_SHA1_96 encryption types are enabled.
6. For a forest trust, verify that in-forest domains can be reached transitively with an LSA SetInformationTrustedDomain call.

7. Add trust topology information about the other forest (IdM in the case of communicating with AD, AD in the case of communicating with IdM) using an LSA RSetForestTrustInformation call.

   Note

   This step might cause a conflict for one of three reasons:

   • A SID namespace conflict, reported as an LSA_SID_DISABLED_CONFLICT error. This conflict cannot be resolved.
   • A NetBIOS namespace conflict, reported as an LSA_NB_DISABLED_CONFLICT error. This conflict cannot be resolved.
   • A DNS namespace conflict with a top level name (TLN), reported as an LSA_TLN_DISABLED_CONFLICT error. The IdM server can automatically resolve a TLN conflict if it is caused by another forest.

   To resolve a TLN conflict, the IdM server performs the following steps:

   1. Retrieve forest trust information for the conflicting forest.
   2. Add an exclusion entry for the IdM DNS namespace to the AD forest.
   3. Set forest trust information for the forest we conflict on.
   4. Re-try establishing the trust to the original forest.

   The IdM server can only resolve these conflicts if you authenticated the ipa trust-add command with the privileges of an AD administrator that can change forest trusts. If you do not have access to those privileges, the administrator of the original forest must manually perform the steps above in the Active Directory Domains and Trusts section of the Windows UI.

8. If it does not exist, create the ID range for the trusted domain.
9. For a forest trust, query Active Directory domain controllers from the forest root for details about the forest topology. The IdM server uses this information to create additional ID ranges for any additional domains from the trusted forest.

Procedure

1. To enable debugging for the IdM server, create the file /etc/ipa/server.conf with the following contents.

   [global]
   debug=True

2. Restart the httpd service to load the debugging configuration.

   [root@trust_controller ~]# systemctl restart httpd

3. Stop the smb and winbind services.

   [root@trust_controller ~]# systemctl stop smb winbind

4. Set the debugging log level for the smb and winbind services.

   [root@trust_controller ~]# net conf setparm global 'log level' 100

5. To enable debug logging for Samba client code used by the IdM framework, edit the /usr/share/ipa/smb.conf.empty configuration file to have the following contents.

       [global]
       log level = 100

6. Remove previous Samba logs.

   [root@trust_controller ~]# rm /var/log/samba/log.*

7. Start the smb and winbind services.

   [root@trust_controller ~]# systemctl start smb winbind

8. Print a timestamp as you attempt to establish a trust with verbose mode enabled.

   [root@trust_controller ~]# date; ipa -vvv trust-add --type=ad ad.example.com

9. Review the following error log files for information about the failed request:

   1. /var/log/httpd/error_log
   2. /var/log/samba/log.*

10. Disable debugging.

    [root@trust_controller ~]# mv /etc/ipa/server.conf /etc/ipa/server.conf.backup
    [root@trust_controller ~]# systemctl restart httpd
    [root@trust_controller ~]# systemctl stop smb winbind
    [root@trust_controller ~]# net conf setparm global 'log level' 0
    [root@trust_controller ~]# mv /usr/share/ipa/smb.conf.empty /usr/share/ipa/smb.conf.empty.backup
    [root@trust_controller ~]# systemctl start smb winbind

11. Optional: If you are unable to determine the cause of the authentication issue:

    1. Collect and archive the log files you recently generated.

       [root@trust_controller ~]# tar -cvf debugging-trust.tar /var/log/httpd/error_log /var/log/samba/log.*

    2. Open a Red Hat Technical Support case and provide the timestamp and debug logs from the attempt.