Re: Request to make me contributor in Apache Ranger

2017-03-14 Thread Nitin Galave 
Selva,

JIRA identifier :

username - nitin dot galave (nitin.galave)
email address - nitin dot galave at gmail dot com  (nitin.gal...@gmail.com)


Thanks,

Nitin Galave

On Wed, Mar 15, 2017 at 4:50 AM, Selvamohan Neethiraj 
wrote:

> Nitin,
>
> I am not able to locate your JIRA identifier, Can you please send your
> JIRA id and email address ?
>
> Thanks,
> Selva-
>
>
> > On Mar 14, 2017, at 8:36 AM, Nitin Galave 
> wrote:
> >
> >
> > Hi Selva,
> >
> > Have you had time to look into this ?
> >
> >
> >
> > Thanks,
> >
> > Nitin Galave.
> >
> >
> > -- Forwarded message --
> > From: Nitin Galave >
> > Date: Thu, Mar 9, 2017 at 10:54 AM
> > Subject: Request to make me contributor in Apache Ranger
> > To: dev@ranger.apache.org 
> >
> >
> >
> >
> > Rangers:
> >
> > As I have been involved in the Apache Ranger project for a while now,
> Can you please add me as a contributor to the project ?
> >
> >
> > Thanks,
> >
> > Nitin Galave.
> >
> >
> >
> >
> >
> > --
> > Thanks,
> > Nitin Galave.
>
>


-- 


*Thanks,Nitin Galave.*

[jira] [Reopened] (RANGER-1400) Enabling Ranger HDFS Plugins failed when hadoop program and Ranger HDFS Plugin are not in the same path.

2017-03-14 Thread Qiang Zhang (JIRA) 

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

Qiang Zhang reopened RANGER-1400:
-

> Enabling Ranger HDFS Plugins failed when hadoop program and Ranger HDFS 
> Plugin are not in the same path.
> 
>
> Key: RANGER-1400
> URL: https://issues.apache.org/jira/browse/RANGER-1400
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>  Labels: patch
> Fix For: 1.0.0
>
> Attachments: 
> 0001-RANGER-1400-Enabling-Ranger-HDFS-Plugins-failed-when.patch
>
>
> Enabling Ranger HDFS Plugins failed when hadoop program and Ranger HDFS 
> Plugin are not in the same path. 
> 1. Install hadoop-2.7.3 under /var/local/hadoop
> 2. Copy ranger-1.0.0-SNAPSHOT-hdfs-plugin.tar.gz to /usr/local
> 3. Run command: cd /usr/local
> 4. Run command: sudo tar -zxvf ranger-1.0.0-SNAPSHOT-hdfs-plugin.tar.gz
> 5. Modified install.properties according to installation guide.
> 6. Execute enable-hdfs-plugin.sh
> result:
> ERROR: Unable to find the lib directory of component [hadoop];  dir 
> [/usr/local/hadoop/lib] not found.
> Reason:
> COMPONENT_INSTALL_DIR_NAME does not exist in install.properties. So the 
> HCOMPONENT_INSTALL_DIR_NAME variable is empty when execute the following 
> sentence.
>  HCOMPONENT_INSTALL_DIR_NAME=$(getInstallProperty 
> 'COMPONENT_INSTALL_DIR_NAME')
> The result is that HCOMPONENT_LIB_DIR directory doesn't exist.
> We should add COMPONENT_INSTALL_DIR_NAME parameter to install.properties. The 
> error can be avoided after setting COMPONENT_INSTALL_DIR_NAME.
> Test and verify:
> I carefully tested and verified the patch before commit the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Issue Comment Deleted] (RANGER-1150) Optimize comments in install.properties

2017-03-14 Thread Haihui Xu (JIRA) 

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

Haihui Xu updated RANGER-1150:
--
Comment: was deleted

(was: Thanks [~gautamborad] very much. I have fixed the text,I need 
review,Thanks in advance.)

