Re: Review Request 65920: Ranger Tagsync should use cookie based authentication for subsequent requests to Ranger admin

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/65920/#review199004 ---

[jira] [Commented] (RANGER-2014) Unable to see policy detail in view policy mode after updating recursive flag

[ https://issues.apache.org/jira/browse/RANGER-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16394874#comment-16394874 ] Nitin Galave commented on RANGER-2014: -- Committed to 

Re: Review Request 66021: RANGER-2014: Unable to see policy detail in view policy mode after updating recursive flag

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/66021/#review199002 --- Ship it! Ship It! - Pradeep Agrawal On March 10, 2018, 3:27

Re: Review Request 65920: Ranger Tagsync should use cookie based authentication for subsequent requests to Ranger admin

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/65920/#review199005 --- Ship it! Ship It! - Gautam Borad On March 9, 2018, 4:35

[jira] [Updated] (RANGER-2010) Ranger Tagsync should use cookie based authentication for subsequent requests to Ranger admin

[ https://issues.apache.org/jira/browse/RANGER-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Purbhe updated RANGER-2010: -- Attachment: 0003-RANGER-2010-Ranger-Tagsync-should-use-cookie-based-a.patch > Ranger Tagsync

[jira] [Created] (RANGER-2015) In view policy we are able to see 'Deny Policy' & 'Except Conditions' even if 'enableDenyAndExceptionsInPolicies : false'

Nitin Galave created RANGER-2015: Summary: In view policy we are able to see 'Deny Policy' & 'Except Conditions' even if 'enableDenyAndExceptionsInPolicies : false' Key: RANGER-2015 URL:

Re: Review Request 65920: Ranger Tagsync should use cookie based authentication for subsequent requests to Ranger admin

> On March 12, 2018, 12:51 p.m., Madhan Neethiraj wrote: > > tagsync/src/main/java/org/apache/ranger/tagsync/sink/tagadmin/TagAdminRESTSink.java > > Lines 328 (patched) > > > > > > when would 'response' not contain

Re: Review Request 65920: Ranger Tagsync should use cookie based authentication for subsequent requests to Ranger admin

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/65920/ --- (Updated March 12, 2018, 3:46 p.m.) Review request for ranger, Ankita Sinha,

Atlas policies to filter access

Hi all, I'm using the Ranger plugin to secure access to Atlas. How can I create a policy in Ranger to allow a user access to a subset of the entities? So for example, I want to allow "alice" to "read" all entities that have a given type. I created an authorization policy of "type" "Table", but I

[jira] [Updated] (RANGER-1948) Support for Read-only Ranger Admin users

[ https://issues.apache.org/jira/browse/RANGER-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-1948: -- Attachment: (was: RANGER-1948_v1.patch) > Support for Read-only Ranger Admin users

[jira] [Updated] (RANGER-1948) Support for Read-only Ranger Admin users

[ https://issues.apache.org/jira/browse/RANGER-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fatima Amjad Khan updated RANGER-1948: -- Attachment: RANGER-1948.patch > Support for Read-only Ranger Admin users >

[jira] [Updated] (RANGER-2015) In view policy we are able to see 'Deny Policy' & 'Except Conditions' even if 'enableDenyAndExceptionsInPolicies : false'

[ https://issues.apache.org/jira/browse/RANGER-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-2015: - Fix Version/s: 1.1.0 > In view policy we are able to see 'Deny Policy' & 'Except

[jira] [Updated] (RANGER-1948) Support for Read-only Ranger Admin users

[ https://issues.apache.org/jira/browse/RANGER-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-1948: - Fix Version/s: (was: 1.0.0) 1.1.0 > Support for Read-only

[jira] [Commented] (RANGER-1991) Fix problems detected by static code analysis

[ https://issues.apache.org/jira/browse/RANGER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16395240#comment-16395240 ] Pradeep Agrawal commented on RANGER-1991: - [~zsombor] : I think I should commit my proposed patch

[jira] [Commented] (RANGER-1991) Fix problems detected by static code analysis

[ https://issues.apache.org/jira/browse/RANGER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16395264#comment-16395264 ] Pradeep Agrawal commented on RANGER-1991: - I have committed the patch in ranger-1.0 branch: 

[jira] [Comment Edited] (RANGER-1991) Fix problems detected by static code analysis

[ https://issues.apache.org/jira/browse/RANGER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16395264#comment-16395264 ] Pradeep Agrawal edited comment on RANGER-1991 at 3/12/18 2:01 PM: -- I

[jira] [Commented] (RANGER-1991) Fix problems detected by static code analysis

[ https://issues.apache.org/jira/browse/RANGER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16395251#comment-16395251 ] Velmurugan Periasamy commented on RANGER-1991: -- [~pradeep.agrawal] +1 for this suggestion. 

Re: Review Request 65920: Ranger Tagsync should use cookie based authentication for subsequent requests to Ranger admin

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/65920/#review199028 ---

[jira] [Updated] (RANGER-2017) Change the default Crypt Algo to use stronger cryptographic algo for Ranger KMS

[ https://issues.apache.org/jira/browse/RANGER-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-2017: - Description: Change the default crypt algorithm to use a stronger cipher

[jira] [Updated] (RANGER-2017) Ranger KMS encryption good practices

[ https://issues.apache.org/jira/browse/RANGER-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy updated RANGER-2017: - Summary: Ranger KMS encryption good practices (was: Change the default Crypt

[jira] [Assigned] (RANGER-2017) Change the default Crypt Algo to use stronger cryptographic algo for Ranger KMS

[ https://issues.apache.org/jira/browse/RANGER-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy reassigned RANGER-2017: Assignee: (was: Endre Kovacs) > Change the default Crypt Algo to use

[jira] [Assigned] (RANGER-2017) Change the default Crypt Algo to use stronger cryptographic algo for Ranger KMS

[ https://issues.apache.org/jira/browse/RANGER-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh reassigned RANGER-2017: Assignee: bhavik patel > Change the default Crypt Algo to use stronger cryptographic algo

[jira] [Created] (RANGER-2016) Fix null passed in as a HttpServletRequest - into the deletePoliciesProvidedInServiceMap method.

Velmurugan Periasamy created RANGER-2016: Summary: Fix null passed in as a HttpServletRequest - into the deletePoliciesProvidedInServiceMap method. Key: RANGER-2016 URL:

[jira] [Created] (RANGER-2018) Upgrade to Spring 4

Pradeep Agrawal created RANGER-2018: --- Summary: Upgrade to Spring 4 Key: RANGER-2018 URL: https://issues.apache.org/jira/browse/RANGER-2018 Project: Ranger Issue Type: Improvement

[jira] [Created] (RANGER-2017) Change the default Crypt Algo to use stronger cryptographic algo for Ranger KMS

Velmurugan Periasamy created RANGER-2017: Summary: Change the default Crypt Algo to use stronger cryptographic algo for Ranger KMS Key: RANGER-2017 URL: https://issues.apache.org/jira/browse/RANGER-2017

[jira] [Commented] (RANGER-1991) Fix problems detected by static code analysis

[ https://issues.apache.org/jira/browse/RANGER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396385#comment-16396385 ] Velmurugan Periasamy commented on RANGER-1991: -- Resolving this now. Filed

[jira] [Resolved] (RANGER-1991) Fix problems detected by static code analysis

[ https://issues.apache.org/jira/browse/RANGER-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Velmurugan Periasamy resolved RANGER-1991. -- Resolution: Fixed > Fix problems detected by static code analysis >

[VOTE] Apache Ranger Release 1.0.0-rc0 (Updated links)

Rangers: Thank you for your contribution to Apache Ranger community. Apache Ranger 1.0.0 release candidate #0 is now available for a vote within dev community. Links to release artifacts are given below. I kindly request all of the Rangers (dev & PMC members) to review and vote on this release.

Re: Atlas policies to filter access

Colm, Perhaps you are using the Atlas service-def from Ranger master, against Atlas from branch-0.8 (or from master before ATLAS-2459)? Earlier Atlas versions use a different authorization model, which don't allow access controls at instance/type levels. Please try with Atlas from master