Bug 1058366

Summary: NullPointerException in tomcatjss searching for attribute "clientauth"
Product: Red Hat Enterprise Linux 7 Reporter: Nathan Kinder <nkinder>
Component: tomcatjssAssignee: Christina Fu <cfu>
Status: CLOSED ERRATA QA Contact: Asha Akkiangady <aakkiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: cfu, edewata, jdennis, kwright, mharmsen, rpattath
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tomcatjss-7.1.0-5.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1052417
: 1190911 (view as bug list) Environment:
Last Closed: 2015-03-05 11:28:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1052417    
Bug Blocks: 1190911    

Description Nathan Kinder 2014-01-27 16:24:34 UTC
+++ This bug was initially created as a clone of Bug #1052417 +++

This was discovered when debug is turned on.  

tomcatjss always throws NullPointerException in its init() function when starting up. Investigation shows that it's looking for the attribute "clientauth" (all lower case) and by default (in server.xml) if you don't have it, it does not handle it but instead let it fall through. 
This resulted in important things not be called such as
* enableOCSP
* eanble certain SSL ciphers

Comment 2 Christina Fu 2014-10-01 17:06:59 UTC
Testing suggestion:
To test this bug fix, here is one suggestion:
in server.xml
make sure "clientauth" (all lower case) is not there (which would cause NullPointerException without this fix)
make debug="true"
enable ocsp (follow the instruction in the server.xml)

restart server and you will see from /tmp/tomcatjss.log that
1. the ocsp is enabled etc. and
2. should not see any NullPointerException.

Or, you can go all out and test to see of ocsp is indeed working ... but I think observing the /tmp/tomcatjss.log should be sufficient.

Comment 3 Roshni 2014-11-06 14:09:34 UTC
Verified by executing the steps described in comment 2.

Comment 5 errata-xmlrpc 2015-03-05 11:28:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0522.html