We store the nicknames of the system certs all over the place in CS.cfg. This makes it difficult to change a nickname and makes for overly complicated installation code. Its further complicated because some of the entries have token: attached and some do not.
For example, in the CA:
[root@alee-workpc alias]# grep nickname /etc/pki-ca22/CS.cfg ca.audit_signing.nickname=auditSigningCert testca ca.cert.audit_signing.nickname=auditSigningCert testca ca.cert.ocsp_signing.nickname=ocspSigningCert testca ca.cert.signing.nickname=signingCert testca ca.cert.sslserver.nickname=sslServerCert testca ca.cert.subsystem.nickname=subsystemCert testca ca.ocsp_signing.cacertnickname=ocspSigningCert testca ca.ocsp_signing.certnickname=ocspSigningCert testca ca.ocsp_signing.nickname=ocspSigningCert testca ca.signing.cacertnickname=signingCert testca ca.signing.certnickname=signingCert testca ca.signing.nickname=signingCert testca ca.sslserver.nickname=sslServerCert testca ca.subsystem.nickname=subsystemCert testca cloning.audit_signing.nickname=auditSigningCert testca cloning.ocsp_signing.nickname=ocspSigningCert testca cloning.signing.nickname=signingCert testca cloning.subsystem.nickname=subsystemCert testca pkiremove.cert.subsystem.nickname=subsystemCert cert-pki-ca22 selftests._006=## ca.cert.<cert tag name>.nickname
This is sheer madness! We need a single nickname for each subsystem cert.
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/734
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.