For migration purposes, crlId should be configurable to not conflict with existing CRL's.
Two potential options for implementation could be:
Checking in fix:
commit 0c502a387c90d2e2d8ebe9e3edf3dfeaf1d6eba4 Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com Date: Wed Jul 27 11:43:33 2016 -0700
Make starting CRL Number configurable.
Ticket #2406 Make starting CRL Number configurable This simple patch provides a pkispawn config param that passes some starting crl number value to the config process. Here is a sample: [CA] pki_ca_starting_crl_number=4000 After the CA comes up the value of "crlNumber" in the db will reflect that value of 4000. Currently no other values are changed. We can talk about if we need more values reset in the given case. Also, this creates a setting in the CS.cfg ca.crl.MasterCrl.startingCrlNumber=4000 This setting is only consulted when the crl Issuing Point record is created for the first time.
Closing ticket
This is documented in this page: http://pki.fedoraproject.org/wiki/CRL_Migration
Metadata Update from @dsirrine: - Issue assigned to jmagne - Issue set to the milestone: 10.3.5
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/2526
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.
Login to comment on this ticket.