If someone enables/or disables proxy ports post-installation, and pkidestroy reads the current CS.cfg, then the DN in the security domain will likely differ from what is calculated by pkidestroy. The answer to this is to require that the security domain be updated accordingly when proxy ports are enabled. (And maybe even provide a script for that).
Per the Dogtag 10.2.3 meeting of 09/25/2014, the documentation bug PKI TRAC Ticket #1167 - (DOC) if proxy ports are enabled post install, security domain must be updated. was filed and assigned to the 10.2.3 milestone.
proposed Milestone: 10.3 - Per Dogtag 10.2.3 meeting of 09/25/2014
NOTE: This bug may entail creating a script.
Metadata Update from @vakwetu: - 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/1659
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.