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

Posted to dev@ranger.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2015/05/07 18:56:59 UTC

[jira] [Resolved] (RANGER-203) Framework to extend Ranger security to new components in a pluggable way

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

Madhan Neethiraj resolved RANGER-203.
-------------------------------------
    Resolution: Fixed

Implementation of stack-model for services and migration of existing services (HDFS/HBase/Hive/Knox/Storm) to use the stack-model has been completed and is available in the master branch.

> Framework to extend Ranger security to new components in a pluggable way
> ------------------------------------------------------------------------
>
>                 Key: RANGER-203
>                 URL: https://issues.apache.org/jira/browse/RANGER-203
>             Project: Ranger
>          Issue Type: Bug
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>             Fix For: 0.5.0
>
>
> To make it easier to integrate with new components, Ranger should support a plugin approach that enables component integration without having to know/touch internal details of Ranger. The plugin writer should be able to describe the component, for example via XML/JSON, to enable Ranger to render necessary UI to create/update security policies and also evaluate the policies to make security decisions and auditing.



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