When using random serial numbers:
pki_random_serial_numbers_enable=True
the following default pki serial number range is specified in '/etc/pki/default.cfg':
pki_serial_number_range_start=1 pki_serial_number_range_end=10000000
However, if the admin overrides this range in their user-provided pkispawn configuration file, their specified range must consist of at least eight numbers (requiring four-bits), or installation will fail with a message such as:
. . . pkispawn : INFO ....... configuring PKI configuration data. Installation failed: com.netscape.certsrv.base.PKIException: Error in setting certificate names and k ey sizes: Range size is too small to support random certificate serial numbers. Please check the CA logs in /var/log/pki/pki-tomcat/ca.
A side-effect of this error is that the un-configured pki server instance will remain running.
This ticket has been created to add a serial number range check into the python code of pkispawn when random serial numbers have been specified to prevent installation if an inadequate serial number range has been specified.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: minor - Issue set to the milestone: 10.5
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.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/2898
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.