2020/07/04 springboot external tomcat http to https

Convert Http of external tomcat of Springboot LAN project to Https

First, you need the keytool tool provided with JDK to generate keys and certificates
Enter in CMD
Keytool -genkey -alias Tomcat -keyalg RSA -keystore/ Server Keystore to get one Keystore file

Enter keystore password:123456
 Enter the new password again:123456
 What is your first and last name?
  [Unknown]:  kaibowang
 What is the name of your organizational unit?
  [Unknown]:  yuxuelian
 What is the name of your organization?
  [Unknown]:  yuxuelian
 What is the name of your city or region?
  [Unknown]:  chengdu
 Your province/city/What is the name of the Autonomous Region?
  [Unknown]:  chengdushi
 The unit's two letter country/What is the area code?
  [Unknown]:  china
CN=kaibowang, OU=yuxuelian, O=yuxuelian, L=chengdu, ST=chengdushi, C=china Correct?
  [no]:  y

input <tomcat> Key password for
        (If the password is the same as the keystore password, Press enter):
Enter the new password again:

JKS The keystore uses a proprietary format. Recommended use "keytool -importkeystore -srckeystore C:\Users\Administrator\.keystore -destkeystore C:\Users\Administrator\.keystore -deststoretype pkcs12" Migrate to industry standard format PKCS12. 

Open eclipse, start setting tomcat, and remove the checked Automatically publish when starting servers in Window → Preferences → Server → Launching

Then change the Server folder in the eclipse working directory, where there is a Server XML (remember to back up the original file first), and modify the content to

<?xml version="1.0" encoding="UTF-8"?>
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at


  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  See the License for the specific language governing permissions and
  limitations under the License.
<!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
<Server port="8006" shutdown="SHUTDOWN">
  <Listener className="org.apache.catalina.startup.VersionLoggerListener" />
  <!-- 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" />
  <!-- 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
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    <Resource name="UserDatabase" auth="Container"
              description="User database that can be updated and saved"
              pathname="conf/tomcat-users.xml" />

  <!-- 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
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
    <Connector port="8080" protocol="HTTP/1.1"
               redirectPort="443" />
    <!-- A "Connector" using the shared thread pool-->
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               redirectPort="8443" />
    <!-- Define an SSL/TLS HTTP/1.1 Connector on port 8443
         This connector uses the NIO implementation. The default
         SSLImplementation will depend on the presence of the APR/native
         library and the useOpenSSL attribute of the
         Either JSSE or OpenSSL style configuration may be used regardless of
         the SSLImplementation selected. JSSE style configuration is used below.
<Connector port="443" protocol="HTTP/1.1" connectionTimeout="20000" maxThreads="150" 
         SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS"
       keystoreFile="C:\Users\Raeky_Chou\.keystore" keystorePass="9191317"/>
    <!-- Define an SSL/TLS HTTP/1.1 Connector on port 8443 with HTTP/2
         This connector uses the APR/native implementation which always uses
         OpenSSL for TLS.
         Either JSSE or OpenSSL style configuration may be used. OpenSSL style
         configuration is used below.
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11AprProtocol"
               maxThreads="150" SSLEnabled="true" >
        <UpgradeProtocol className="org.apache.coyote.http2.Http2Protocol" />
            <Certificate certificateKeyFile="conf/localhost-rsa-key.pem"
                         type="RSA" />

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector 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"

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


Tomcat server XML must be configured with two connectors, one http and one https. If you configure Tomcat to start with eclipse or idea, you can only modify the port numbers of those two. The port priority is for the development tool, and the other data priority is to read the server of Tomcat XML, only the port will be overwritten. If you do not want to access http, set the server Delete the http connector in the XML (then set the configured http port in the Tomcat of eclipse to null, and http cannot be accessed. If you want to use http, keep it. If you don't need it, delete it. Moreover, ClientAuth is the key. If this is filled in as false, there is no difference between http and https. If you change it to true, you need a certificate.)

Then double-click tomcat in Servers. Before double clicking, remember to remove all the previously imported projects, and then select the second one from the Server Locations option. This is for me to test whether I can open the tomcat home page.

Finally, change the server XML, and then copy it to the server The contents of XML are copied in.

Then start the project. In case of an error, look carefully at the output content in the console. Most of the errors are caused by port occupation. Use CMD to find out what process occupies the port, For example, the command netstat -ano | findstr "8005" "tasklist | findstr" 3228 "taskkill /f /t /im javaw.exe, or directly change the port numbers in the two server.xml. I use 443 because it is convenient to fill in the port numbers when you do not need to enter the web address.

Such a project is successfully converted from http to https

Tags: Java Tomcat SSL

Posted by ranbla on Thu, 02 Jun 2022 09:27:36 +0530