The cacertnickname property in CS.cfg has been deprecated and replaced with certnickname. However, both of these properties are used and sometimes inconsistently, which may cause an error.
For example, the updateConfig() in CASigningCert.java and OCSPSigningCert.java update the cacertnickname property without updating certnickname, but the SigningUnit.getNickname() reads the certnickname first if it exists, so it may not read the new cacertnickname value.
Proposed solution:
Proposed milestone: 10.3
Per CS/DS Meeting of 09/14/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/2162
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.