ssl-guide.html 9.54 KB
Newer Older
Matt Tucker's avatar
Matt Tucker committed
1 2 3 4 5 6 7 8 9 10 11
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title>Jive Messenger SSL Guide</title>
  <link type="text/css" rel="stylesheet" href="style.css">
</head>
<body>
<a name="top"></a>
<h1>Jive Messenger SSL Guide</h1>
<h2>Introduction</h2>
<p>
12 13 14 15 16 17 18 19 20
This document outlines how to customize the SSL support in Jive Messenger.
<font color="red"><b>Important note:</b></font>
because Jive Messenger ships with self-signed certificates, most users can
use the default configration and do not need to change the SSL environment. You should only
attempt to change the SSL settings if it's required for your deployment.</p>

<p>Jive Messenger's SSL support is built using the standard Java security
SSL implementation (javax.net.ssl.SSLServerSocket). In this document, we will
describe how use the standard JDK 1.5 tools to accomplish these tasks.
Matt Tucker's avatar
Matt Tucker committed
21 22 23 24 25 26 27
</p>
<h2>Background</h2>
<p>
A server SSL connection uses two sets of certificates to secure the
connection. The first set is called a "keystore". The keystore contains
the keys and certificates for the server. These security credentials
are used to prove to clients that the server is legitimately operating
28 29
on behalf of a particular domain. If your server will only need to act
as one domain, you only need one key entry and certificate in the keystore.
Matt Tucker's avatar
Matt Tucker committed
30
Keys are stored in the keystore under aliases. Each alias corresponds
Matt Tucker's avatar
Matt Tucker committed
31
to a domain name (e.g. "example.com").
Matt Tucker's avatar
Matt Tucker committed
32 33 34
</p>
<p>
The second set of certificates is called the "truststore" and is used
35 36 37 38
to verify that a client is legitimately operating on behalf of a
particular user. In the vast majority of cases, the truststore is
empty and the server will not attempt to validate client connections
using SSL. Instead, the XMPP authentication process verifies users
Matt Tucker's avatar
Matt Tucker committed
39
in-band. However, you may wish to require SSL authentication for
40 41
certain clients when security is especially important and the number
of clients connection to the server is relatively small.
Matt Tucker's avatar
Matt Tucker committed
42 43 44
</p>
<p>
Certificates attempt to guarantee that a particular party is who they
45 46 47
claim to be. Certificates are trusted based on who signed the certificate.
If you only require light security, are deploying for internal use on
trusted networks, etc. you can use "self-signed" certificates.
Matt Tucker's avatar
Matt Tucker committed
48
Self-signed certificates encrypts the communication channel between
49 50 51
client and server. However the client must verify the legitimacy of the
self-signed certificate through some other channel. The most common client
reaction to a self-signed certificate is to ask the user whether
Matt Tucker's avatar
Matt Tucker committed
52 53 54 55 56 57
to trust the certificate, or to silently trust the certificate is
legitimate. Unfortunately, blindly accepting self-signed certificates
opens up the system to 'man-in-the-middle' attacks.
</p>
<p>
The advantage of a self-signed certificate is you can create them for
58 59 60 61
free which is great when cost is a major concern, or for testing and evaluation.
In addition, you can safely use a self-signed certificate if you can verify
that the certificate you're using is legitimate. So if a system administrator
creates a self-signed certificate, then personally installs it on a client's
Matt Tucker's avatar
Matt Tucker committed
62
truststore (so that the certificate is trusted) you can be assured that
63
the SSL connection will only work between the client and the correct server.
Matt Tucker's avatar
Matt Tucker committed
64 65 66
</p>
<p>
For higher security deployments, you should get your certificate signed
67 68 69 70 71 72
by a certificate authority (CA). Clients truststores will usually contain
the certificates of the major CA's and can verify that a CA has signed a
certificate. This chain of trust allows clients to trust certificate from
servers they've never interacted with before. Certificate signing is similar
to a public notary (with equivalent amounts of verification of identity,
record keeping, and costs).
Matt Tucker's avatar
Matt Tucker committed
73
</p>
Gaston Dombiak's avatar
Gaston Dombiak committed
74
<h2>Sun JDK 1.5 security tools</h2>
Matt Tucker's avatar
Matt Tucker committed
75
<p>
Gaston Dombiak's avatar
Gaston Dombiak committed
76
The Sun JDK (version 1.5.x) ships with all the security tools you need
77 78 79 80 81 82 83
to configure SSL with Jive Messenger. The most important is the
<tt>keytool</tt> located in the <tt>JAVA_HOME/bin directory</tt> of the
JDK. Sun JVMs persist keystores and truststores on the filesystem as
encrypted files. The <tt>keytool</tt> is used to create, read, update,
and delete entries in these files. Jive Messenger ships with a self-signed
"dummy" certificate designed for initial evaluation testing. You will need
to adjust the default configuration for most deployments.
Matt Tucker's avatar
Matt Tucker committed
84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109
</p>
<p>
In order to configure SSL on your server you need complete the
following tasks:
</p>
<ol>
  <li>Decide on your Jive Messenger server's domain.</li>
  <li>Create a self-signed SSL server certificate for your server
