Tomcat 7 SSL Failed

Question

I use Tomcat 7 and will enable the SSL Connector. Actuall i have edit this solution to the server.xml file:

Answer 1

You can not use a keystore if you are using the APR connector. It requires the same certificate formats as used by Apache.

EDIT: if you are running either Debian or Ubuntu on Linux you can use the ssl-cert package to generate a self-signed cert that would work with the APR connector as documented at http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Edit_the_Tomcat_Configuration_File (scroll down to the APR section).

EDIT: Try this as your server.xml file. I removed some of the comments and commented out the APR listener. Your keystore should work now.

<?xml version='1.0' encoding='utf-8'?>
<Server port="8005" shutdown="SHUTDOWN">
  <!-- Security listener. Documentation at /docs/config/listeners.html
  <Listener className="org.apache.catalina.security.SecurityListener" />
  -->
  <!--APR library loader. Documentation at /docs/apr.html -->
  <!-- <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> -->
  <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
  <Listener className="org.apache.catalina.core.JasperListener" />
  <!-- Prevent memory leaks due to use of particular java/javax APIs-->
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

  <!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  -->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container", 
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   -->
  <Service name="Catalina">

    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" 
        maxThreads="150" minSpareThreads="4"/>
    -->


    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    -->
    <Connector port="8080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1" 
               connectionTimeout="20000" 
               redirectPort="8443" />
    -->           
    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the 
         connector should be using the OpenSSL style configuration
         described in the APR documentation -->

<!--
    <Connector  port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                maxThreads="150" scheme="https" secure="true"
                clientAuth="false" sslProtocol="TLS" />
 -->

 <Connector
   clientAuth="true" port="8443" minSpareThreads="5" maxSpareThreads="75"
   enableLookups="true" disableUploadTimeout="true"
   acceptCount="100" maxThreads="200"
   scheme="https" secure="true" SSLEnabled="true"
   keystoreFile="${catalina.home}/conf/server.jks"
   keystoreType="JKS" keystorePass="password"
   truststoreFile="${catalina.home}/conf/server.jks"
   truststoreType="JKS" truststorePass="password"
   SSLVerifyClient="require" SSLEngine="on" SSLVerifyDepth="2" sslProtocol="TLS"
/>

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />


    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">         
    --> 
    <Engine name="Catalina" defaultHost="localhost">

      <!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) -->
      <!--
      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
      -->        

      <!-- Use the LockOutRealm to prevent attempts to guess user passwords
           via a brute-force attack -->
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <!-- This Realm uses the UserDatabase configured in the global JNDI
             resources under the key "UserDatabase".  Any edits
             that are performed against this UserDatabase are immediately
             available for use by the Realm.  -->
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
               resourceName="UserDatabase"/>
      </Realm>

      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">

        <!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all example.
             Documentation at: /docs/config/valve.html
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"  
               prefix="localhost_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" resolveHosts="false"/>

      </Host>
    </Engine>
  </Service>
</Server>

Answer 2

There are two ways to implement SSL on TOMCAT

(APR implementation of SSL and JSSE implementation of SSL)

The difference is that the JDK is using it's own SSL implementation, while the APR it's using what's installed on the computer, i.e. OpenSSL in most cases.

First way (jSSE) using java

1. Creating a Keystore file

   (windows-os) in comand prompet cmd [cd $JAVA_HOME/bin]

   keytool -genkey -alias tomcat -keyalg RSA
   

2. (Configuring Tomcat's SSL Connectors) in (..\Tomcat 8.0\conf\server.xml)

<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
 scheme="https" URIEncoding="UTF-8"sslProtocol="TLS"keystorePass="yourPassword"
keystoreFile="locationofkeystorefile" keyAlias="youralias" clientAuth="false" />

Second way (ARP) using openssl

1. Creating a Keystore file using Java

2. (Configuring Tomcat's SSL Connectors) in (..\Tomcat 8.0\conf\server.xml)

<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on"  />

<Connector protocol="org.apache.coyote.http11.Http11AprProtocol"
port="8443" clientAuth="false" sslProtocol="TLS"
SSLEnabled="true" maxThreads="150" scheme="https" secure="true"
SSLCertificateFile="/tmp/monitoringPortalCert.pem"
SSLCertificateKeyFile="/tmp/monitoringPortalKey.pem"
SSLPassword="hide"/>

Useful URLs:

http://java.dzone.com/articles/setting-ssl-tomcat-5-minutes

http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html

Answer 3

8443 port in Tomcat is by default used for SSL connection.

I suggest you see tomcat documentation for SSL:
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html

There is one more link that I found which could resolve your issue in no time:
http://java.dzone.com/articles/setting-ssl-tomcat-5-minutes This is an amazing article. Please go through to resolve the issue. Hope this helps !

Answer 4

comment out this line:

<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> 

Answer 5

Disable Auto-Switching

There's a bit of a mean automatic mechanism at work here. I recommend you disable that and EXPLICTLY select your desired connector. Details below.

Details

You have your connector configured like so:

<Connector  port="8443" protocol="HTTP/1.1"

The important parameter here is the "protocol" part. The Tomcat 7 documentation says this: (line breaks mine)

protocol

Sets the protocol to handle incoming traffic.

The default value is HTTP/1.1 which uses an auto-switching mechanism to select either a blocking Java based connector or an APR/native based connector.

If the PATH (Windows) or LD_LIBRARY_PATH (on most unix systems) environment variables contain the Tomcat native library, the APR/native connector will be used.

If the native library cannot be found, the blocking Java based connector will be used. Note that the APR/native connector has different settings for HTTPS than the Java connectors.

[...]

So it seems that auto-switching is being used and it doesn't work. And the reason is give in the final paragraph above: we're auto-switching and end up with the "APR" connector.

So then this happens:

1. APR connector has mandatory parameter called SSLCertificateFile.
2. We have NOT supplied that parameter inside server.xml.
3. Tomcat complains about that missing parameter.

Options

So in order to fix this you have several options:

• Turn auto-switching off replace the "HTTP/1.1" text by your desired connector.
• Leave auto-switching on and fix it. By adding the required parameter to server.xml.
• Leave auto-switching on and break it on purpose. By simply deleting "tomcat\bin\tcnative-1.dll". This will trigger the section mentioned above after If the native library cannot be found. This is a bit of a dirty solution. And I'm mentioning this here not because I think this is a great idea. But because I happened to find that this had been done on one of our Development Tomcat machines.