When the CA signing certificate is renewed using the caCACert profile, the validity period end of the renewed certificate is the same as the validity period end of the old certificate. The validity period start is correctly set to the renewal time.
For example, old certificate:
Subject: "CN=Certificate Authority,O=IDM.LAB.BOS.REDHAT.COM" Issuer: "CN=Certificate Authority,O=IDM.LAB.BOS.REDHAT.COM" Serial Number: 1 (0x1) Validity: Not Before: Tue Sep 30 01:25:53 2014 Not After : Sat Sep 30 01:25:53 2034
renewed certificate:
Subject: "CN=Certificate Authority,O=IDM.LAB.BOS.REDHAT.COM" Issuer: "CN=Certificate Authority,O=IDM.LAB.BOS.REDHAT.COM" Serial Number: 11 (0xb) Validity: Not Before: Tue Oct 07 09:27:08 2014 Not After : Sat Sep 30 01:25:53 2034
Steps to Reproduce:
1. Renew the CA signing certificate using the caCACert profile.
Actual results:
The renewed certificate's validity period end is the same as the old certificate's period end.
Expected results:
The renewed certificate's validity period end is 7305 days (or whatever is configured in the profile) from the validity period start.
Per discussions in the Dogtag 10.3 Triage meeting of 01/06/2016: Dogtag 10.4.
Metadata Update from @jcholast: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: FUTURE (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Metadata Update from @mharmsen: - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1150031)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2283
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.