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 1849914 - FreeIPA - Utilize 256-bit AJP connector passwords
Summary: FreeIPA - Utilize 256-bit AJP connector passwords
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.3
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: 8.3
Assignee: Thomas Woerner
QA Contact: ipa-qe
URL:
Whiteboard:
: 1849146 (view as bug list)
Depends On: 1845447
Blocks: 1793411 1842946
TreeView+ depends on / blocked
 
Reported: 2020-06-23 07:17 UTC by Christian Heimes
Modified: 2020-11-04 02:51 UTC (History)
5 users (show)

Fixed In Version: ipa-4.8.7-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:51:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Christian Heimes 2020-06-23 07:17:11 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/8372

### Request for enhancement

As an admin, I wish all passwords utilized in an IPA environment to be at least 128 or 256 bits. Importantly, this should include the AJP connector secret shared by Tomcat and httpd.

### Issue

Currently, when Dogtag PKI 10.9 generates an AJP secret (during the initial `pkispawn`), we generate a [~75 bit](https://github.com/dogtagpki/pki/blob/737fc097afb42c0b48fe362e970591099dfed2c7/base/common/python/pki/__init__.py#L217-L218) password. Because this is static and not rotated, it probably makes sense to use a more secure AJP connector password. PKI has exposed the `pki_ajp_secret` configuration value that allows IPA to generate and specify their preferred password.

#### Steps to Reproduce

1. Grab Dogtag 10.9.
2. Install a fresh IPA server.
3. Realize that the password is 12 alpha-numeric-with-punctation characters. 

#### Actual behavior

75 bit password.

#### Expected behavior

256-bit password.

#### Version/Release/Distribution

All branches prior to https://github.com/freeipa/freeipa/pull/4819 

#### Additional info:

Comment 2 Christian Heimes 2020-06-23 07:26:42 UTC
*** Bug 1849146 has been marked as a duplicate of this bug. ***

Comment 8 Kaleem 2020-07-10 10:45:23 UTC
Verified based on pytest-run attached (pytest-run.log). Also runner.log has been attached to show machine is in FIPS mode and also IPA version.

Snippet from attached files.

IPA Version:
------------
2020-07-08T23:24:56+0000 ok: [master.testrelm.test] => (item=ipa-server) => 
2020-07-08T23:24:56+0000   msg:
2020-07-08T23:24:56+0000   - arch: x86_64
2020-07-08T23:24:56+0000     epoch: null
2020-07-08T23:24:56+0000     name: ipa-server
2020-07-08T23:24:56+0000     release: 4.module+el8.3.0+7221+eedbd403
2020-07-08T23:24:56+0000     source: rpm
2020-07-08T23:24:56+0000     version: 4.8.7

--------------------------------
2020-07-08T23:23:16+0000 TASK [Check FIPS crypto-policies is enabled] ***********************************
2020-07-08T23:23:17+0000 changed: [master.testrelm.test]
2020-07-08T23:23:18+0000 changed: [runner.testrelm.test]


============================= test session starts ==============================
platform linux -- Python 3.6.8, pytest-3.4.2, py-1.5.3, pluggy-0.6.0 -- /usr/libexec/platform-python
cachedir: ../../../../../home/cloud-user/.pytest_cache
metadata: {'Python': '3.6.8', 'Platform': 'Linux-4.18.0-222.el8.x86_64-x86_64-with-redhat-8.3-Ootpa', 'Packages': {'pytest': '3.4.2', 'py': '1.5.3', 'pluggy': '0.6.0'}, 'Plugins': {'metadata': '1.10.0', 'html': '1.22.1', 'sourceorder': '0.5', 'multihost': '3.0'}}
rootdir: /usr/lib/python3.6/site-packages/ipatests, inifile:
plugins: metadata-1.10.0, html-1.22.1, sourceorder-0.5, multihost-3.0
collecting ... collected 4 items

test_integration/test_automember.py::TestAutounmembership::test_modify_user_entry_unmembership PASSED [ 25%]
test_integration/test_automember.py::TestAutounmembership::test_modify_host_entry_unmembership PASSED [ 50%]
test_integration/test_automember.py::TestAutounmembership::test_modify_user_entry_unmembership_disabled PASSED [ 75%]
test_integration/test_automember.py::TestAutounmembership::test_modify_host_entry_unmembership_disabled PASSED [100%]

--------------- generated xml file: /home/cloud-user/junit.xml ----------------
----------- generated html file: file:///home/cloud-user/report.html -----------
========================== 4 passed in 567.71 seconds ==========================

Comment 11 errata-xmlrpc 2020-11-04 02:51:04 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 (Moderate: idm:DL1 and idm:client security, bug fix, and enhancement update), 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/RHSA-2020:4670


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