Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 1 Dec 2017 06:26:00 +0000 (UTC)
From: "Doroszlai, Attila (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13119709.1511195359000.362816.1512109560052@Atlassian.JIRA>
In-Reply-To: <JIRA.13119709.1511195359000@Atlassian.JIRA>
References: <JIRA.13119709.1511195359000@Atlassian.JIRA> <JIRA.13119709.1511195359890@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMBARI-22485) Allow Ambari to support
 non-kerberos SASL mechanisms for Kafka
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 01 Dec 2017 06:26:11 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-22485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274005#comment-16274005 ] 

Doroszlai, Attila commented on AMBARI-22485:
--------------------------------------------

Hi [~YolandaMDavis],

The [unit test that validates config XMLs is failing|https://builds.apache.org/job/Ambari-trunk-Commit/8477/testReport/junit/org.apache.ambari.server.state/ServicePropertiesTest/validatePropertySchemaOfServiceXMLs/] since this commit.

{noformat:title=KAFKA/0.10.0/configuration/kafka-broker.xml}
<on-ambari-upgrade add="upgrade"/>
{noformat}

should be:

{noformat}
<on-ambari-upgrade add="true"/>
{noformat}

> Allow Ambari to support non-kerberos SASL mechanisms for Kafka
> --------------------------------------------------------------
>
>                 Key: AMBARI-22485
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22485
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.6.0
>            Reporter: Yolanda M. Davis
>            Assignee: Yolanda M. Davis
>         Attachments: AMBARI-22485.patch, AMBARI-22485_branch-2.6.patch
>
>
> Currently AMBARI support's SASL and SSL as the security options for Kafka.
> Within SASL Ambari only supports GSSAPI(kerberos) only. Kafka supports other mechanisms such as plain, md5 etc.. This allows users to plug in their LDAP system into Kafka.
> Also another important option is SASL_SSL. 
> We need to expose necessary configs in Ambari to enable these mechanisms for users.
> Ambari should allow users to not only configure Kafka for non-kerberos based SASL mechanisms, but also ensure that jaas configuration files are written when these options are provided (as opposed to only writing those files when kerberos has been enabled)..


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)