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 1608783 - ipa trust-add fails in FIPS mode.
Summary: ipa trust-add fails in FIPS mode.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-26 09:50 UTC by Sudhir Menon
Modified: 2022-03-13 15:24 UTC (History)
10 users (show)

Fixed In Version: ipa-4.6.4-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1615765 (view as bug list)
Environment:
Last Closed: 2018-10-30 11:00:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
console-output (4.19 KB, text/plain)
2018-07-26 09:52 UTC, Sudhir Menon
no flags Details
http error log (583.75 KB, text/plain)
2018-07-26 09:57 UTC, Sudhir Menon
no flags Details
dirsrv error logs (240.68 KB, text/plain)
2018-07-26 09:58 UTC, Sudhir Menon
no flags Details
samba logs (200.41 KB, application/x-gzip)
2018-07-26 10:04 UTC, Sudhir Menon
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FREEIPA-7979 0 None None None 2022-03-13 15:24:33 UTC
Red Hat Product Errata RHBA-2018:3187 0 None None None 2018-10-30 11:01:37 UTC

Description Sudhir Menon 2018-07-26 09:50:41 UTC
Description of problem: ipa trust-add fails in FIPS mode.


Version-Release number of selected component (if applicable):
[root@intel-canoepass-12 abrt]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 Beta (Maipo)

ipa-server-4.6.4-3.el7.x86_64
sssd-1.16.2-7.el7.x86_64
krb5-server-1.15.1-33.el7.x86_64
pki-server-10.5.9-3.el7.noarch
389-ds-base-1.3.8.4-8.el7.x86_64
samba-4.8.3-3.el7.x86_64

How reproducible: Always

Steps to Reproduce:
1. Seup IPA on FIPS enabled machine
2. establish trust with Windows2K16 AD
3. Check the message displayed on the console.

Actual results:
3. echo password | ipa trust-add ipaad2016.test --admin Administrator  --two-way=True --password

ipa: ERROR: CIFS server communication error: code "3221225473", message "{Operation Failed} The requested operation was unsuccessful." (both may be "None")

Expected results:
Trust should be established without any error.

Additional info: 
Attaching the samba, http and dirsrv debug logs for reference.

Comment 2 Sudhir Menon 2018-07-26 09:52:54 UTC
Created attachment 1470670 [details]
console-output

Comment 3 Sudhir Menon 2018-07-26 09:57:12 UTC
Created attachment 1470671 [details]
http error log

Comment 4 Sudhir Menon 2018-07-26 09:58:05 UTC
Created attachment 1470672 [details]
dirsrv error logs

Comment 5 Sudhir Menon 2018-07-26 10:04:17 UTC
Created attachment 1470675 [details]
samba logs

Comment 8 Rob Crittenden 2018-07-30 15:46:18 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/7659

Comment 9 Alexander Bokovoy 2018-08-09 08:24:03 UTC
Upstream pull request: https://github.com/freeipa/freeipa/pull/2228

Comment 10 Florence Blanc-Renaud 2018-08-16 13:14:39 UTC
Fixed upstream
master:
    https://pagure.io/freeipa/c/de8f969f2d40722b590f43ab9bb31eada58ec4b3 Move fips_enabled to a common library to share across different plugins
    https://pagure.io/freeipa/c/6907a0cef7f22293c16df17aa486f7ec2d8a0899 ipasam: do not use RC4 in FIPS mode

ipa-4-7:
    https://pagure.io/freeipa/c/5e8bc96b2aca26878f98e8180ee21e94f06ae9f1 Move fips_enabled to a common library to share across different plugins
    https://pagure.io/freeipa/c/04c5798d61d4c2275592b77467adc927f3a08b0d ipasam: do not use RC4 in FIPS mode

ipa-4-6:
    https://pagure.io/freeipa/c/2ede8e6b90d8cec4ba651ecd14e1213536a585d6 Move fips_enabled to a common library to share across different plugins
    https://pagure.io/freeipa/c/0a89f648d600610b6a17438847eb0d18c47be6db ipasam: do not use RC4 in FIPS mode

Comment 12 Nikhil Dehadrai 2018-08-17 18:41:08 UTC
ipa-server-version and components:
sssd-1.16.2-12.el7.x86_64
ipa-server-4.6.4-6.el7.x86_64
389-ds-base-1.3.8.4-10.el7.x86_64
krb5-server-1.15.1-34.el7.x86_64

Verified the bug on the basis of following observations:
1. Verified that trust-addition is successful in FIPS mode
2. Verified that trust addition is successful in non-FIPS mode.

Coonsole output: (FIPS)
:: [ 23:15:45 ] :: [  BEGIN   ] :: Running 'echo Secret123 | ipa trust-add ipaad2016.test --admin Administrator                 --range-type=ipa-ad-trust --password --two-way=True'
-------------------------------------------------------
Added Active Directory trust for realm "ipaad2016.test"
-------------------------------------------------------
  Realm name: ipaad2016.test
  Domain NetBIOS name: IPAAD2016
  Domain Security Identifier: S-1-5-21-813110839-3732285123-1597101681
  Trust direction: Two-way trust
  Trust type: Active Directory domain
  Trust status: Established and verified
:: [ 23:16:05 ] :: [   PASS   ] :: Command 'echo Secret123 | ipa trust-add ipaad2016.test --admin Administrator                 --range-type=ipa-ad-trust --password --two-way=True' (Expected 0, got 0)


Console output: (Non-FIPS)

:: [ 12:53:44 ] :: [  BEGIN   ] :: Running 'echo Secret123 | ipa trust-add ipaad2016.test --admin Administrator                 --range-type=ipa-ad-trust --password --two-way=True'
-------------------------------------------------------
Added Active Directory trust for realm "ipaad2016.test"
-------------------------------------------------------
  Realm name: ipaad2016.test
  Domain NetBIOS name: IPAAD2016
  Domain Security Identifier: S-1-5-21-813110839-3732285123-1597101681
  Trust direction: Two-way trust
  Trust type: Active Directory domain
  Trust status: Established and verified
:: [ 12:53:49 ] :: [   PASS   ] :: Command 'echo Secret123 | ipa trust-add ipaad2016.test --admin Administrator                 --range-type=ipa-ad-trust --password --two-way=True' (Expected 0, got 0)


Thus on the basis of above observations, marking the status of bug to 'VERIFIED'.

Comment 15 errata-xmlrpc 2018-10-30 11:00:22 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://access.redhat.com/errata/RHBA-2018:3187


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