Random serial number on clone CA is not enabled after required configuration changes are made to master CA CS.cfg
Steps to Reproduce:
1. Configure master and clone CA 2. stop master CA service 3. Enable random serial number on master CA by changing the following parameters dbs.enableRandomSerialNumbers=true dbs.forceModeChange=true dbs.randomSerialNumberCounter=-2 4. start master CA service 5. random serial number is successfully enabled on the master CA 6. Wait for the certificate repository maintenance thread to be run
Actual results:
random serial number is not enabled on the clone CA after the thread is run.
Expected results:
random serial number should be enabled on the clone CA after the thread is run.
On December 7, 2015, rpattath confirmed the following work-around:
If random serial number is manually enabled on the clone CA by editing CS.cfg, the random serial number is generated for every cert issued after that.
Per the documented work-around in comment 2 above, and by proposal made in CS/DS meeting of 12/07/2015: 10.3 - minor
Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - major
Metadata Update from @rpattath: - Issue assigned to vakwetu - Issue set to the milestone: FUTURE
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
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 rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1286834) - Custom field version adjusted to None - Issue close_status updated to: None
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/2267
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.