-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.9.1
-
None
-
5
-
Severity 3 - Minor
-
0
-
Problem
In Running Confluence over SSL or HTTPS, under Step 2. Modify your Confluence server.xml file, the example config uses sslProtocols incorrectly:
<Connector port="8443" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" protocol="org.apache.coyote.http11.Http11NioProtocol" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" sslProtocols="TLSv1,TLSv1.1,TLSv1.2" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" SSLEnabled="true" URIEncoding="UTF-8" keystorePass="<MY_CERTIFICATE_PASSWORD>"/>
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
sslProtocols is not necessary and should be removed from the example. Using only sslEnabledProtocols is enough.
- is cloned from
-
JRASERVER-66168 Documentation regarding configuring SSL uses wrong attribute in example config
- Closed