Currently pkispawn creates a temp SSL server cert before the server starts, then replaces it with a permanent cert in the configuration servlet while the server is running.
Ideally pkispawn should not create the temp SSL server cert if there is a permanent cert already in the NSS database (e.g. in standalone KRA case). Also, SSL server cert replacement should be done while the server is not running.
Fixed in master:
Metadata Update from @edewata: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.0 (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/2906
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.