domain. Note: you may already have one if your Jive Messenger server
domain matches an existing web domain with SSL.
If so, you can skip to step 4.</li>
  <li>[Optional] Have a certificate authority (CA) certify the SSL
server certificate.
    <ol style="list-style-type: lower-alpha;">
      <li>Generate a certificate signing request (CSR).</li>
      <li>Submit your CSR to a CA for signing.</li>
    </ol>
  </li>
  <li>Import the server certificate into the keystore. Note: if you are
going to use a self-signed certificate
generated in step 2, the certificate is already imported and you can
skip this step.</li>
  <li>Import client certificates into the truststore.</li>
  <li>Adjust the Messenger configuration with proper keystore and
truststore settings.</li>
</ol>
Matt Tucker's avatar
Matt Tucker committed
110
<h3>1. Decide on a Server Domain</h3>
Matt Tucker's avatar
Matt Tucker committed
111 112
<p>
The Messenger server domain should match the host name of the server;
Matt Tucker's avatar
Matt Tucker committed
113 114 115
for example, "example.com". Your user accounts will have addresses with
the format "user@example.com" like email addresses. We'll assume
the domain is "example.com" for the rest of the examples.
Matt Tucker's avatar
Matt Tucker committed
116
</p>
Matt Tucker's avatar
Matt Tucker committed
117
<h3>2. Create a self-signed server certificate</h3>
Matt Tucker's avatar
Matt Tucker committed
118 119
<p>
In order to create a self-signed server certificate go to the command
Matt Tucker's avatar
Matt Tucker committed
120 121
line and change directories to the <tt>resources/security</tt>
directory of your Jive Messenger installation. You should see the default
Matt Tucker's avatar
Matt Tucker committed
122 123 124 125 126 127 128 129 130 131
<tt>keystore</tt> and <tt>truststore</tt> files. First, you should
change the default keystore
password:
</p>
<p><tt>keytool -storepasswd -keystore keystore</tt></p>
<p>
keytool will ask for the old password (by default it is <tt>changeit</tt>)
then the new password.
Now we'll create a certificate using the keytool:
</p>
Matt Tucker's avatar
Matt Tucker committed
132
<p><tt>keytool -genkey -keystore keystore -alias example.com</tt></p>
Matt Tucker's avatar
Matt Tucker committed
133
<p>
Matt Tucker's avatar
Matt Tucker committed
134
where you should substitute your server's name for <tt>example.com</tt>.
135
The keytool will ask for the store password, then several pieces of
136 137 138 139
information required for the certificate. Enter all the information but remember 
to <b>complete with your server's name when asked for your first and last name</b>. 
After you have entered all the required information, keytool will ask you to 
verify the information and set a key password.
140 141 142 143 144
<b>You must use the same key password as the store password.</b> By default
you get this by simply hitting 'enter' when prompted for a key password.</p>
<p>If you later change the keystore password remember to change the entries'
password as well using the keytool:</p>

