#222 Dogtag 10: Scrub 'pkicreate'/'pkiremove' entries from CS.cfg
Closed: duplicate Opened by mharmsen.

Since 'pkicreate'/'pkiremove' are being replaced by 'pkispawn'/'pkidestroy' respectively, scrub the values that are associated with the former from 'CS.cfg'.

For Dogtag 10: post-Alpha, this initially needs to include the 'CS.cfg' files for CA, KRA, OCSP, and TKS. Eventually, this will need to include the 'CS.cfg' files for RA and TPS, as well.


[06/04/2014] - Moving to Milestone 10.3 due to schedule restrictions.

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

This old ticket has been closed as a duplicate of the more comprehensive ticket:
* https://pagure.io/dogtagpki/issue/3047

Metadata Update from @mharmsen:
- 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: duplicate
- Issue status updated to: Closed (was: Open)

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

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