You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Arpit Khare (JIRA)" <ji...@apache.org> on 2017/11/02 18:43:00 UTC
[jira] [Created] (AMBARI-22356) Ambari changing kafka config upon
regenerating keytabs
Arpit Khare created AMBARI-22356:
------------------------------------
Summary: Ambari changing kafka config upon regenerating keytabs
Key: AMBARI-22356
URL: https://issues.apache.org/jira/browse/AMBARI-22356
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Environment: Operating System: CentOS-6 (64 Bit)
Ambari Version: 2.5.2.0
Reporter: Arpit Khare
In a Kerberos secure environment, when we add a property *security.inter.broker.protocol* in custom kafka-broker from Ambari:
{code}security.inter.broker.protocol = SASL_SSL{code}
and we regenerate the keytabs for missing hosts and components, then Ambari overrides this custom property and set it to the default value:
{code}security.inter.broker.protocol = PLAINTEXTSASL{code}
Attachments:
1. compare_config.png
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)