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

Robert Levas updated AMBARI-17479:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk
{noformat}
commit 2913de53c82524ae44270ce52b561f457f47a37c
Author: Robert Levas <[email protected]>
Date:   Thu Jul 7 12:01:05 2016 -0400
{noformat}

Committed to branch-2.4
{noformat}
commit 9a606ef2fd356fa611d7f83dec7537b263e36964
Author: Robert Levas <[email protected]>
Date:   Thu Jul 7 12:07:10 2016 -0400
{noformat}


> authorizer.class.name not being set on secure kafka clusters
> ------------------------------------------------------------
>
>                 Key: AMBARI-17479
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17479
>             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
>
>         Attachments: AMBARI-17479_branch-2.4_01.patch, 
> AMBARI-17479_trunk_01.patch
>
>
> 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)

Reply via email to