[AMBARI-12598] kafka_client_jaas.conf not being managed by Ambari

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.1
• Assignee: Harsha
• Reporter: Harsha
• Created: 31/Jul/15 06:42
• Updated: 31/Jul/15 21:52
• Resolved: 31/Jul/15 17:58

Description

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.