ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sriharsha Chintalapani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12598) kafka_client_jaas.conf not being managed by Ambari
Date Fri, 31 Jul 2015 06:54:04 GMT

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

Sriharsha Chintalapani commented on AMBARI-12598:
-------------------------------------------------

[~u39kun] [~jaimin] here is the patch https://reviews.apache.org/r/36976/

> kafka_client_jaas.conf not being managed by Ambari
> --------------------------------------------------
>
>                 Key: AMBARI-12598
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12598
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Sriharsha Chintalapani
>            Assignee: Sriharsha Chintalapani
>             Fix For: 2.1.1
>
>
> when kafka gets kerberized we need 2 jaas files
>     kafka_jaas.conf used by server
>     kafka_client_jaas.conf used by kafka command line tools to connect to kafka server.
> Only kafka_jaas.conf is being generated by Ambari where as kafka_client_jaas.conf is
coming from rpm. When user changes kafka service principal names kafka_client_jaas.conf values
are not being reflected causing kafka-console-producer.sh and kafka-console-consumer.sh throw
kerberos exception UNKNOWN_SERVER.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message