Originally, the location of a serverCertNick.conf template was defined in default.cfg:
[DEFAULT] pki_source_server_path=/usr/share/pki/server/conf [Tomcat] pki_source_servercertnick_conf=%(pki_source_server_path)s/serverCertNick.conf
and contained the following single line:
[PKI_SSL_SERVER_NICKNAME]
This template was copied via the slot_substitution.py scriptlet during pkidaemon installation to its selected place within an instance:
deployer.file.copy_with_slot_substitution( deployer.mdict['pki_source_servercertnick_conf'], deployer.mdict['pki_target_servercertnick_conf'], overwrite_flag=True)
During the course of correcting PKI TRAC Ticket #1370 - pkispawn: installation with HSM from external CA should hold off prepending token name in serverCertNick.conf till phase 2 for Dogtag 10.2.4, it was determined that under certain circumstances, the value contained within this file would differ between scenarios which required a two-pass installation (e. g. - an HSM using an External CA). To fix this issue, a new ServerCertNickConf Python class was created and called during the finalization.py scriptlet.
This ticket proposes consolidating all of this various logic, encapsulating it within the ServerCertNickConf class, and re-factoring the pkidaemon installation code to utilize these methods.
Proposed Milestone: 10.2.5
As I feel that this is not urgent, and is not as critical as man page/documentation in the 10.2.X lifecycle, I am moving this ticket to 10.3.
Metadata Update from @mharmsen: - Issue assigned to mharmsen - 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/1941
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)