ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-17478) authorizer.class.name not being set on secure kafka clusters
Date Wed, 29 Jun 2016 14:29:31 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Levas resolved AMBARI-17478.
-----------------------------------
    Resolution: Duplicate

> authorizer.class.name not being set on secure kafka clusters
> ------------------------------------------------------------
>
>                 Key: AMBARI-17478
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17478
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: kerberos, kerberos_descriptor, stack_advisor
>             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)

Mime
View raw message