Currently the CS.cfg contains a lot of properties which can be hard to manage. Many of these properties are not meant to be user-configurable or very unlikely to change. These properties can be moved into a default system-wide configuration file (similar to /etc/pki/default.cfg) such that the only properties stored in each instance are the ones customized by the admin, which should not be too many.
Proposed milestone: 10.3
Per Dogtag 10.2.X TRIAGE meeting of 04/28/2015: 10.3
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/1917
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.