The current CS.cfg contains the cert requests of the subsystem certificates. The cert requests are actually also stored in the database, so the copies in the CS.cfg are redundant.
To remove redundancy, the cert requests should be obtained directly from the database. There should be an interface to find the cert request of a given cert, for example:
$ pki <agent auth> ca-cert-request-find --cert cert.pem
Once the new interface is implemented, all codes should be converted incrementally to use the interface. Once everything is converted, the redundant cert requests can be removed from CS.cfg.
Per CS/DS Meeting of 08/17/2015 - 10.3
See also ticket #1598.
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/2111
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.