-
Bug
-
Resolution: Fixed
-
Low
-
7.5.0, 7.5.1
-
None
-
7.05
-
Severity 3 - Minor
-
Problem
In Running JIRA applications over SSL or HTTPS, under Command Line Installation -> Step 2. Update Tomcat with the KeyStore, the example config uses sslProtocol incorrectly:
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" maxHttpHeaderSize="8192" SSLEnabled="true" maxThreads="150" minSpareThreads="25" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" sslEnabledProtocols="TLSv1.2,TLSv1.3" clientAuth="false" sslProtocol="TLSv1.2,TLSv1.3" useBodyEncodingForURI="true" keyAlias="jira" keystoreFile="<JIRA_HOME>/jira.jks" keystorePass="changeit" keystoreType="JKS"/>
This attribute shouldn't accept multiple values.
Configuring as above makes the Connector fail to start: JIRA's Tomcat SSL Connector fails to start with SSLContext not available.
Suggested Fix
sslProtocol is not necessary and should be removed from the example. Using only sslEnabledProtocols is good enough.
- was cloned as
-
CONFSERVER-55884 Documentation regarding configuring SSL uses wrong attribute in example config
- Gathering Impact