pkispawn KRA subsystem with SSL Directory Server shows confusing root cert nicknames.
Steps to Reproduce:
1. Setup a Directory Server SSL instance with the self signed CA cert. 2. pkispawn a CA subsystem using SSL DS. 3. Configure DS SSL instance to be trusted by issuing DS server certificate by newly created CA. 4. pkispawn KRA instance via two step process using externally issued CMC certs. The nickname for DS SSL certificate (pki_ds_secure_connection_ca_nickname) is not provided in the pkispawn config file. The second step of KRA installation shows message: * "Imported certificate "Directory Server CA certificate" More details are contained in the associated bug.
Actual results:
KRA installation is successful. Verbose mode shows message "Imported certificate "Directory Server CA certificate". Looks like DS Cert is imported first with the default nickname "Directory Server CA certificate". When other pkcs7 is imported, since DS cert is the root CA cert, it kept the nickname of root cert that was initially imported with, i.e "Directory Server CA certificate". Probably the code did not care about the nickname.
Expected results:
While importing pkcs7 the root certificate nickname should be the one auto generated from the subject DN.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1541499 - Custom field type adjusted to None - Custom field version adjusted to None
Per 10.5.x/10.6 Triage: 10.6
edewata: install works, but the log is misleading
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Might be related to IPA issue: https://pagure.io/freeipa/issue/7516
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/3043
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.