MINOR: Fixed misleading reference to HTTPS instead of SSL support in the doc

Author: ppatierno <ppatierno@live.com>

Reviewers: Ewen Cheslack-Postava <ewen@confluent.io>

Closes #3487 from ppatierno/ssl-doc-https
This commit is contained in:
ppatierno 2017-07-20 20:16:15 -07:00 committed by Ewen Cheslack-Postava
parent 8a81566214
commit 1d2d0bac9e
1 changed files with 1 additions and 1 deletions

View File

@ -40,7 +40,7 @@
<ol>
<li><h4><a id="security_ssl_key" href="#security_ssl_key">Generate SSL key and certificate for each Kafka broker</a></h4>
The first step of deploying HTTPS is to generate the key and the certificate for each machine in the cluster. You can use Java's keytool utility to accomplish this task.
The first step of deploying one or more brokers with the SSL support is to generate the key and the certificate for each machine in the cluster. You can use Java's keytool utility to accomplish this task.
We will generate the key into a temporary keystore initially so that we can export and sign it later with CA.
<pre class="brush: bash;">
keytool -keystore server.keystore.jks -alias localhost -validity {validity} -genkey -keyalg RSA</pre>