[jira] [Assigned] (RANGER-1676) Policy Details popup from Access audit page not displaying details of masking policy

2017-07-05 Thread Nitin Galave (JIRA)

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

Nitin Galave reassigned RANGER-1676:


Assignee: Nitin Galave

> Policy Details popup from Access audit page not displaying details of masking 
> policy
> 
>
> Key: RANGER-1676
> URL: https://issues.apache.org/jira/browse/RANGER-1676
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.2
>Reporter: suja s
>Assignee: Nitin Galave
>
> Policy Details popup from Access audit page (The popup which is displayed 
> when we click on the respective PolicyId of audit item) is not displaying 
> details of masking policy. 
> Please refer attached screenshots, the details are available for access 
> policy and not available for masking policy.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (RANGER-1247) Hive Metastore Plugin for CLI Authorization and DDL-trigged Policy Updates

2017-07-05 Thread Weizhan Zeng (JIRA)

[ 
https://issues.apache.org/jira/browse/RANGER-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074672#comment-16074672
 ] 

Weizhan Zeng commented on RANGER-1247:
--

any process?

> Hive Metastore Plugin for CLI Authorization and DDL-trigged Policy Updates
> --
>
> Key: RANGER-1247
> URL: https://issues.apache.org/jira/browse/RANGER-1247
> Project: Ranger
>  Issue Type: Sub-task
>  Components: plugins
>Affects Versions: 0.6.2
>Reporter: Yan
>
> Motivations and functional specs can be found at 
> https://cwiki.apache.org/confluence/display/RANGER/Ranger+Plugin+for+Hive+MetaStore



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (RANGER-1672) Ranger supports plugin to enable, monitor and manage apache kylin

2017-07-05 Thread Qiang Zhang (JIRA)

[ 
https://issues.apache.org/jira/browse/RANGER-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074458#comment-16074458
 ] 

Qiang Zhang commented on RANGER-1672:
-

Thanks [~srikvenk].
1) They are stored in HBase.
2) My colleague is contributor of Kylin. He has committed an improved issue for 
kylin about the problem(https://issues.apache.org/jira/browse/KYLIN-2703). The 
problem you mention will be resolved if this issue be accepted by kylin 
community.
3)  it is the same as processing logic of other plugin.
4) Now it support dynamic policies.
5) Kylin support LDAP to manager user.

> Ranger supports plugin to enable, monitor and manage apache kylin
> -
>
> Key: RANGER-1672
> URL: https://issues.apache.org/jira/browse/RANGER-1672
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>  Labels: newbie, patch
>
> Apache Kylin is an open source Distributed Analytics Engine designed to 
> provide SQL interface and multi-dimensional analysis (OLAP) on Hadoop 
> supporting extremely large datasets, original contributed from eBay Inc. 
> Apache Kylin lets user query massive data set at sub-second latency in 3 
> steps.
> 1. Identify a Star Schema on Hadoop.
> 2. Build Cube from the identified tables.
> 3. Query with ANSI-SQL and get results in sub-second, via ODBC, JDBC or 
> RESTful API.
> We should support that using Ranger to control kylin's access rights for 
> project and cube.
> Specific implementation plan is as following:
> On the ranger website, administrators can configure policies to control user 
> access to projects and cube permissions.
> Kylin provides an abstract class and authorization interfaces for use by the 
> ranger plugin. kylin instantiates ranger plugin’s implementation class when 
> starting(this class extends the abstract class provided by kylin).
> Ranger plugin periodically polls ranger admin, updates the policy to the 
> local, and updates project and cube access rights based on policy information.
> In the Kylin side:
> 1. Kylin provides an abstract class that enables the ranger plugin's 
> implementation class to extend.
> 2. Add configuration item. 1) ranger authorization switch, 2) ranger plugin 
> implementation class's name.
> 3. Instantiate the ranger plugin implementation class when starting kylin.
> 4. kylin provides authorization interfaces for ranger plugin calls.
> 5. According to the ranger authorization configuration item, hide kylin's 
> authorization management page.
> 6. Using ranger manager access rights of the kylin does not affect kylin's 
> existing permissions functions and logic.
> In the Ranger side:
> 1. Ranger plugin will periodically polls ranger admin, updates the policy to 
> the local.
> 2. The ranger plugin invoking the authorization interfaces provided by kylin 
> to updates the project and cube access rights based on the policy information.
> reference link:https://issues.apache.org/jira/browse/KYLIN-2703



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (RANGER-1675) Policy conditions not enabled by default for Hive policies

2017-07-05 Thread suja s (JIRA)

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

suja s updated RANGER-1675:
---
Affects Version/s: (was: 0.7.1)
   0.7.2

> Policy conditions not enabled by default for Hive policies
> --
>
> Key: RANGER-1675
> URL: https://issues.apache.org/jira/browse/RANGER-1675
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.2
>Reporter: suja s
>
> Policy conditions (like expiry_date) are not visible by default on Ranger UI 
> for hive policy creation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (RANGER-1675) Policy conditions not enabled by default for Hive policies

2017-07-05 Thread suja s (JIRA)
suja s created RANGER-1675:
--

 Summary: Policy conditions not enabled by default for Hive policies
 Key: RANGER-1675
 URL: https://issues.apache.org/jira/browse/RANGER-1675
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 0.7.1
Reporter: suja s


Policy conditions (like expiry_date) are not visible by default on Ranger UI 
for hive policy creation



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)