Apache Tomcat 8 SSL

11/11/2015
ApacheTomcat8(8.0.28)SSL/TLSConfigurationHOWTO
Apache Tomcat 8
Version 8.0.28, Oct 7 2015
SSL/TLS Configuration HOW-TO

Table of Contents
Quick Start
Introduction to SSL/TLS
SSL/TLS and Tomcat
Certificates
General Tips on Running SSL
Configuration
1. Prepare the Certificate Keystore
2. Edit the Tomcat Configuration File
Installing a Certificate from a Certificate Authority
1. Create a local Certificate Signing Request (CSR)
2. Importing the Certificate
Troubleshooting
Using the SSL for session tracking in your application
Miscellaneous Tips and Bits
Quick Start
The description below uses the variable name $CATALINA_BASE to refer the base directory against
which most relative paths are resolved. If you have not configured Tomcat for multiple instances by
setting a CATALINA_BASE directory, then $CATALINA_BASE will be set to the value of $CATALINA_HOME,
the directory into which you have installed Tomcat.
To install and configure SSL/TLS support on Tomcat, you need to follow these simple steps. For
more information, read the rest of this HOW-TO.
1. Create a keystore file to store the server's private key and self-signed certificate by
executing the following command:
Windows:
"%JAVA_HOME%\bin\keytool"genkeyaliastomcatkeyalgRSA
Unix:
$JAVA_HOME/bin/keytoolgenkeyaliastomcatkeyalgRSA
and specify a password value of "changeit".
2. Uncomment the "SSL HTTP/1.1 Connector" entry in $CATALINA_BASE/conf/server.xml
and modify as described in the Configuration section below.
Introduction to SSL/TLS
https://tomcat.apache.org/tomcat8.0doc/sslhowto.html
1/11
11/11/2015
Transport Layer Security (TLS) and its predecessor, Secure Sockets Layer (SSL), are technologies
which allow web browsers and web servers to communicate over a secured connection. This
means that the data being sent is encrypted by one side, transmitted, then decrypted by the
other side before processing. This is a two-way process, meaning that both the server AND the
browser encrypt all traffic before sending out data.
Another important aspect of the SSL/TLS protocol is Authentication. This means that during
your initial attempt to communicate with a web server over a secure connection, that server will
present your web browser with a set of credentials, in the form of a "Certificate", as proof the
site is who and what it claims to be. In certain cases, the server may also request a Certificate
from your web browser, asking for proof that you are who you claim to be. This is known as
"Client Authentication," although in practice this is used more for business-to-business (B2B)
transactions than with individual users. Most SSL-enabled web servers do not request Client
Authentication.
SSL/TLS and Tomcat

It is important to note that configuring Tomcat to take advantage of secure sockets is usually
only necessary when running it as a stand-alone web server. Details can be found in the
Security Considerations Document. When running Tomcat primarily as a Servlet/JSP container
behind another web server, such as Apache or Microsoft IIS, it is usually necessary to configure
the primary web server to handle the SSL connections from users. Typically, this server will
negotiate all SSL-related functionality, then pass on any requests destined for the Tomcat
container only after decrypting those requests. Likewise, Tomcat will return cleartext responses,
that will be encrypted before being returned to the user's browser. In this environment, Tomcat
knows that communications between the primary web server and the client are taking place
over a secure connection (because your application needs to be able to ask about this), but it
does not participate in the encryption or decryption itself.
Certificates
In order to implement SSL, a web server must have an associated Certificate for each external
interface (IP address) that accepts secure connections. The theory behind this design is that a
server should provide some kind of reasonable assurance that its owner is who you think it is,
particularly before receiving any sensitive information. While a broader explanation of
Certificates is beyond the scope of this document, think of a Certificate as a "digital driver's
license" for an Internet address. It states what company the site is associated with, along with
some basic contact information about the site owner or administrator.
This "driver's license" is cryptographically signed by its owner, and is therefore extremely
difficult for anyone else to forge. For sites involved in e-commerce, or any other business
transaction in which authentication of identity is important, a Certificate is typically purchased
from a well-known Certificate Authority (CA) such as VeriSign or Thawte. Such certificates can be
electronically verified -- in effect, the Certificate Authority will vouch for the authenticity of the
certificates that it grants, so you can believe that the Certificate is valid if you trust the
Certificate Authority that granted it.
In many cases, however, authentication is not really a concern. An administrator may simply
want to ensure that the data being transmitted and received by the server is private and cannot
be snooped by anyone who may be eavesdropping on the connection. Fortunately, Java
provides a relatively simple command-line tool, called keytool, which can easily create a "selfsigned" Certificate. Self-signed Certificates are simply user generated Certificates which have
2/11
11/11/2015
not been officially registered with any well-known CA, and are therefore not really guaranteed
to be authentic at all. Again, this may or may not even be important, depending on your needs.
General Tips on Running SSL

