[jira] [Updated] (RANGER-1035) Implement Security Best Practices

[ https://issues.apache.org/jira/browse/RANGER-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Polavarapu updated RANGER-1035: --- Attachment: 0001-RANGER-1035-Decypting-service-password-only-when-use.patch >

[jira] [Commented] (RANGER-1035) Implement Security Best Practices

[ https://issues.apache.org/jira/browse/RANGER-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343751#comment-15343751 ] Sailaja Polavarapu commented on RANGER-1035: Review request available at:

Review Request 49066: RANGER-1035: Implement Security Best Practices

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49066/ --- Review request for ranger, Alok Lal, Don Bosco Durai, Abhay Kulkarni, Madhan

[jira] [Assigned] (RANGER-1023) Handle requests from non-kerberized browser when Ranger is kerberized

[ https://issues.apache.org/jira/browse/RANGER-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-1023: Assignee: Ankita Sinha (was: Selvamohan Neethiraj) > Handle requests from non-kerberized

[jira] [Commented] (RANGER-1023) Handle requests from non-kerberized browser when Ranger is kerberized

[ https://issues.apache.org/jira/browse/RANGER-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343638#comment-15343638 ] Ankita Sinha commented on RANGER-1023: -- Committed to Master Branch :

[jira] [Commented] (RANGER-1023) Handle requests from non-kerberized browser when Ranger is kerberized

[ https://issues.apache.org/jira/browse/RANGER-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343250#comment-15343250 ] rangerqa commented on RANGER-1023: -- {color:red}-1 overall{color}. Here are the results of testing the

[jira] [Updated] (RANGER-1023) Handle requests from non-kerberized browser when Ranger is kerberized

[ https://issues.apache.org/jira/browse/RANGER-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha updated RANGER-1023: - Attachment: RANGER-1023.patch > Handle requests from non-kerberized browser when Ranger is

[jira] [Commented] (RANGER-1048) Ranger Hbase lookup should use the config provided in the Ranger hbase service

[ https://issues.apache.org/jira/browse/RANGER-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343123#comment-15343123 ] Ramesh Mani commented on RANGER-1048: - commit link

[jira] [Commented] (RANGER-842) Allow PAM for authentication

[ https://issues.apache.org/jira/browse/RANGER-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343045#comment-15343045 ] Yujie Li commented on RANGER-842: - I have been testing this patch and it's built successfully. But have

Re: Review Request 48679: Add tests for the HIVE plugin

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/48679/#review138961 --- After applying this patch, I get the below error during build.

Re: Review Request 49043: RANGER-1048 : Ranger Hbase lookup should use the config provided in the hbase service

Vel, I have updated that. Copied a wrong heading Thanks, Ramesh From: Velmurugan Periasamy > on behalf of Velmurugan Periasamy > Reply-To: Velmurugan Periasamy

[jira] [Updated] (RANGER-1048) Ranger Hbase lookup should use the config provided in the Ranger hbase service

[ https://issues.apache.org/jira/browse/RANGER-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated RANGER-1048: Summary: Ranger Hbase lookup should use the config provided in the Ranger hbase service (was:

Re: Review Request 49043: RANGER-1048 : Ranger Hbase lookup should use the config provided in the hbase service

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49043/#review138943 --- Ramesh - could you please update the description and Apache JIRA

[jira] [Updated] (RANGER-1048) Ranger Hbase lookup should use the config provided in the hbase service

[ https://issues.apache.org/jira/browse/RANGER-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramesh Mani updated RANGER-1048: Attachment: RANGER-1048.patch > Ranger Hbase lookup should use the config provided in the hbase

[jira] [Commented] (RANGER-1023) Handle requests from non-kerberized browser when Ranger is kerberized

[ https://issues.apache.org/jira/browse/RANGER-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342699#comment-15342699 ] Velmurugan Periasamy commented on RANGER-1023: -- This patch was reverted due to issues in

[jira] [Created] (RANGER-1048) Ranger Hbase lookup should use the config provided in the hbase service

Ramesh Mani created RANGER-1048: --- Summary: Ranger Hbase lookup should use the config provided in the hbase service Key: RANGER-1048 URL: https://issues.apache.org/jira/browse/RANGER-1048 Project:

Re: Review Request 49021: Handle requests from non-kerberized browser when Ranger is kerberized

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49021/#review138938 --- Ship it! Ship It! - Velmurugan Periasamy On June 21, 2016,

[jira] [Commented] (RANGER-1041) Failure to sync one user to admin causes other users/groups also not to be synced from usersync to admin

[ https://issues.apache.org/jira/browse/RANGER-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342496#comment-15342496 ] Velmurugan Periasamy commented on RANGER-1041: -- Latest patch from review request

[jira] [Commented] (RANGER-709) Support conditions that handle only a single value

[ https://issues.apache.org/jira/browse/RANGER-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342495#comment-15342495 ] Velmurugan Periasamy commented on RANGER-709: - Patch committed to master -

Re: Review Request 48944: RANGER-1041 : Failure to add/update one user should not cause failure in syncing rest of the users

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/48944/#review138911 --- Ship it! Ship It! - Sailaja Polavarapu On June 21, 2016,

Re: Review Request 49009: RANGER-709 : Support conditions that handle only a single value

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49009/#review138908 --- Ship it! Ship It! - Velmurugan Periasamy On June 21, 2016,

[jira] [Comment Edited] (RANGER-1047) Getting 204 error when trying to access Ranger with KnoxSSO if user does not exist in Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342354#comment-15342354 ] Krishna Pandey edited comment on RANGER-1047 at 6/21/16 6:11 PM: -

[jira] [Updated] (RANGER-1047) Getting 204 error when trying to access Ranger with KnoxSSO if user does not exist in Ranger DB

[ https://issues.apache.org/jira/browse/RANGER-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Pandey updated RANGER-1047: --- Attachment: Screen Shot 2016-06-21 at 11.18.28 PM.png Screenshot > Getting 204 error when

[jira] [Created] (RANGER-1047) Getting 204 error when trying to access Ranger with KnoxSSO if user does not exist in Ranger DB

Krishna Pandey created RANGER-1047: -- Summary: Getting 204 error when trying to access Ranger with KnoxSSO if user does not exist in Ranger DB Key: RANGER-1047 URL:

Re: Review Request 46432: RANGER-937 - Fix PMD unused local variables issue

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

[jira] [Commented] (RANGER-1026) Ranger service to generate PID

[ https://issues.apache.org/jira/browse/RANGER-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15342311#comment-15342311 ] Velmurugan Periasamy commented on RANGER-1026: -- Patch committed to master -

Re: Review Request 48632: RANGER-1026 : Ranger service to generate PID

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/48632/#review138879 --- Ship it! Ship It! - Velmurugan Periasamy On June 20, 2016,

[jira] [Commented] (RANGER-824) Fix code standards to remove exceptions in pmd ruleset

[ https://issues.apache.org/jira/browse/RANGER-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341938#comment-15341938 ] Colm O hEigeartaigh commented on RANGER-824: I have a bunch more work done on this, but patch

[jira] [Assigned] (RANGER-824) Fix code standards to remove exceptions in pmd ruleset

[ https://issues.apache.org/jira/browse/RANGER-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned RANGER-824: -- Assignee: Colm O hEigeartaigh > Fix code standards to remove exceptions in pmd

Review Request 49021: Handle requests from non-kerberized browser when Ranger is kerberized

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49021/ --- Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni,

[jira] [Resolved] (RANGER-933) Services landing page restricts the listing to first 25 services only

[ https://issues.apache.org/jira/browse/RANGER-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-933. Resolution: Cannot Reproduce > Services landing page restricts the listing to first 25

[jira] [Resolved] (RANGER-703) Policy UI validation blocks policy with audit-disabled and no groups

[ https://issues.apache.org/jira/browse/RANGER-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal resolved RANGER-703. Resolution: Cannot Reproduce > Policy UI validation blocks policy with audit-disabled and

[jira] [Updated] (RANGER-703) Policy UI validation blocks policy with audit-disabled and no groups

[ https://issues.apache.org/jira/browse/RANGER-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-703: --- Fix Version/s: 0.6.0 > Policy UI validation blocks policy with audit-disabled and no groups

[jira] [Assigned] (RANGER-1046) ranger kms repo creation is failing after ranger kms is installed

[ https://issues.apache.org/jira/browse/RANGER-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankita Sinha reassigned RANGER-1046: Assignee: Ankita Sinha > ranger kms repo creation is failing after ranger kms is

[jira] [Created] (RANGER-1046) ranger kms repo creation is failing after ranger kms is installed

Deepak Sharma created RANGER-1046: - Summary: ranger kms repo creation is failing after ranger kms is installed Key: RANGER-1046 URL: https://issues.apache.org/jira/browse/RANGER-1046 Project: Ranger

[jira] [Assigned] (RANGER-458) Recursive button in HDFS and Yarn Service definition needs to be changed

[ https://issues.apache.org/jira/browse/RANGER-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh reassigned RANGER-458: --- Assignee: Mehul Parikh (was: Gautam Borad) > Recursive button in HDFS and Yarn Service

Review Request 49009: RANGER-709 : Support conditions that handle only a single value

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49009/ --- Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni,

[jira] [Updated] (RANGER-709) Support conditions that handle only a single value

[ https://issues.apache.org/jira/browse/RANGER-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh updated RANGER-709: Attachment: RANGER-709.patch > Support conditions that handle only a single value >

[jira] [Updated] (RANGER-709) Support conditions that handle only a single value

[ https://issues.apache.org/jira/browse/RANGER-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehul Parikh updated RANGER-709: Assignee: Mehul Parikh (was: Gautam Borad) > Support conditions that handle only a single value >

Re: Ranger question

Hi, Hafiz is right, you need to set the username/password in the request header. Also make sure that the user you are setting has either of the following roles: Admin, Keyadmin or Delegate Admin. Since only users with these roles have permission to view the policy. Hi, Regard, Bhavik Patel