Matt Tucker's avatar
Matt Tucker committed
145
<p><tt>keytool -keypasswd -alias example.com -keystore keystore</tt>
Matt Tucker's avatar
Matt Tucker committed
146
</p>
Matt Tucker's avatar
Matt Tucker committed
147
<h3>3. Obtain a CA signed certificate</h3>
Matt Tucker's avatar
Matt Tucker committed
148 149 150 151 152
<p>
If you decide to get a CA signed certificate, you must first export the
certificate in the
standard CSR format. You can do this with the keytool:
</p>
Matt Tucker's avatar
Matt Tucker committed
153
<p><tt>keytool -certreq -keystore keystore -alias example.com -file
Matt Tucker's avatar
Matt Tucker committed
154 155
certificate_file</tt></p>
<p>
Matt Tucker's avatar
Matt Tucker committed
156
Where you should substitute your server's name for <tt>example.com</tt>
Matt Tucker's avatar
Matt Tucker committed
157 158 159 160 161
and the name of the
certificate file you wish to produce for <tt>certificate_file</tt>.
Submit the generated CSR to the CA and follow their instructions to get
it signed.
</p>
Matt Tucker's avatar
Matt Tucker committed
162
<h3>4. Import server certificates</h3>
Matt Tucker's avatar
Matt Tucker committed
163 164 165 166 167
<p>
If you had a CA sign your server certificate, or if you have an
existing SSL certificate,
you must import it using the keytool.
</p>
Matt Tucker's avatar
Matt Tucker committed
168
<p><tt>keytool -import -keystore keystore -alias example.com -file
Matt Tucker's avatar
Matt Tucker committed
169 170 171 172 173
signed_certificate_file</tt></p>
<p>
It is important that the alias not already have an associated key or
you'll receive an error.
</p>
Matt Tucker's avatar
Matt Tucker committed
174
<h3>5. Import client certificates</h3>
Matt Tucker's avatar
Matt Tucker committed
175 176 177 178 179 180 181 182 183 184 185 186 187 188
<p>
If you require clients to verify themselves using certificates, obtain
their certificates and import them into the truststore file rather than
the keystore. First, you should change the default truststore
password:
</p>
<p><tt>keytool -storepasswd -keystore truststore</tt></p>
<p>
keytool will ask for the old password (by default it is <tt>changeit</tt>)
then the new password.
Now import each certificate using the keytool:
</p>
<p><tt>keytool -import -keystore truststore -alias user_name -file
certificate_file</tt></p>
Matt Tucker's avatar
Matt Tucker committed
189
<h3>6. Configure Messenger</h3>
Matt Tucker's avatar
Matt Tucker committed
190
<p>
Gaston Dombiak's avatar
Gaston Dombiak committed
191 192
Open the Jive Messenger Admin Console in your favorite
browser and add or change the following system properties:
Matt Tucker's avatar
Matt Tucker committed
193 194
</p>
<ul>
195 196
  <li>xmpp.socket.ssl.active -- set to 'true' to active SSL</li>
  <li>xmpp.socket.ssl.port -- the port to use for SSL (default is
Matt Tucker's avatar
Matt Tucker committed
197
5223 for XMPP)</li>
198
  <li>xmpp.socket.ssl.storeType -- the store type used ("JKS" is
199 200
the Sun Java Keystore format used by the JDK keytool). If this property is 
not defined, Messenger will assume a value of "jks".</li>
201
  <li>xmpp.socket.ssl.keystore -- the location of the keystore file
Matt Tucker's avatar
Matt Tucker committed
202 203
relative to your Jive Messenger installation root directory. You can leave this property
blank to use the default keystore.</li>
204
  <li>xmpp.socket.ssl.keypass -- the keystore/key password you
Matt Tucker's avatar
Matt Tucker committed
205
changed in step 2.</li>
206
  <li>xmpp.socket.ssl.truststore -- leave blank to not use a
Matt Tucker's avatar
Matt Tucker committed
207
truststore, otherwise the location of the truststore file relative to
Matt Tucker's avatar
Matt Tucker committed
208
your Jive Messenger installation root directory.</li>
209
  <li>xmpp.socket.ssl.trustpass -- the truststore/key password you
Matt Tucker's avatar
Matt Tucker committed
210 211
changed in step 5.</li>
</ul>
212
You will need to restart the server after you have modified any of the above system properties.
Gaston Dombiak's avatar
Gaston Dombiak committed
213
</body>
Matt Tucker's avatar
Matt Tucker committed
214
</html>