pkispawn should complain if a different subsystem cert nicknames are specified in the config file for shared tomcat instance
Steps to Reproduce:
Install CA with the subsystem cert nickname <instance-name>subsystemcert Install KRA (shared tomcat) with the subsystem cert nickname krasubsystemcert in the config file
Actual results:
pkispawn is successful but no certificate created with nickname krasubsystemcert
Expected results:
pkispawn should complain when a different subsystem cert is specified in the config file.
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1426362
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: 3 - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.
Metadata Update from @mharmsen: - Issue set to the milestone: FUTURE (was: 10.4)
Metadata Update from @mharmsen: - Custom field lowhangingfruit adjusted to vakwetu: X - Issue priority set to: minor (was: major)
Per 10.5.x/10.6 Triage: FUTURE
jmagne: This can be avoided easily, but is nice to have for future.
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/2731
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.