Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
.FIPS mode does not support using a shared secret to establish a cross-forest trust
Establishing a cross-forest trust using a shared secret fails in FIPS mode because NTLMSSP authentication is not FIPS-compliant. To work around this problem, authenticate with an Active Directory (AD) administrative account when establishing a trust between an IdM domain with FIPS mode enabled and an AD domain.
Description of problem:
When trying to establish trust with AD domain with IPA in FIPS mode creation of Windows side of trust fails with "Access denied"
Version-Release number of selected component (if applicable):
ipa-server-4.9.1-1.module+el8.4.0+9665+c9815399.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Execute test suite: freeipa/ipatests/test_integration/test_trust.py
2. Look at results of test case "test_establish_forest_trust_with_shared_secret"
Actual results:
transport.py 513 DEBUG RUN ['powershell', '-c', '[System.DirectoryServices.ActiveDirectory.Forest]::getCurrentForest().CreateLocalSideOfTrustRelationship("testrelm.test", 1, "qwertyuiopQq!1")']
transport.py 558 DEBUG bash: line 2: /home/Administrator/env.sh: No such file or directory
transport.py 558 DEBUG Exception calling "CreateLocalSideOfTrustRelationship" with "3" argument(s): "Access is denied.
transport.py 558 DEBUG "
transport.py 558 DEBUG At line:1 char:1
transport.py 558 DEBUG + [System.DirectoryServices.ActiveDirectory.Forest]::getCurrentForest() ...
transport.py 558 DEBUG + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
transport.py 558 DEBUG + CategoryInfo : NotSpecified: (:) [], MethodInvocationException
transport.py 558 DEBUG + FullyQualifiedErrorId : UnauthorizedAccessException
transport.py 558 DEBUG
transport.py 214 ERROR Exit code: 1
Additional info:
The test succeeds in non-FIPS mode in otherwise equivalent environment.
Comment 1Alexander Bokovoy
2021-02-09 09:59:12 UTC
Please collect Samba debug logs and network traces between IPA and AD DCs during this test run. All traffic, both TCP and UDP.
With "log level = 10" in /usr/share/ipa/smb.conf.empty no lines are added to /var/log/httpd/error_log during execution of CreateLocalSideOfTrustRelationship
In attached log the last message is dated "16:10:30" while command was executed around 16:24
I also attach two trafic logs for two sequental attempts to execute CreateLocalSideOfTrustRelationship
master1.testrelm.test is 192.168.121.73
ad1.ad.test is 192.168.121.165
Without FIPS both variants works.
I have provided network traffic capture for establishing trust using PowerShell.
Comment 11Alexander Bokovoy
2021-02-12 10:01:02 UTC
So, according to the network traffic for non-FIPS mode, AD DC attempts to auth to IPA DC with NTLMSSP. That's blocked in FIPS mode because RC4 (NTLM hash) is not allowed in FIPS mode, so that should be expected.
The difference: in case of non-FIPS we respond with with STATUS_MORE_PROCESSING_REQUIRED, NTLMSSP_CHALLENGE which leads to eventual STATUS_LOGON_FAILURE and then use of a different method. In FIPS mode we don't do that and AD DC never goes further with a different method.
Comment 13Alexander Bokovoy
2021-02-16 08:46:11 UTC
This warrant more investigation which may prove it would be not possible to use a shared secret trust in FIPS mode.
I added a documentation note for RHEL 8.4.
Comment 14Florence Blanc-Renaud
2021-02-16 09:47:39 UTC
Hi Triviño,
Do you know if it looks like this bug might get fixed in time for RHEL 8.8?
Take care,
Josip
Comment 36RHEL Program Management
2023-09-18 18:37:38 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 37RHEL Program Management
2023-09-18 18:39:49 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 38Red Hat Bugzilla
2024-01-17 04:25:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Description of problem: When trying to establish trust with AD domain with IPA in FIPS mode creation of Windows side of trust fails with "Access denied" Version-Release number of selected component (if applicable): ipa-server-4.9.1-1.module+el8.4.0+9665+c9815399.x86_64 How reproducible: Always Steps to Reproduce: 1. Execute test suite: freeipa/ipatests/test_integration/test_trust.py 2. Look at results of test case "test_establish_forest_trust_with_shared_secret" Actual results: transport.py 513 DEBUG RUN ['powershell', '-c', '[System.DirectoryServices.ActiveDirectory.Forest]::getCurrentForest().CreateLocalSideOfTrustRelationship("testrelm.test", 1, "qwertyuiopQq!1")'] transport.py 558 DEBUG bash: line 2: /home/Administrator/env.sh: No such file or directory transport.py 558 DEBUG Exception calling "CreateLocalSideOfTrustRelationship" with "3" argument(s): "Access is denied. transport.py 558 DEBUG " transport.py 558 DEBUG At line:1 char:1 transport.py 558 DEBUG + [System.DirectoryServices.ActiveDirectory.Forest]::getCurrentForest() ... transport.py 558 DEBUG + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ transport.py 558 DEBUG + CategoryInfo : NotSpecified: (:) [], MethodInvocationException transport.py 558 DEBUG + FullyQualifiedErrorId : UnauthorizedAccessException transport.py 558 DEBUG transport.py 214 ERROR Exit code: 1 Additional info: The test succeeds in non-FIPS mode in otherwise equivalent environment.