Description of problem:
When a wrong subsystem cert nickname is provided in the pkispawn input file for a shared tomcat instance, it should error out.

Version-Release number of selected component (if applicable):
pki-server-10.3.3-10.el7

How reproducible:


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