Some certificates may be overwritten if multiple subsystems are deployed to the same instance because of conflicting certificate nicknames.
The default certificate nicknames contain the certificate type and the instance name, for example:
These default nicknames will be identical for all subsystems, so subsequent deployment may overwrite existing certificates.
The default nicknames should be changed to include the subsystem name. Also the deployment code should check to make sure it doesn't overwrite existing certificates.
One thing that I noticed that once all of the certificates are in the database, it would be nice for all of them (with the exception of the lone Server-Cert) to append the PKI subsystem that they are associated with for consistency and readability.
For example, although I know that the storage and transport certs are associated with the DRM, it would be nice if that subsystem were attached to their nicknames.
Checkin for change:
db9537d210a20b90115374e5b406db6c9658bc3a
Metadata Update from @edewata: - Issue assigned to vakwetu - Issue set to the milestone: 10.0.0-0.X.rc1
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/956
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.