The server certificate nickname is hard-coded in various locations as follows:
Server-Cert cert-[PKI_INSTANCE_ID]
Sometimes it's necessary to use a different nickname, but the above configuration doesn't allow much flexibility.
For example IPA configures the CA as follows:
config.set("CA", "pki_ssl_server_nickname", "Server-Cert cert-pki-ca")
The problem is the instance name is actually pki-tomcat, and for some reason it creates a problem when configuring additional subsystem.
A possible solution is to replace all occurences with pki_ssl_server_nickname parameter.
master: 2b1efa0fa66b247ae0b1e4c605f1ed8290bd7a08
10.0 branch: 7a514e40ddf2a34cfa098770dea634e87110bd6d
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.0.3
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/1201
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.
Login to comment on this ticket.