[
https://issues.apache.org/jira/browse/AMBARI-9602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated AMBARI-9602:
-----------------------------------------
Attachment: 0001-AMBARI-9602-Stack-advisor-validation-for-Ranger-HBas.patch
> Stack advisor validation for Ranger HBase plugin is incorrect
> -------------------------------------------------------------
>
> Key: AMBARI-9602
> URL: https://issues.apache.org/jira/browse/AMBARI-9602
> Project: Ambari
> Issue Type: Bug
> Reporter: Velmurugan Periasamy
> Assignee: Velmurugan Periasamy
> Attachments:
> 0001-AMBARI-9602-Stack-advisor-validation-for-Ranger-HBas.patch
>
>
> The stack advisor validation when Ranger HBase plugin enabled are incorrect.
> The problem with the current approach is that it checks for an exact match
> against com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor for
> hbase.coprocessor.master.classes and hbase.coprocessor.region.classes;
> however, these are comma-delimited lists, so there could be other classes
> defined that the user needs.
> The stack advisor should be checking to see the following when the Ranger
> plugin is enabled for HBase:
> * hbase.coprocessor.master.classes contains
> com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor and does
> not contain org.apache.hadoop.hbase.security.access.AccessController
> * hbase.coprocessor.region.classes contains
> com.xasecure.authorization.hbase.XaSecureAuthorizationCoprocessor and does
> not contain org.apache.hadoop.hbase.security.access.AccessController
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