The first time a user attempts to access a secured page on your site, he or she is typically
presented with a dialog containing the details of the certificate (such as the company and
contact name), and asked if he or she wishes to accept the Certificate as valid and continue with
the transaction. Some browsers will provide an option for permanently accepting a given
Certificate as valid, in which case the user will not be bothered with a prompt each time they
visit your site. Other browsers do not provide this option. Once approved by the user, a
Certificate will be considered valid for at least the entire browser session.
Also, while the SSL protocol was designed to be as efficient as securely possible,
encryption/decryption is a computationally expensive process from a performance standpoint.
It is not strictly necessary to run an entire web application over SSL, and indeed a developer can
pick and choose which pages require a secure connection and which do not. For a reasonably
busy site, it is customary to only run certain pages under SSL, namely those pages where
sensitive information could possibly be exchanged. This would include things like login pages,
personal information pages, and shopping cart checkouts, where credit card information could
possibly be transmitted. Any page within an application can be requested over a secure socket
by simply prefixing the address with https: instead of http:. Any pages which absolutely
require a secure connection should check the protocol type associated with the page request
and take the appropriate action if https is not specified.
Finally, using name-based virtual hosts on a secured connection can be problematic. This is a
design limitation of the SSL protocol itself. The SSL handshake, where the client browser
accepts the server certificate, must occur before the HTTP request is accessed. As a result, the
request information containing the virtual host name cannot be determined prior to
authentication, and it is therefore not possible to assign multiple certificates to a single IP
address. If all virtual hosts on a single IP address need to authenticate against the same
certificate, the addition of multiple virtual hosts should not interfere with normal SSL
operations on the server. Be aware, however, that most client browsers will compare the
server's domain name against the domain name listed in the certificate, if any (applicable
primarily to official, CA-signed certificates). If the domain names do not match, these browsers
will display a warning to the client user. In general, only address-based virtual hosts are
commonly used with SSL in a production environment.
Configuration
Prepare the Certificate Keystore
Tomcat currently operates only on JKS, PKCS11 or PKCS12 format keystores. The JKS format is
Java's standard "Java KeyStore" format, and is the format created by the keytool commandline utility. This tool is included in the JDK. The PKCS12 format is an internet standard, and can
be manipulated via (among other things) OpenSSL and Microsoft's Key-Manager.
Each entry in a keystore is identified by an alias string. Whilst many keystore implementations
treat aliases in a case insensitive manner, case sensitive implementations are available. The
PKCS11 specification, for example, requires that aliases are case sensitive. To avoid issues
related to the case sensitivity of aliases, it is not recommended to use aliases that differ only
in case.
3/11
11/11/2015
To import an existing certificate into a JKS keystore, please read the documentation (in your
JDK documentation package) about keytool. Note that OpenSSL often adds readable
comments before the key, but keytool does not support that. So if your certificate has
comments before the key data, remove them before importing the certificate with keytool.
To import an existing certificate signed by your own CA into a PKCS12 keystore using OpenSSL
you would execute a command like:
opensslpkcs12exportinmycert.crtinkeymykey.key
outmycert.p12nametomcatCAfilemyCA.crt
canamerootchain
For more advanced cases, consult the OpenSSL documentation.
To create a new JKS keystore from scratch, containing a single self-signed Certificate, execute
the following from a terminal command line:
Windows:
Unix:
(The RSA algorithm should be preferred as a secure algorithm, and this also ensures general
compatibility with other servers and components.)
This command will create a new file, in the home directory of the user under which you run it,
named ".keystore". To specify a different location or filename, add the keystore
parameter, followed by the complete pathname to your keystore file, to the keytool
command shown above. You will also need to reflect this new location in the server.xml
configuration file, as described later. For example:
Windows:
keystore\path\to\my\keystore
Unix:
keystore/path/to/my/keystore
After executing this command, you will first be prompted for the keystore password. The
default password used by Tomcat is "changeit" (all lower case), although you can specify a
custom password if you like. You will also need to specify the custom password in the
server.xml configuration file, as described later.
Next, you will be prompted for general information about this Certificate, such as company,
contact name, and so on. This information will be displayed to users who attempt to access a
secure page in your application, so make sure that the information provided here matches
what they will expect.
4/11
11/11/2015
Finally, you will be prompted for the key password, which is the password specifically for this
Certificate (as opposed to any other Certificates stored in the same keystore file). The
keytool prompt will tell you that pressing the ENTER key automatically uses the same
password for the key as the keystore. You are free to use the same password or to select a
custom one. If you select a different password to the keystore password, you will also need to
specify the custom password in the server.xml configuration file.
If everything was successful, you now have a keystore file with a Certificate that can be used
by your server.
Edit the Tomcat Configuration File
Tomcat can use two different implementations of SSL:
the JSSE implementation provided as part of the Java runtime (since 1.4)
the APR implementation, which uses the OpenSSL engine by default.
The exact configuration details depend on which implementation is being used. If you
configured Connector by specifying generic protocol="HTTP/1.1" then the implementation
used by Tomcat is chosen automatically. If the installation uses APR - i.e. you have installed
the Tomcat native library - then it will use the APR SSL implementation, otherwise it will use
the Java JSSE implementation.
As configuration attributes for SSL support significantly differ between APR vs. JSSE
implementations, it is recommended to avoid auto-selection of implementation. It is done by
specifying a classname in the protocol attribute of the Connector.
To define a Java (JSSE) connector, regardless of whether the APR library is loaded or not, use
one of the following:
<!DefineaHTTP/1.1Connectoronport8443,JSSENIOimplementation>
<Connectorprotocol="org.apache.coyote.http11.Http11NioProtocol"
port="8443".../>
<!DefineaHTTP/1.1Connectoronport8443,JSSENIO2implementation>
<Connectorprotocol="org.apache.coyote.http11.Http11Nio2Protocol"
port="8443".../>
<!DefineaHTTP/1.1Connectoronport8443,JSSEBIOimplementation>
<Connectorprotocol="org.apache.coyote.http11.Http11Protocol"
port="8443".../>
Alternatively, to specify an APR connector (the APR library must be available) use:
<!DefineaHTTP/1.1Connectoronport8443,APRimplementation>
<Connectorprotocol="org.apache.coyote.http11.Http11AprProtocol"
port="8443".../>
If you are using APR, you have the option of configuring an alternative engine to OpenSSL.
<ListenerclassName="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="someengine"SSLRandomSeed="somedevice"/>
The default value is
5/11
11/11/2015
<ListenerclassName="org.apache.catalina.core.AprLifecycleListener"
SSLEngine="on"SSLRandomSeed="builtin"/>
So to use SSL under APR, make sure the SSLEngine attribute is set to something other than
off. The default value is on and if you specify another value, it has to be a valid engine name.
SSLRandomSeed allows to specify a source of entropy. Productive system needs a reliable
source of entropy but entropy may need a lot of time to be collected therefore test systems
could use no blocking entropy sources like "/dev/urandom" that will allow quicker starts of
Tomcat.
The final step is to configure the Connector in the $CATALINA_BASE/conf/server.xml file,
where $CATALINA_BASE represents the base directory for the Tomcat instance. An example
<Connector> element for an SSL connector is included in the default server.xml file installed
with Tomcat. To configure an SSL connector that uses JSSE, you will need to remove the
comments and edit it so it looks something like this:
<!DefineaSSLCoyoteHTTP/1.1Connectoronport8443>
<Connector
protocol="org.apache.coyote.http11.Http11NioProtocol"
port="8443"maxThreads="200"
scheme="https"secure="true"SSLEnabled="true"
keystoreFile="${user.home}/.keystore"keystorePass="changeit"
clientAuth="false"sslProtocol="TLS"/>
The APR connector uses different attributes for many SSL settings, particularly keys and
certificates. An example of an APR configuration is:
<Connector
protocol="org.apache.coyote.http11.Http11AprProtocol"
SSLCertificateFile="/usr/local/ssl/server.crt"
SSLCertificateKeyFile="/usr/local/ssl/server.pem"
SSLVerifyClient="optional"SSLProtocol="TLSv1+TLSv1.1+TLSv1.2"/>
The configuration options and information on which attributes are mandatory, are
documented in the SSL Support section of the HTTP connector configuration reference. Make
sure that you use the correct attributes for the connector you are using. The BIO, NIO and
NIO2 connectors use JSSE whereas the APR/native connector uses APR.
The port attribute is the TCP/IP port number on which Tomcat will listen for secure
connections. You can change this to any port number you wish (such as to the default port for
https communications, which is 443). However, special setup (outside the scope of this
document) is necessary to run Tomcat on port numbers lower than 1024 on many operating
systems.
If you change the port number here, you should also change the value specified for the
redirectPort attribute on the non-SSL connector. This allows Tomcat to automatically redirect
users who attempt to access a page with a security constraint specifying that SSL is required, as
required by the Servlet Specification.
After completing these configuration changes, you must restart Tomcat as you normally do,
6/11
11/11/2015
and you should be in business. You should be able to access any web application supported
by Tomcat via SSL. For example, try:
https://localhost:8443/
and you should see the usual Tomcat splash page (unless you have modified the ROOT web
application). If this does not work, the following section contains some troubleshooting tips.
Installing a Certificate from a Certificate Authority