> Optimize comments in install.properties
> ---
>
> Key: RANGER-1150
> URL: https://issues.apache.org/jira/browse/RANGER-1150
> Project: Ranger
>  Issue Type: Bug
>  Components: usersync
>Affects Versions: 0.6.0, 0.5.3
> Environment: centos6.5 x64
> ranger 0.7.0-SNAPSHOT
>Reporter: Haihui Xu
>Assignee: Haihui Xu
>Priority: Minor
> Fix For: 0.5.3, 0.7.0
>
> Attachments: RANGER-1150_1.patch, RANGER-1150.patch
>
>
> The properties file of unixauthservice/scripts/install.properties has two 
> mistakes, and when compiled the ranger source, the install.properties would 
> be in ranger-0.7.0-SNAPSHOT-usersync.tar.gz.
> a.  the first inaccurate comment is " # a sample value would be 
> cn=admin,ou=users,dc=hadoop,dc=apache,dc-org". When deploy the usersync, the 
> comment given sample value would mislead user,especially the user do not 
> understant LDAP.  Sample value would possibly be 
> cn=admin,ou=users,dc=hadoop,dc=apache,dc=org.
> b. second is:"# if the value is false, typical AD would return would not 
> returm more than 1000 entries", the word "returm" should be "return", and the 
> sentence should be: "# if the value is false, typical AD would not return 
> more than 1000 entries."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (RANGER-1321) Provide a mechanism to create service-specific default policies

2017-03-14 Thread Abhay Kulkarni (JIRA) 

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

Abhay Kulkarni updated RANGER-1321:
---
Fix Version/s: 0.7.1

> Provide a mechanism to create service-specific default policies
> ---
>
> Key: RANGER-1321
> URL: https://issues.apache.org/jira/browse/RANGER-1321
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.6.0, 0.7.0
>Reporter: Ramesh Mani
>Assignee: Abhay Kulkarni
> Fix For: 1.0.0, 0.7.1
>
>
> When a service is created, Ranger Admin creates a default policy in the new 
> service which grants all access to the user specified in service-config. This 
> works for most services. However, it is possible that some service 
> implementation might want to create default policy with different accesses. 
> It will be useful to provide a mechanism to enable service-specific default 
> policy creation – similar to service-specific resource-lookup implementations 
> which is available today via RangerBaseService interface. Something like:
>  
> public abstract class RangerBaseService {
>   // ...
>  
>   public List getDefaultPolicies();
> }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (RANGER-1437) Disable optimization for tag download to include only tags that have policies

2017-03-14 Thread Velmurugan Periasamy (JIRA) 

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

Velmurugan Periasamy updated RANGER-1437:
-
Fix Version/s: (was: master)
   1.0.0

> Disable optimization for tag download to include only tags that have policies
> -
>
> Key: RANGER-1437
> URL: https://issues.apache.org/jira/browse/RANGER-1437
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.0
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Minor
> Fix For: 1.0.0, 0.7.1
>
>
> It is useful to download tagged entities to components even when there is no 
> enabled policy for the tag; mainly for verification and auditing purpose. 
> Therefore, by default, it is advised to disable this optimization.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (RANGER-1414) Ranger Hive Authorizer API for row-filtering and column-masking need only return those tables that need masking/filtering

2017-03-14 Thread Velmurugan Periasamy (JIRA) 

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

Velmurugan Periasamy updated RANGER-1414:
-
Fix Version/s: (was: master)
   1.0.0

> Ranger Hive Authorizer API for row-filtering and column-masking need only 
> return those tables that need masking/filtering
> -
>
> Key: RANGER-1414
> URL: https://issues.apache.org/jira/browse/RANGER-1414
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.0
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
> Fix For: 1.0.0, 0.7.1
>
>
> Currently, Ranger Hive authorizer implementation of 
> applyRowFilterAndColumnMasking() API returns all privileged objects given to 
> it as argument. It needs to return only those objects to which 
> row-filter/column-mask apply per Ranger policies.
> CC: [~hagleitn], [~ashutoshc], [~wzheng]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty

2017-03-14 Thread Velmurugan Periasamy (JIRA) 

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

Velmurugan Periasamy updated RANGER-1446:
-
Fix Version/s: (was: master)
   1.0.0

