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.
Description of problem:
Customer is looking for a way to toggle to stop allowing CA's to be issued past the issuing CA's validity period. This is a concern that they are seeking to address as they are concerned it goes against their policies.
Version-Release number of selected component (if applicable):
pki-ca*
How reproducible:
Very
Steps to Reproduce:
1. Issue a CA certificate with the date going beyond the issuing CA's validity period
Actual results:
Cert g ets issued with no problems. All other certs will reset to the notAfter of the issuing CA.
Expected results:
Same as every other cert issued.
Additional info:
This is what occurs for a regular Server cert. It identifies that the notAfter is past the CA's own and resets it.
[25/Jan/2021:14:46:35][http-bio-8443-exec-5]: CAService: issueX509Cert: cert past CA's NOT_AFTER...ca.enablePastCATime != true...resetting
This is what appears for a CA cert. It just alerts you of the issue.
[25/Jan/2021:14:48:51][http-bio-8443-exec-5]: CAService: issueX509Cert: CA cert issuance past CA's NOT_AFTER.
And in looking at the code, this was intended.
base/ca/src/com/netscape/ca/CAService.java
if (end.after(caNotAfter)) {
if (!is_ca) {
if (!engine.getEnablePastCATime()) {
end = caNotAfter;
certi.set(CertificateValidity.NAME,
new CertificateValidity(begin, caNotAfter));
logger.debug("CAService: issueX509Cert: cert past CA's NOT_AFTER...ca.enablePastCATime != true...resetting");
} else {
logger.debug("CAService: issueX509Cert: cert past CA's NOT_AFTER...ca.enablePastCATime = true...not resetting");
}
} else {
logger.debug("CAService: issueX509Cert: CA cert issuance past CA's NOT_AFTER.");
} //!is_ca
logger.info(CMS.getLogMessage("CMSCORE_CA_PAST_NOT_AFTER"));
}
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 (pki-core 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/RHEA-2021:4239
Description of problem: Customer is looking for a way to toggle to stop allowing CA's to be issued past the issuing CA's validity period. This is a concern that they are seeking to address as they are concerned it goes against their policies. Version-Release number of selected component (if applicable): pki-ca* How reproducible: Very Steps to Reproduce: 1. Issue a CA certificate with the date going beyond the issuing CA's validity period Actual results: Cert g ets issued with no problems. All other certs will reset to the notAfter of the issuing CA. Expected results: Same as every other cert issued. Additional info: This is what occurs for a regular Server cert. It identifies that the notAfter is past the CA's own and resets it. [25/Jan/2021:14:46:35][http-bio-8443-exec-5]: CAService: issueX509Cert: cert past CA's NOT_AFTER...ca.enablePastCATime != true...resetting This is what appears for a CA cert. It just alerts you of the issue. [25/Jan/2021:14:48:51][http-bio-8443-exec-5]: CAService: issueX509Cert: CA cert issuance past CA's NOT_AFTER. And in looking at the code, this was intended. base/ca/src/com/netscape/ca/CAService.java if (end.after(caNotAfter)) { if (!is_ca) { if (!engine.getEnablePastCATime()) { end = caNotAfter; certi.set(CertificateValidity.NAME, new CertificateValidity(begin, caNotAfter)); logger.debug("CAService: issueX509Cert: cert past CA's NOT_AFTER...ca.enablePastCATime != true...resetting"); } else { logger.debug("CAService: issueX509Cert: cert past CA's NOT_AFTER...ca.enablePastCATime = true...not resetting"); } } else { logger.debug("CAService: issueX509Cert: CA cert issuance past CA's NOT_AFTER."); } //!is_ca logger.info(CMS.getLogMessage("CMSCORE_CA_PAST_NOT_AFTER")); }