To obtain and install a Certificate from a Certificate Authority (like verisign.com, thawte.com or
trustcenter.de), read the previous section and then follow these instructions:
Create a local Certificate Signing Request (CSR)
In order to obtain a Certificate from the Certificate Authority of your choice you have to
create a so called Certificate Signing Request (CSR). That CSR will be used by the Certificate
Authority to create a Certificate that will identify your website as "secure". To create a CSR
follow these steps:
Create a local self-signed Certificate (as described in the previous section):
keytoolgenkeyaliastomcatkeyalgRSA
keystore<your_keystore_filename>
Note: In some cases you will have to enter the domain of your website (i.e.
www.myside.org) in the field "first- and lastname" in order to create a working
Certificate.
The CSR is then created with:
keytoolcertreqkeyalgRSAaliastomcatfilecertreq.csr
keystore<your_keystore_filename>
Now you have a file called certreq.csr that you can submit to the Certificate Authority (look
at the documentation of the Certificate Authority website on how to do this). In return you get
a Certificate.
Importing the Certificate
Now that you have your Certificate you can import it into you local keystore. First of all you
have to import a so called Chain Certificate or Root Certificate into your keystore. After that
you can proceed with importing your Certificate.
Download a Chain Certificate from the Certificate Authority you obtained the Certificate
from.
For Verisign.com commercial certificates go to:
http://www.verisign.com/support/install/intermediate.html
For Verisign.com trial certificates go to: http://www.verisign.com/support/verisignintermediate-ca/Trial_Secure_Server_Root/index.html
For Trustcenter.de go to:
http://www.trustcenter.de/certservices/cacerts/en/en.htm#server
For Thawte.com go to: http://www.thawte.com/certs/trustmap.html
7/11
11/11/2015
Import the Chain Certificate into your keystore