> Ranger Solr Plugin does not work when the collection list in the request is 
> empty
> -
>
> Key: RANGER-1446
> URL: https://issues.apache.org/jira/browse/RANGER-1446
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 0.7.0, 0.6.1, 0.6.2, 0.6.3
>Reporter: Yan
>Assignee: Yan
>Priority: Critical
> Fix For: 1.0.0, 0.7.1
>
> Attachments: 
> 0001-Ranger-1446-Ranger-Solr-Plugin-does-not-work-when-th.patch
>
>
> The fix of Ranger-1095 set the initial value of "denied" to "true" from the 
> previous "false". One impact of this change is that, when 
> context.getCollectionRequests() is empty which could be the case in many 
> invocations Solr makes to Ranger on authorization per client request, the 
> permission is plainly denied without going to Ranger policy engine. So the 
> fix changed the default behavior related "denied".
> A proper fix of Ranger-1095 IMO should be just to set the "denied" to "true" 
> in the catch block without changing the initial value of the variable.
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (RANGER-1443) Ranger binds to 127.0.0.1 after enabling ssl

2017-03-14 Thread Selvamohan Neethiraj (JIRA) 

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

Selvamohan Neethiraj resolved RANGER-1443.
--
Resolution: Invalid

Based on the comment above, I am resolving this as Invalid jira

> Ranger binds to 127.0.0.1 after enabling ssl
> 
>
> Key: RANGER-1443
> URL: https://issues.apache.org/jira/browse/RANGER-1443
> Project: Ranger
>  Issue Type: Bug
>  Components: admin
>Affects Versions: 0.6.2
>Reporter: Yujie Li
>Assignee: Pradeep Agrawal
>
> With http, Ranger binds with 0.0.0.0. But after enabling ssl, it only listens 
> to 127.0.0.1 (localhost). Other IPs can't access to Ranger UI.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (RANGER-1443) Ranger binds to 127.0.0.1 after enabling ssl

2017-03-14 Thread Yujie Li (JIRA) 

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

Yujie Li edited comment on RANGER-1443 at 3/14/17 9:36 PM:
---

[~pradeep.agrawal]
Hello, please delete this since I mistook the shutdown port as the ssl port. I 
checked and Ranger doesn't have this issue at all.

Sorry for confusion.


was (Author: yujie.li):
[~pradeep.agrawal]
Hello, please delete this thi since I mistook the shutdown port as the ssl 
port. I checked and Ranger doesn't have this issue at all.

Sorry for confusion.

> Ranger binds to 127.0.0.1 after enabling ssl
> 
>
> Key: RANGER-1443
> URL: https://issues.apache.org/jira/browse/RANGER-1443
> Project: Ranger
>  Issue Type: Bug
>  Components: admin
>Affects Versions: 0.6.2
>Reporter: Yujie Li
>Assignee: Pradeep Agrawal
>
> With http, Ranger binds with 0.0.0.0. But after enabling ssl, it only listens 
> to 127.0.0.1 (localhost). Other IPs can't access to Ranger UI.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (RANGER-1443) Ranger binds to 127.0.0.1 after enabling ssl

2017-03-14 Thread Yujie Li (JIRA) 

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

Yujie Li commented on RANGER-1443:
--

[~pradeep.agrawal]
Hello, please delete this thi since I mistook the shutdown port as the ssl 
port. I checked and Ranger doesn't have this issue at all.

Sorry for confusion.

> Ranger binds to 127.0.0.1 after enabling ssl
> 
>
> Key: RANGER-1443
> URL: https://issues.apache.org/jira/browse/RANGER-1443
> Project: Ranger
>  Issue Type: Bug
>  Components: admin
>Affects Versions: 0.6.2
>Reporter: Yujie Li
>Assignee: Pradeep Agrawal
>
> With http, Ranger binds with 0.0.0.0. But after enabling ssl, it only listens 
> to 127.0.0.1 (localhost). Other IPs can't access to Ranger UI.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (RANGER-1442) https port not configurable

2017-03-14 Thread Yujie Li (JIRA) 

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

