<?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: security.inter.broker.protocol can not be set to SASL_SSL, as Kerberos is not enabled in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Kafka-security-inter-broker-protocol-can-not-be-set-to-SASL/m-p/269685#M207017</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/29428"&gt;@AKR&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;I run into the same problem. I don't think SASL itself is restricted to use Kerberos protocol, according to &lt;A href="https://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer" target="_blank" rel="noopener"&gt;wikipedia&lt;/A&gt;. As far as I am concerned, it seems that Cloudera recommends its users to use Kerberos and kind of forbids us using other mechanisms. I wonder the reason why we cannot or should not use other SASL mechanisms.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Sep 2019 02:16:55 GMT</pubDate>
    <dc:creator>iamabug</dc:creator>
    <dc:date>2019-09-04T02:16:55Z</dc:date>
  </channel>
</rss>