keytoolimportaliasrootkeystore<your_keystore_filename>
trustcacertsfile<filename_of_the_chain_certificate>
And finally import your new Certificate
keytoolimportaliastomcatkeystore<your_keystore_filename>
file<your_certificate_filename>
Troubleshooting
Here is a list of common problems that you may encounter when setting up SSL
communications, and what to do about them.
When Tomcat starts up, I get an exception like "java.io.FileNotFoundException: {somedirectory}/{some-file} not found".
A likely explanation is that Tomcat cannot find the keystore file where it is looking. By
default, Tomcat expects the keystore file to be named .keystore in the user home
directory under which Tomcat is running (which may or may not be the same as yours :-).
If the keystore file is anywhere else, you will need to add a keystoreFile attribute to the
<Factory> element in the Tomcat configuration file.
When Tomcat starts up, I get an exception like "java.io.FileNotFoundException: Keystore
was tampered with, or password was incorrect".
Assuming that someone has not actually tampered with your keystore file, the most likely
cause is that Tomcat is using a different password than the one you used when you
created the keystore file. To fix this, you can either go back and recreate the keystore file,
or you can add or update the keystorePass attribute on the <Connector> element in the
Tomcat configuration file. REMINDER - Passwords are case sensitive!
When Tomcat starts up, I get an exception like "java.net.SocketException: SSL handshake
error javax.net.ssl.SSLException: No available certificate or key corresponds to the SSL
cipher suites which are enabled."
A likely explanation is that Tomcat cannot find the alias for the server key within the
specified keystore. Check that the correct keystoreFile and keyAlias are specified in
the <Connector> element in the Tomcat configuration file. REMINDER - keyAlias values
may be case sensitive!
My Java-based client aborts handshakes with exceptions such as
"java.lang.RuntimeException: Could not generate DH keypair" and
"java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64,
and can only range from 512 to 1024 (inclusive)"
If you are using the APR/native connector, starting with version 1.1.34 it will determine
the strength of ephemeral DH keys from the key size of your RSA certificate. For example
a 2048 bit RSA key will result in using a 2048 bit prime for the DH keys. Unfortunately Java
6 only supports 768 bit and Java 7 only supports 1024 bit. So if your certificate has a
stronger key, old Java clients might produce such handshake failures. As a mitigation you
can either try to force them to use another cipher by configuring an appropriate
8/11
11/11/2015
SSLCipherSuite and activate SSLHonorCipherOrder, or embed weak DH params in your

