#1692 Refactoring CA system certificates creation
Closed: migrated by dmoluguw. Opened by edewata.

Currently the CA subsystem creates the system certificates locally during installation. At that point the CA is not completely installed yet, so some components inside it may not be running properly, but it is used to generate the system certificates. For this to work the server has to ignore some errors that happen due to the incomplete state (e.g. #1615). The problem is if there are real errors during installation it will be hard to detect and investigate since the proper state of the server at that point is not clearly defined.

It would be better to create the system certificates in pkispawn before the server is started. That way there is no chicken-and-egg problem. When the server is started the server already has the system certificates. This will reduce the code complexity and improve troubleshooting.

This requires moving the "local" certificate generation code from ConfigurationUtils into a reusable library and CLI. This also depends on refactoring the certificate profile processor (#1691).


Metadata Update from @edewata:
- Issue set to the milestone: 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/2251

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata