dogtagpki

#299 Tomcat JSS ignores clientAuth setting
Closed: migrated by dmoluguw. Opened by edewata.

Closed: migrated
Reopen Issue

Tomcat 7 JSS does not read the clientAuth setting correctly from server.xml.

The code JSSSocketFactory.java:405-407 will always produce a null value.

// MUST look for "clientauth" (ALL lowercase) since "clientAuth"
// (camel case) has already been processed by Tomcat 7
String clientAuthStr = (String)endpoint.getAttribute("clientauth");

The correct way should be:

String clientAuthStr = endpoint.getClientAuth();

Note that this change will have a side effect. Previously when a user opens the EE page via SSL the server will not prompt for the client certificate. After fixing this the server will prompt for client certificate since the clientAuth is set to "want".

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: UNTRIAGED

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/870

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)
Metadata
None
None
None
Normal
defect
Auth
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.