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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/6019

After installing a replica, only the main CA cert is tracked by certmonger:
{{{
# getcert list | grep 'certificate:.*caSigningCert'
	certificate: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='caSigningCert cert-pki-ca',token='NSS Certificate DB'
}}}

One has to run `ipa-certupdate` for lightweight sub-CA certs to be tracked by certmonger as well:
{{{
# getcert list | grep 'certificate:.*caSigningCert'
	certificate: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='caSigningCert cert-pki-ca',token='NSS Certificate DB'
	certificate: type=NSSDB,location='/etc/pki/pki-tomcat/alias',nickname='caSigningCert cert-pki-ca fb8eb99f-5a29-4e57-9de0-4027b65a5dcb',token='NSS Certificate DB'
}}}

Fix `ipa-replica-install` to do this automatically.

Current behaviour: admins must manually run `ipa-certupdate' command
to add Certmonger tracking requests for lightweight CAs after deploying
a replica.

This ticket means they don't have to do that extra manual step.

Note that this ticket only applies to replica install.  Even if this
ticket is implemented, it will still be necessary for admins to
run `ipa-certupdate' to add tracking request after creating a new
lightweight CA.

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/08b768313020c45bfa82d67cd214afabf605f4b3
ipa-4-4:
https://fedorahosted.org/freeipa/changeset/99b0db0ebf090c9f60078e9ca9bf2aba665635f5

Verified using IPA version ::
ipa-server-4.4.0-12.el7.x86_64

Please find the attachment for verification steps. Marking BZ as verified.

Created attachment 1202888 [details]
console.log

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://rhn.redhat.com/errata/RHBA-2016-2404.html