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.
Comment 3Florence Blanc-Renaud
2020-01-29 18:22:29 UTC
Issue reproduce with the following scenario on RHEL 7.7:
1. install IPA server with embedded CA
2. install replica without CA
At this point the replica ha PKINIT enabled.
3. disable pkinit on the replica with ipa-pkinit-manage disable
4. try to re-enable pkinit on the replica with ipa-pkinit-manage enable
The command fails with
# ipa-pkinit-manage enable
Configuring Kerberos KDC (krb5kdc)
[1/1]: installing X509 Certificate for PKINIT
PKINIT certificate request failed: Certificate issuance failed (CA_UNREACHABLE: Error 7 connecting to https://vm-151.abc.idm.lab.eng.brq.redhat.com:8443/ca/ee/ca/profileSubmitSSLClient: Couldn't connect to server.)
Failed to configure PKINIT
Full PKINIT configuration did not succeed
The setup will only install bits essential to the server functionality
You can enable PKINIT after the setup completed using 'ipa-pkinit-manage'
Done configuring Kerberos KDC (krb5kdc).
The ipa-pkinit-manage command was successful
If I apply the patch, the command succeeds, meaning we missed to backport the patch to ipa-4-6 branch.
Comment 5Florence Blanc-Renaud
2020-01-30 09:14:59 UTC
Comment 6Florence Blanc-Renaud
2020-01-30 09:22:00 UTC
Fixed upstream:
master:
7785210 pkinit enable: use local dogtag only if host has CA
64be314 ipatests: add integration test for pkinit enable on replica
6589837 pkinit setup: fix regression on master install
a25de95 test: add non-reg test checking pkinit after server install
ipa-4-7:
20b0a7a pkinit enable: use local dogtag only if host has CA
3636460 ipatests: add integration test for pkinit enable on replica
fcf3fd7 test: add non-reg test checking pkinit after server install
acc3849 pkinit setup: fix regression on master install
Comment 7Florence Blanc-Renaud
2020-01-30 12:06:54 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: ipa 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:3936