Yujie Li commented on RANGER-1442:
--

[~pradeep.agrawal]

hello, sorry I made a mistake and took the shutdown port as ssl port. I tested 
and ssl port is configurable. Please help delete this JIRA.

> https port not configurable
> ---
>
> Key: RANGER-1442
> URL: https://issues.apache.org/jira/browse/RANGER-1442
> Project: Ranger
>  Issue Type: Bug
>  Components: admin
>Affects Versions: 0.6.2
>Reporter: Yujie Li
>Assignee: Pradeep Agrawal
> Fix For: 0.6.2
>
> Attachments: 0001-RANGER-1442-https-port-not-configurable.patch
>
>
> Ranger doesn't take the https port value (default 6182) from 
> ranger-admin-site.xml and uses hardcoded value (6185) after enabling SSL



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Review Request 57603: RANGER-1455 - Incorrect conf dir in scripts for Hadoop

2017-03-14 Thread Colm O hEigeartaigh 

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

Review request for ranger.


Bugs: RANGER-1455
https://issues.apache.org/jira/browse/RANGER-1455


Repository: ranger


Description
---

If I run the start-enable-hdfs.sh script for the hdfs plugin against Hadoop 
2.7.3 I get the error:

ERROR: Unable to find the conf directory of component [hadoop];

Instead of "conf" it should be using the value "etc/hadoop". This is the 
default conf directory location for Hadoop post 2.0.


Diffs
-

  agents-common/scripts/enable-agent.sh 9270c5f 


Diff: https://reviews.apache.org/r/57603/diff/1/


Testing
---

Tested it with Hadoop 2.7.3


Thanks,

Colm O hEigeartaigh

[jira] [Updated] (RANGER-1455) Incorrect conf dir in scripts for Hadoop

2017-03-14 Thread Colm O hEigeartaigh (JIRA) 

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

Colm O hEigeartaigh updated RANGER-1455:

Attachment: 0001-RANGER-1455-Incorrect-conf-dir-in-scripts-for-Hadoop.patch

> Incorrect conf dir in scripts for Hadoop
> 
>
> Key: RANGER-1455
> URL: https://issues.apache.org/jira/browse/RANGER-1455
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 1.0.0, 0.7.1
>
> Attachments: 
> 0001-RANGER-1455-Incorrect-conf-dir-in-scripts-for-Hadoop.patch
>
>
> If I run the start-enable-hdfs.sh script for the hdfs plugin against Hadoop 
> 2.7.3 I get the error:
> ERROR: Unable to find the conf directory of component [hadoop];
> Instead of "conf" it should be using the value "etc/hadoop". This is the 
> default conf directory location for Hadoop post 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (RANGER-1455) Incorrect conf dir in scripts for Hadoop

2017-03-14 Thread Colm O hEigeartaigh (JIRA) 
Colm O hEigeartaigh created RANGER-1455:
---

 Summary: Incorrect conf dir in scripts for Hadoop
 Key: RANGER-1455
 URL: https://issues.apache.org/jira/browse/RANGER-1455
 Project: Ranger
  Issue Type: Bug
  Components: plugins
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
 Fix For: 1.0.0, 0.7.1


If I run the start-enable-hdfs.sh script for the hdfs plugin against Hadoop 
2.7.3 I get the error:

ERROR: Unable to find the conf directory of component [hadoop];

Instead of "conf" it should be using the value "etc/hadoop". This is the 
default conf directory location for Hadoop post 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 57588: Ranger KMS failed to start with Exception: More than one Master Key exists

2017-03-14 Thread Pradeep Agrawal 

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


Ship it!




Ship It!

- Pradeep Agrawal


