<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Kafka with SSL in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Kafka-with-SSL/m-p/234030#M195851</link>
    <description>&lt;P&gt;It should be like this, in case only the brokers need to authenticate (one-way server side SSL auth) to the clients:&lt;/P&gt;&lt;P&gt;You need:&lt;/P&gt;&lt;P&gt;1. Client side: 1 keystore (client.truststore.jks) containing just the ca_cert you created and was used to sign the broker / server certificates&lt;/P&gt;&lt;P&gt;2. Server side: On each broker 1 keystore (server.keystore.jks) containing both the server specific certificate generated before, ( which should now be signed by the CA) and the certificate of the CA itself. &lt;/P&gt;&lt;P&gt;What is misleading in the Kafka documentation is the first step, where a keystore 'server.keystore.jks' is created in the very first step, only to export the unsigned cert from to actually sign it. This is not the same 'server.keystore.jks' as in 2. above as the it should not contain the unsigned broker cert anymore ! You don't necessarily need a keystore to create a certificate to sign, you can also just create a cert + key, have it signed and then import it into a new keystore. &lt;/P&gt;&lt;P&gt;Also, it makes more sense to me to copy the CA cert onto the brokers then moving it back-and-forth from server -&amp;gt; CA node (to sign) -&amp;gt; back to server (to import into final 'server.keystore.jks')&lt;/P&gt;&lt;P&gt;Hope it makes sense&lt;/P&gt;</description>
    <pubDate>Fri, 01 Sep 2017 04:37:48 GMT</pubDate>
    <dc:creator>jknulst</dc:creator>
    <dc:date>2017-09-01T04:37:48Z</dc:date>
  </channel>
</rss>

