When originally designed (see PKI Instance Deployment), it was believed that the contents which eventually ended up in the 'default.cfg' file as used by the pkispawn/pkidestroy framework would need to support Java-based Tomcat PKI subsystems (CA, KRA, OCSP, and TKS), as well as native-based Apache PKI subsystems (RA, TPS).
Since that time, TPS is in the late stages of being moved from an Apache-based process to a Tomcat-based process, and the existing RA will continue to utilize the legacy pkicreate/pkiremove framework until such time as it too is re-architected.
Consequently, we should consider:
Proposed Milestone: 10.3
Per CS/DS meeting of 08/04/2014: moving to Milestone 10.2 (August)
NOTE: For the purposes of Dogtag 10.2, at least remove the [Apache] section from 'default.cfg'. However, if removing all of the APACHE-based checks from the python code is not possible in the Dogtag 10.2 timeframe, do not close this bug.
All APACHE-based checks from the python code were removed in the Dogtag 10.2 timeframe; closing this bug.
Checked into 'master':
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue set to the milestone: 10.2 - 08/14 (August)
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/1640
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.