On March 14, 2017, 7:23 a.m., Ankita Sinha wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57588/
> ---
> 
> (Updated March 14, 2017, 7:23 a.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
> Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja 
> Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1453
> https://issues.apache.org/jira/browse/RANGER-1453
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger KMS failed to start with Exception: More than one Master Key exists
> ```java
> log4j:WARN No such property [maxFileSize] in 
> org.apache.log4j.DailyRollingFileAppender.
> java.lang.Exception: More than one Master Key exists
>   at 
> org.apache.hadoop.crypto.key.RangerMasterKey.getEncryptedMK(RangerMasterKey.java:143)
>   at 
> org.apache.hadoop.crypto.key.RangerMasterKey.getMasterKey(RangerMasterKey.java:71)
>   at 
> org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:106)
>   at 
> org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
>   at 
> org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
>   at 
> org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:176)
>   at 
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
>   at 
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
>   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
>   at 
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
>   at 
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> ```
> 
> 
> Diffs
> -
> 
>   kms/scripts/db/mysql/kms_core_db.sql f753f7e 
>   kms/scripts/db/oracle/kms_core_db_oracle.sql fd8b0e4 
>   kms/scripts/db/postgres/kms_core_db_postgres.sql 048cb0c 
>   kms/scripts/db/sqlanywhere/kms_core_db_sqlanywhere.sql fd7abdd 
>   kms/scripts/db/sqlserver/kms_core_db_sqlserver.sql 6567d3b 
>   kms/src/main/java/org/apache/ranger/kms/dao/BaseDao.java f2dc633 
>   security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java c1cbfa0 
>   security-admin/src/main/java/org/apache/ranger/common/RangerProperties.java 
> 3a5d1c8 
>   security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
> 6ca2d22 
>   src/main/assembly/kms.xml 5c65c77 
> 
> 
> Diff: https://reviews.apache.org/r/57588/diff/1/
> 
> 
> Testing
> ---
> 
> 1. Tested Ranger KMS with all key operations as well as zone operations
> 2. Tested Ranger KMS with all supported DB flavor
> 
> 
> Thanks,
> 
> Ankita Sinha
> 
>

Re: Review Request 57585: RANGER-1451: Incorrect error message for hadoop security authentication

2017-03-14 Thread Colm O hEigeartaigh 

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


Ship it!




Ship It!

- Colm O hEigeartaigh


On March 14, 2017, 4:03 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57585/
> ---
> 
> (Updated March 14, 2017, 4:03 a.m.)
> 
> 
> Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
> Neethiraj, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1451
> https://issues.apache.org/jira/browse/RANGER-1451
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> In hadoop security authentication, there are some error message doesn't match 
> the logic.
> if (fsDefaultName.isEmpty())  {
>   throw new IllegalArgumentException("Value for neither fs.default.name 
> is specified");
> }
> It should be not specified here.
> 
> 
> Diffs
> -
> 
>   
> hdfs-agent/src/main/java/org/apache/ranger/services/hdfs/client/HdfsClient.java
>  c5331a3 
> 
> 
> Diff: https://reviews.apache.org/r/57585/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Review Request 57533: RANGER-1448 : Change of import / export icons on Ranger UI

2017-03-14 Thread Ankita Sinha 

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


Ship it!




Ship It!

- Ankita Sinha


On March 11, 2017, 5:12 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57533/
> ---
> 
> (Updated March 11, 2017, 5:12 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Mehul Parikh, Pradeep Agrawal, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1448
> https://issues.apache.org/jira/browse/RANGER-1448
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> To make it more intuitive for end users, need to change icons used for import 
> / export feature in landing page.
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/webapp/templates/common/ServiceManagerLayout_tmpl.html
>  acaabce 
>   security-admin/src/main/webapp/templates/reports/UserAccessLayout_tmpl.html 
> 13d6776 
> 
> 
> Diff: https://reviews.apache.org/r/57533/diff/1/
> 
> 
> Testing
> ---
> 
> Verified links associated with icons to work as expected.
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Review Request 57588: Ranger KMS failed to start with Exception: More than one Master Key exists

2017-03-14 Thread Ankita Sinha 

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

Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja 
Polavarapu, and Velmurugan Periasamy.


Bugs: RANGER-1453
https://issues.apache.org/jira/browse/RANGER-1453


Repository: ranger


Description
---

Ranger KMS failed to start with Exception: More than one Master Key exists
```java
log4j:WARN No such property [maxFileSize] in 
org.apache.log4j.DailyRollingFileAppender.
java.lang.Exception: More than one Master Key exists
at 
org.apache.hadoop.crypto.key.RangerMasterKey.getEncryptedMK(RangerMasterKey.java:143)
at 
org.apache.hadoop.crypto.key.RangerMasterKey.getMasterKey(RangerMasterKey.java:71)
at 
org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:106)
at 
org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
at 
org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
at 
org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:176)
at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
```


Diffs
-

  kms/scripts/db/mysql/kms_core_db.sql f753f7e 
  kms/scripts/db/oracle/kms_core_db_oracle.sql fd8b0e4 
  kms/scripts/db/postgres/kms_core_db_postgres.sql 048cb0c 
  kms/scripts/db/sqlanywhere/kms_core_db_sqlanywhere.sql fd7abdd 
  kms/scripts/db/sqlserver/kms_core_db_sqlserver.sql 6567d3b 
  kms/src/main/java/org/apache/ranger/kms/dao/BaseDao.java f2dc633 
  security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java c1cbfa0 
  security-admin/src/main/java/org/apache/ranger/common/RangerProperties.java 
3a5d1c8 
  security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
6ca2d22 
  src/main/assembly/kms.xml 5c65c77 


Diff: https://reviews.apache.org/r/57588/diff/1/


Testing
---

1. Tested Ranger KMS with all key operations as well as zone operations
2. Tested Ranger KMS with all supported DB flavor


Thanks,

Ankita Sinha

[jira] [Created] (RANGER-1453) Ranger KMS failed to start with Exception: More than one Master Key exists

2017-03-14 Thread Ankita Sinha (JIRA) 
Ankita Sinha created RANGER-1453:


 Summary: Ranger KMS failed to start with Exception: More than one 
Master Key exists
 Key: RANGER-1453
 URL: https://issues.apache.org/jira/browse/RANGER-1453
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 0.7.0
Reporter: Ankita Sinha
Assignee: Ankita Sinha
 Fix For: 0.7.1


Ranger KMS failed to start with Exception: More than one Master Key exists
{code}
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was 
removed in 8.0
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer 
loadConfig
SEVERE: Load configuration fail. Reason: java.io.FileNotFoundException: 
/usr/hdp/2.6.0.2-4/ranger-kms/ews/ranger-admin-default-site.xml (No such file 
or directory)
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer start
INFO: Webapp file =./webapp, webAppName = /kms
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer start
INFO: Adding webapp [/kms] = path [./webapp] .
Mar 07, 2017 7:22:30 AM org.apache.ranger.server.tomcat.EmbeddedServer start
INFO: Finished init of webapp [/kms] = path [./webapp].
Mar 07, 2017 7:22:30 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-9292"]
Mar 07, 2017 7:22:30 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat
Mar 07, 2017 7:22:30 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.68
Mar 07, 2017 7:22:30 AM org.apache.catalina.startup.ContextConfig 
getDefaultWebXmlFragment
INFO: No global web.xml found
Mar 07, 2017 7:22:36 AM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug 
logging for this logger for a complete list of JARs that were scanned but no 
TLDs were found in them. Skipping unneeded JARs during scanning can improve 
startup time and JSP compilation time.
log4j:WARN No such property [maxFileSize] in 
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in 
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in 
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxFileSize] in 
org.apache.log4j.DailyRollingFileAppender.
java.lang.Exception: More than one Master Key exists
at 
org.apache.hadoop.crypto.key.RangerMasterKey.getEncryptedMK(RangerMasterKey.java:143)
at 
org.apache.hadoop.crypto.key.RangerMasterKey.getMasterKey(RangerMasterKey.java:71)
at 
org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:106)
at 
org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
at 
org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
at 
org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:176)
at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
java.lang.Exception: No Master Key Found
at 
org.apache.hadoop.crypto.key.RangerMasterKey.getMasterKey(RangerMasterKey.java:75)
at 
org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:106)
at 
org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
at 
org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
at 
org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:176)
at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5068)
at 
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5584)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1572)
at 
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1562)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at