When a wrong subsystem cert nickname is provided in the pkispawn input file for a shared tomcat instance, it should error out.
Steps to Reproduce:
1. pkispwan a CA instance with pki_subsystem_nickname=casubsystemcert # certutil -L -d /var/lib/pki/pki-master/alias/ | grep casubsystemcert casubsystemcert u,u,u 2. pkispawn a kra instance in the shared tomcat with an in-correct subsystem cert nickname, pki_subsystem_nickname=kra3subsystemcert
Actual results:
pkispawn is successful. CS.cfg has: cloning.subsystem.nickname=kra3subsystemcert kra.cert.subsystem.nickname=casubsystemcert
Expected results:
pkispawn should error out with a message that nickname kra3subsystemcert is not found.
Additional info:
The same problem persist for ocsp and tks as well. pkispawn of TPS subsystem fails to install and throws following correct error message when wrong nickname is provided. ConfigurationUtils: getSubsystemCert: nickname=tps1subsystemcert org.mozilla.jss.crypto.ObjectNotFoundException
Metadata Update from @aakkiang: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field lowhangingfruit adjusted to vakwetu: X - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue priority set to: minor (was: major) - Issue set to the milestone: FUTURE (was: UNTRIAGED)
Per 10.5.x/10.6 Triage: FUTURE
RHBZ: CLOSED UPSTREAM
Metadata Update from @mharmsen: - Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1377860)
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/2597
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.