You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2016/09/08 10:53:21 UTC

[jira] [Updated] (RANGER-1171) Invert authorization logic in RangerKafkaAuthorizer

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

Colm O hEigeartaigh updated RANGER-1171:
----------------------------------------
    Attachment: 0001-RANGER-1171-Invert-authorization-logic-in-RangerKafk.patch

> Invert authorization logic in RangerKafkaAuthorizer
> ---------------------------------------------------
>
>                 Key: RANGER-1171
>                 URL: https://issues.apache.org/jira/browse/RANGER-1171
>             Project: Ranger
>          Issue Type: Bug
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 0.7.0, 0.6.2
>
>         Attachments: 0001-RANGER-1171-Invert-authorization-logic-in-RangerKafk.patch
>
>
> Similar to RANGER-1095, the RangerKafkaAuthorizer has a boolean "returnValue" which defaults to true. However, there is a catch clause which just logs an error, meaning that  a RuntimeException could result in successful authorization. Instead, the boolean should default to false.



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