Rohit,

You are right. REPOSITORY_NAME referenced in the doc is the name of the service 
instance in Ranger Admin, which contains the policies for the component (in 
this case HBase). The plugin reads this value from a configuration named 
ranger.plugin.hbase.service.name (in file ranger-hbase-security.xml).

>> After doing this I don't see anything in the Audit -> Plugins
An entry will be created here for every policy download form plugins. Plugins 
download the policies at the following events:
 - during the component startup (HBase/HiveServer/...)
 - when there is a policy change in service instance

Hope this helps.

Madhan 



On 4/6/16, 7:13 PM, "rohit sinha" <[email protected]> wrote:

>Thanks for sharing the SampleApp. I was able to run it understand the
>integration point.
>I also tried to enable HBase ranger plugin. When I added the service from
>the Ranger Admin UI I was able to talk to HBase and the resource completion
>worked. After that I deleted the HBase plugin from the UI and tried to
>enable it from the the command line following instructions mentioned here:
>https://cwiki.apache.org/confluence/display/RANGER/Apache+Ranger+0.5.0+Installation#ApacheRanger0.5.0Installation-InstallingApacheHBase(1.1.0.1)
>
>After doing this I don't see anything in the Audit -> Plugins. In the
>instructions I do see warning
>
>> Make sure the REPOSITORY_NAME service exists in Ranger Admin. If not, the
>> hbase-plugin will not be able to communicate with Ranger admin.
>
>Does this mean I need to add the service from the Ranger Admin Panel  or I
>did something wrong in the enabling the plugin ?
>
>Any help will be highly appreciated.
>
>Thanks.
>
>Thanks,
>Rohit Sinha
>
>
>On Wed, Apr 6, 2016 at 12:43 PM, rohit sinha <[email protected]>
>wrote:
>
>> Awesome. Thanks a lot.
>>
>> Thanks,
>> Rohit Sinha
>>
>>
>> On Wed, Apr 6, 2016 at 12:27 PM, Don Bosco Durai <[email protected]> wrote:
>>
>>> It is optional. It is easy to setup and helps a lot while debugging
>>> during initial setup.
>>>
>>> Bosco
>>>
>>>
>>>
>>>
>>>
>>> On 4/6/16, 12:23 PM, "rohit sinha" <[email protected]> wrote:
>>>
>>> >Thanks a lot for the prompt replies. Really appreciate it.
>>> >The "Ranger Stacks - How to add a custom plugin?" was really helpful in
>>> >getting some understanding of the integration. I am going through the
>>> >SampleApp docs now.
>>> >
>>> >Is auditing an optional feature ? From the documentation it looks like
>>> it's
>>> >not and Solr installation is a requirement. I was wondering if I can have
>>> >auditing off and skip Solr installation for initial integration purpose.
>>> >
>>> >Thanks.
>>> >
>>> >Thanks,
>>> >Rohit Sinha
>>> >
>>> >
>>> >On Wed, Apr 6, 2016 at 11:55 AM, Madhan Neethiraj <[email protected]>
>>> wrote:
>>> >
>>> >> Rohit,
>>> >>
>>> >> In addition to the details in the wiki, I would recommend reviewing the
>>> >> following sample application to understand the details of adding Ranger
>>> >> authorization to an application.
>>> >>
>>> >> - README.txt:
>>> >>
>>> https://github.com/apache/incubator-ranger/blob/master/ranger-examples/README.txt
>>> >> - Application sources:
>>> >>
>>> https://github.com/apache/incubator-ranger/tree/master/ranger-examples/sampleapp
>>> >> .
>>> >>
>>> >> Madhan
>>> >>
>>> >>
>>> >>
>>> >> On 4/6/16, 11:22 AM, "Velmurugan Periasamy" <
>>> [email protected]
>>> >> on behalf of [email protected]> wrote:
>>> >>
>>> >> >Rohit -
>>> >> >
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=53741207
>>> >> >explains how to add a custom plugin for Ranger.
>>> >> >
>>> >> >On 4/6/16, 10:47 AM, "rohit sinha" <[email protected]> wrote:
>>> >> >
>>> >> >>Hello,
>>> >> >>I am looking into integrating an external service with Apache Ranger
>>> for
>>> >> >>authorization.
>>> >> >>I looked up the wiki but there is no information about integrating
>>> new
>>> >> >>services.
>>> >> >>Can someone give me some info which might be helpful in identifying
>>> >> >>different components which needs to be developed and other required
>>> stuff
>>> >> >>
>>> >> >>Thanks.
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >>
>>>
>>>
>>

Reply via email to