While testing Dogtag 10.0.2, it was noticed that whenever a CA, KRA, OCSP, or TKS subsystem was started using 'systemctl start pki-tomcatd@.service', JSS would throw an exception that appeared in the '/var/log/pki//catalina.out' file:
The following two versions of JSS both displayed this behavior on 32-bit i686 Fedora 18:
It was also reported that this behavior also occurred on 64-bit x86_64 Fedora 18 using the following version of JSS:
This problem is caused by missing 'clientauth' parameter (not clientAuth) in the element in server.xml.
I think this might be the tomcatjss bug I found earlier: Bug 1058366 - NullPointerException in tomcatjss searching for attribute "clientauth"
Proposed Milestone: 10.2.1 (per CS Meeting of 09/17/2014)
cfu to close based upon status of Bugzilla Bug #1058366 - NullPointerException in tomcatjss searching for attribute "clientauth".
I'm pretty sure that this has been fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1058366
Metadata Update from @mharmsen: - Issue assigned to cfu - Issue set to the milestone: 10.2.1
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/1179
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.