You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2016/06/29 13:36:31 UTC
[jira] [Created] (AMBARI-17477) authorizer.class.name not being set
on secure kafka clusters
Robert Levas created AMBARI-17477:
-------------------------------------
Summary: authorizer.class.name not being set on secure kafka clusters
Key: AMBARI-17477
URL: https://issues.apache.org/jira/browse/AMBARI-17477
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Blocker
Fix For: 2.4.0
The {{kafka-broker/authorizer.class.name}} property is not being set properly when Kerberos is enabled.
The following logic should be followed:
{noformat}
if Kerberos is enabled
if ranger-kafka-plugin-properties/ranger-kafka-plugin-enabled == yes
set authorizer.class.name to "org.apache.ranger.authorization.kafka.authorizer.RangerKafkaAuthorizer"
else
set authorizer.class.name to "kafka.security.auth.SimpleAclAuthorizer"
else
remove authorizer.class.name
{noformat}
This should be updated in the stack advisor code.
While at it, configurations from Kafka's {{kerberos.json}} file should be moved to the stack advisor to help ensure properties are set in the the same place to help with code maintenance and consistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)