#1698 Refactoring CSR generation for standalone installation
Closed: fixed Opened by edewata.

Currently the CSRs for standalone KRA & OCSP installation are generated in the server during installation. The CSRs need to be signed by a separate CA, then the certificates need to be imported, and only after that the installation can continue. This two-step process poses the same issues as in external CA installation, for example the server must remain running while waiting for the certificates.

The issues with external CA are being addressed in ticket #456 by moving the CSR generation before starting the server. The same solution should be applied for standalone KRA & OCSP installation. Once this is complete, the configuration servlet can be simplified to remove the step two codes.


Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

This was implemented in 10.5.

Metadata Update from @edewata:
- 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 version adjusted to None
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.7 (was: UNTRIAGED)

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

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.

Metadata