IMPORTANT!

This change likely needs to be backported - most likely to 10.0 and 10.1.
Please add/clone tickets when this ticket is addressed.

Proposed Milestone: 10.2.1 (per CS Meeting of 09/17/2014)

We need steps to reproduce the problem.

Steps to reproduce:
1. Optional: assuming ticket #1226 is fixed, edit /usr/share/pki/ca/conf/caOCSP.profile, change the range and add the rangeUnit properties to create a short-lived certificate:

2.default.params.range=1
2.default.params.rangeUnit=minute

1. Create CA master.
2. Wait for the OCSP certificate to expire, or change the system date past the expiration date.
3. Use console to renew the OCSP certificate.
4. Export CA subsystem certificates. See: https://access.redhat.com/documentation/en-US/Red_Hat_Certificate_System/8.1/html/Deploy_and_Install_Guide/exporting-keys.html
5. Create CA clone with the exported CA subsystem certificates.

The CA clone installation will fail since it incorrectly imports just the expired certificate but not the valid one.

master:

• 78371f0ecd801ccfb1a637ba8dd95a7f4dd051b9
• bd411710a735f49147fa085fda000857a5370627

Cloned to #1231 for 10.1.

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/1656

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.