[
https://issues.apache.org/jira/browse/AMBARI-17694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398053#comment-15398053
]
Sriharsha Chintalapani commented on AMBARI-17694:
-------------------------------------------------
[~anitajebaraj] [~rlevas] This fix is breaking general deployments of kafka
itself. It looks like this patch only addressed moving the listeners change to
stack_advisor. We had to add a follow-up patch fix the
inter.security.broker.protocol config change and now we are seeing the
security.protocol is not being set in the broker side in listeners propery when
kerberos is deployed.
Ideally we need to make all the security related to changes thats defined
in kafka kerberos.json to stack_advisor so that the config changes are
reflected back in Ambari Kafka config page. We need re-open and address the
issue better. For now lets revert this patch as it causing deployment failures.
> Kafka listeners property does not show SASL_PLAINTEXT protocol when Kerberos
> is enabled
> ---------------------------------------------------------------------------------------
>
> Key: AMBARI-17694
> URL: https://issues.apache.org/jira/browse/AMBARI-17694
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: Anita Gnanamalar Jebaraj
> Assignee: Anita Gnanamalar Jebaraj
> Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-17694-1.patch, AMBARI-17694-Jul26.patch,
> AMBARI-17694.patch
>
>
> When kerberos is enabled, the protocol for listeners in
> /etc/kafka/conf/server.properties is updated from PLAINTEXT to PLAINTEXTSASL,
> even though the Ambari UI shows otherwise
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