certificate file. The latter approach is not recommended because it weakens the SSL
security (logjam attack).
If you are still having problems, a good source of information is the TOMCAT-USER mailing list.
You can find pointers to archives of previous messages on this list, as well as subscription and
unsubscription information, at http://tomcat.apache.org/lists.html.
Using the SSL for session tracking in your application

This is a new feature in the Servlet 3.0 specification. Because it uses the SSL session ID
associated with the physical client-server connection there are some limitations. They are:
Tomcat must have a connector with the attribute isSecure set to true.
If SSL connections are managed by a proxy or a hardware accelerator they must populate
the SSL request headers (see the SSLValve) so that the SSL session ID is visible to Tomcat.
If Tomcat terminates the SSL connection, it will not be possible to use session replication
as the SSL session IDs will be different on each node.
To enable SSL session tracking you need to use a context listener to set the tracking mode for
the context to be just SSL (if any other tracking mode is enabled, it will be used in preference). It
might look something like:
packageorg.apache.tomcat.example;
importjava.util.EnumSet;
importjavax.servlet.ServletContext;
importjavax.servlet.ServletContextEvent;
importjavax.servlet.ServletContextListener;
importjavax.servlet.SessionTrackingMode;
publicclassSessionTrackingModeListenerimplementsServletContextListener{
@Override
publicvoidcontextDestroyed(ServletContextEventevent){
//Donothing
}
@Override
publicvoidcontextInitialized(ServletContextEventevent){
ServletContextcontext=event.getServletContext();
EnumSet<SessionTrackingMode>modes=
EnumSet.of(SessionTrackingMode.SSL);
context.setSessionTrackingModes(modes);
}
}
Note: SSL session tracking is implemented for the BIO, NIO and NIO2 connectors. It is not yet
implemented for the APR connector.
Miscellaneous Tips and Bits

9/11
11/11/2015
To access the SSL session ID from the request, use:

StringsslID=(String)request.getAttribute("javax.servlet.request.ssl_session_id");
For additional discussion on this area, please see Bugzilla.

To terminate an SSL session, use:
//StandardHTTPsessioninvalidation
session.invalidate();
//InvalidatetheSSLSession
org.apache.tomcat.util.net.SSLSessionManagermgr=
(org.apache.tomcat.util.net.SSLSessionManager)
request.getAttribute("javax.servlet.request.ssl_session_mgr");
mgr.invalidateSession();
//ClosetheconnectionsincetheSSLsessionwillbeactiveuntiltheconnection
//isclosed
response.setHeader("Connection","close");
Note that this code is Tomcat specific due to the use of the SSLSessionManager class. This is
currently only available for the BIO, NIO and NIO2 connectors, not the APR/native connector.
Comments
Notice: This comments section collects your suggestions on improving documentation
for Apache Tomcat.
If you have trouble and need help, read Find Help page and ask your question on the
tomcat-users mailing list. Do not ask such questions here. This is not a Q&A section.
The Apache Comments System is explained here. Comments may be removed by our
moderators if they are either implemented or considered invalid/off-topic.
RSS Log in / register
Nick196daysagoRating:0(registeranaccountinordertoratecomments)
IfyouusePKCS12formatforthekeystore(usingopenssltogeneratethe.p12
file)youneedtospecifythekeystoreTypeparameterintheConnectorline:
<Connector
protocol="org.apache.coyote.http11.Http11NioProtocol"
keystoreFile="${user.home}/mycert.p12"keystoreType="PKCS12"
keystorePass="changeit"
clientAuth="false"sslProtocol="TLS"/>
10/11
11/11/2015
Tomcatdoesnotseemtoautomaticallydetectthetypeofthekeystore.
Copyright 1999-2015, The Apache Software Foundation
11/11

Apache Tomcat 8 SSL

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Apache Tomcat 8 SSL

Transféré par

Droits d'auteur :

Formats disponibles

11/11/2015

SSL/TLS Configuration HOW-TO

SSL/TLS and Tomcat

General Tips on Running SSL

Installing a Certificate from a Certificate Authority

Import the Chain Certificate into your keystore

SSLCipherSuite and activate SSLHonorCipherOrder, or embed weak DH params in your

Using the SSL for session tracking in your application

Miscellaneous Tips and Bits

To access the SSL session ID from the request, use:

For additional discussion on this area, please see Bugzilla.

Copyright 1999-2015, The Apache Software Foundation

Vous aimerez peut-être aussi