Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65888

JIRA SSL Documentation Refers to Invalid Tomcat Parameter

    XMLWordPrintable

Details

    Description

      While working a support case we noticed that the example on Running JIRA applications over SSL or HTTPS has a typo. Step 2 of Step 2. Update Tomcat with the KeyStore contains the example connector:

      <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"
              sslEnabledProtocol="TLSv1.2,TLSv1.3"
              clientAuth="false" sslProtocol="TLSv1.2,TLSv1.3" useBodyEncodingForURI="true"
              keyAlias="jira" keystoreFile="<JIRA_HOME>/jira.jks" keystorePass="changeit" keystoreType="JKS"/>

      however sslEnabledProtocol is not a valid Tomcat connector attribute, it should read sslEnabledProtocols, as it does in the examples below. If a customer copies this over directly, they can get errors initializing Tomcat, so we should correct this ASAP.

      Attachments

        Activity

          People

            tbartyzel Tomasz Bartyzel
            agallien@atlassian.com Alex Gallien
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: