[jira] [Assigned] (RANGER-1482) 'Ranger KMS' repo is not getting created in manual installation
[ https://issues.apache.org/jira/browse/RANGER-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Kulkarni reassigned RANGER-1482: -- Assignee: Abhay Kulkarni > 'Ranger KMS' repo is not getting created in manual installation > --- > > Key: RANGER-1482 > URL: https://issues.apache.org/jira/browse/RANGER-1482 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Mehul Parikh >Assignee: Abhay Kulkarni > Fix For: 0.7.1 > > > In manual installation of 'Ranger KMS' the repo is not getting created if > 'HIVE' and 'HDFS' user are not present in Ranger DB. > While Manual Repo creation the API which is being called is > "/service/plugins/services" which doesn't handle creation of 'HIVE' and > 'HDFS' user. > whereas for KMS Repo creation if we use API "/service/public/v2/api/service" > which handles creation of 'HIVE' and 'HDFS' user if does not exists. > Note: Ranger KMS default policy gives access to Hive and HDFS user so this > issue is seen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1482) 'Ranger KMS' repo is not getting created in manual installation
Mehul Parikh created RANGER-1482: Summary: 'Ranger KMS' repo is not getting created in manual installation Key: RANGER-1482 URL: https://issues.apache.org/jira/browse/RANGER-1482 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 0.7.1 Reporter: Mehul Parikh Fix For: 0.7.1 In manual installation of 'Ranger KMS' the repo is not getting created if 'HIVE' and 'HDFS' user are not present in Ranger DB. While Manual Repo creation the API which is being called is "/service/plugins/services" which doesn't handle creation of 'HIVE' and 'HDFS' user. whereas for KMS Repo creation if we use API "/service/public/v2/api/service" which handles creation of 'HIVE' and 'HDFS' user if does not exists. Note: Ranger KMS default policy gives access to Hive and HDFS user so this issue is seen. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1481) Capture cluster name in ranger audit info
bhavik patel created RANGER-1481: Summary: Capture cluster name in ranger audit info Key: RANGER-1481 URL: https://issues.apache.org/jira/browse/RANGER-1481 Project: Ranger Issue Type: Bug Components: Ranger Reporter: bhavik patel Assignee: bhavik patel Fix For: 0.7.1 In the HDC shared services setup, shared datalake cluster contains ranger admin service and ephemeral clusters have ranger hive plugin that connect to ranger admin service on remote datalake cluster. Ranger captures client/plugin ip in access and plugin audit info. As there are multiple clusters in cloud environment, its difficult to map this ip to the cluster it belongs to. Its userful to have the ambari cluster name in the access and plugin audit info. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Review Request 57905: RANGER-1474 : On SP12, hive policy page opens up with UDF as default under resources, rather than table.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57905/#review170360 --- Ship it! Ship It! - Gautam Borad On March 24, 2017, 5:52 a.m., Nitin Galave wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/57905/ > --- > > (Updated March 24, 2017, 5:52 a.m.) > > > Review request for ranger, Ankita Sinha, Gautam Borad, Mehul Parikh, Navina > Ramesh, Pradeep Agrawal, and Velmurugan Periasamy. > > > Bugs: RANGER-1474 > https://issues.apache.org/jira/browse/RANGER-1474 > > > Repository: ranger > > > Description > --- > > On Suse env, when add Hive policy page opens up, it shows 'UDF' as default > (Hive Column * is not seen) rather than 'table', under resources. > Till now, users are used to getting 'table' by default under resources and > also that's the more used option between 'table' and 'udf'. > > > Diffs > - > > security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js > 283e626 > > > Diff: https://reviews.apache.org/r/57905/diff/1/ > > > Testing > --- > > Verified population of resources for all services(hdfs, hive, hbase, > atlas,knox) and also tested policy CRUD for the same. > > > Thanks, > > Nitin Galave > >
Review Request 57990: RANGER-1480 : First version of the druid plugin. Only 'unsecure' mode is tested, and the autocomplete for druid datasource is not implemented
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57990/ --- Review request for ranger. Bugs: RANGER-1480 https://issues.apache.org/jira/browse/RANGER-1480 Repository: ranger Description --- Druid plugin - which should be deployed as a druid extension, and the druid-service which should be running inside the ranger admin. To make it more simple, the plugin is built into one jar - which is still huge ~25MB, but the deployment is more straightforward. As ranger haven't had 3 level module system, minor fixes needed by the maven build. Diffs - agents-common/src/main/resources/service-defs/ranger-servicedef-druid.json PRE-CREATION druid/druid-service/pom.xml PRE-CREATION druid/druid-service/src/main/java/org/apache/ranger/service/druid/RangerDruidService.java PRE-CREATION druid/plugin-druid/conf/ranger-druid-audit.xml PRE-CREATION druid/plugin-druid/conf/ranger-druid-security.xml PRE-CREATION druid/plugin-druid/pom.xml PRE-CREATION druid/plugin-druid/src/main/java/org/apache/ranger/druid/DruidResource.java PRE-CREATION druid/plugin-druid/src/main/java/org/apache/ranger/druid/PluginConfig.java PRE-CREATION druid/plugin-druid/src/main/java/org/apache/ranger/druid/RangerAuthorizationInfo.java PRE-CREATION druid/plugin-druid/src/main/java/org/apache/ranger/druid/RangerFilter.java PRE-CREATION druid/plugin-druid/src/main/java/org/apache/ranger/druid/RangerFilterHolder.java PRE-CREATION druid/plugin-druid/src/main/java/org/apache/ranger/druid/RangerPlugin.java PRE-CREATION druid/plugin-druid/src/main/resources/META-INF/services/io.druid.initialization.DruidModule PRE-CREATION druid/pom.xml PRE-CREATION pom.xml 4fb62e25124bc8ddd67c349cbc440c7173ceb42f Diff: https://reviews.apache.org/r/57990/diff/1/ Testing --- Thanks, Zsombor Gegesy
[jira] [Updated] (RANGER-1479) Plugins couldnt load settings xml files from the classpath, if they are inside a jar
[ https://issues.apache.org/jira/browse/RANGER-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zsombor Gegesy updated RANGER-1479: --- Attachment: 0001-RANGER-1479-Fix-bug-in-ranger-security-audit-.xml-lo.patch > Plugins couldnt load settings xml files from the classpath, if they are > inside a jar > > > Key: RANGER-1479 > URL: https://issues.apache.org/jira/browse/RANGER-1479 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 0.7.0 >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy > Labels: configuration, plugins > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1479-Fix-bug-in-ranger-security-audit-.xml-lo.patch > > > RangerConfiguration first checks, if the necessary xml files are on the > classpath, and after it tries to convert it to a file path, check that file > is on the filesystem, and convert that path to back to URL. If the > configurations are inside a jar, then this will fail very badly (the > resource url will be something file://config.jar!/ranger-services.xml ) > If the conversion is removed, it would work pretty nicely -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1480) Implement plugin for Druid
[ https://issues.apache.org/jira/browse/RANGER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zsombor Gegesy updated RANGER-1480: --- Attachment: 0001-RANGER-1480-First-version-of-the-druid-plugin.-Only-.patch > Implement plugin for Druid > -- > > Key: RANGER-1480 > URL: https://issues.apache.org/jira/browse/RANGER-1480 > Project: Ranger > Issue Type: New Feature > Components: admin, plugins >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy > Attachments: > 0001-RANGER-1480-First-version-of-the-druid-plugin.-Only-.patch > > > Druid is a high-performance, column-oriented, distributed data store, which > has an extension mechanism to incorporate various functionalities, for > example an external authorization system - just like ranger. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1480) Implement plugin for Druid
Zsombor Gegesy created RANGER-1480: -- Summary: Implement plugin for Druid Key: RANGER-1480 URL: https://issues.apache.org/jira/browse/RANGER-1480 Project: Ranger Issue Type: New Feature Components: admin, plugins Reporter: Zsombor Gegesy Assignee: Zsombor Gegesy Druid is a high-performance, column-oriented, distributed data store, which has an extension mechanism to incorporate various functionalities, for example an external authorization system - just like ranger. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Review Request 57988: RANGER-1479 : Fix bug in ranger-*-(security/audit).xml loading, which prevented loading from JAR's
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57988/ --- Review request for ranger. Bugs: RANGER-1479 https://issues.apache.org/jira/browse/RANGER-1479 Repository: ranger Description --- RangerConfiguration first checks, if the necessary xml files are on the classpath, and after it tries to convert it to a file path, check that file is on the filesystem, and convert that path to back to URL. If the configurations are inside a jar, then this will fail very badly (the resource url will be something file://config.jar!/ranger-services.xml ) If the conversion is removed, it would work pretty nicely Diffs - agents-common/src/main/java/org/apache/ranger/authorization/hadoop/config/RangerConfiguration.java d81f6b93a6847877a178c88086dea6ff8670f20e Diff: https://reviews.apache.org/r/57988/diff/1/ Testing --- Thanks, Zsombor Gegesy
[jira] [Created] (RANGER-1479) Plugins couldnt load settings xml files from the classpath, if they are inside a jar
Zsombor Gegesy created RANGER-1479: -- Summary: Plugins couldnt load settings xml files from the classpath, if they are inside a jar Key: RANGER-1479 URL: https://issues.apache.org/jira/browse/RANGER-1479 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 0.7.0 Reporter: Zsombor Gegesy Assignee: Zsombor Gegesy Fix For: 1.0.0 RangerConfiguration first checks, if the necessary xml files are on the classpath, and after it tries to convert it to a file path, check that file is on the filesystem, and convert that path to back to URL. If the configurations are inside a jar, then this will fail very badly (the resource url will be something file://config.jar!/ranger-services.xml ) If the conversion is removed, it would work pretty nicely -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Review Request 57987: RANGER-1478 : Small refactor in RangerPolicyEngineCache and RangerPolicyEngineOptions, to avoid looking up RangerConfiguration everytime, and try to write the RPEO fields only fr
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57987/ --- Review request for ranger. Bugs: RANGER-1478 https://issues.apache.org/jira/browse/RANGER-1478 Repository: ranger Description --- RangerPolicyEngineOptions has a lot of public fields, which is written from various places from the code base, which should be avoided. That object is configured from RangerConfiguration, but in the middle of the plugin initialization code, which makes this a bit more complex, than it should be. Suggestions: RangerConfiguration should be treated as an object, not a static facade for a couple of config values RangerPolicyEngineOptions should get his configuration from directly the RangerConfiguration, in an explicit, encapsulated way. Diffs - agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyEngineCache.java 5376b5205cb7b0b0a6f7b827198bbee055191f0f agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyEngineOptions.java a9027bca75b66836c87fc0508f99ef9787d99512 agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBasePlugin.java acf8d1545536d84b0f7d20b971655fe20c67cfa6 security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 617631949244993e46f5b0ab2168acc6ed0bf634 Diff: https://reviews.apache.org/r/57987/diff/1/ Testing --- Thanks, Zsombor Gegesy
[jira] [Updated] (RANGER-1478) Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many times
[ https://issues.apache.org/jira/browse/RANGER-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zsombor Gegesy updated RANGER-1478: --- Attachment: 0001-RANGER-1478-Small-refactor-in-RangerPolicyEngineCach.patch > Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many > times > --- > > Key: RANGER-1478 > URL: https://issues.apache.org/jira/browse/RANGER-1478 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 0.7.0 >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy >Priority: Minor > Labels: code-cleanup > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1478-Small-refactor-in-RangerPolicyEngineCach.patch > > > RangerPolicyEngineOptions has a lot of public fields, which is written from > various places from the code base, which should be avoided. That object is > configured from RangerConfiguration, but in the middle of the plugin > initialization code, which makes this a bit more complex, than it should be. > Suggestions: > * RangerConfiguration should be treated as an object, not a static facade for > a couple of config values > * RangerPolicyEngineOptions should get his configuration from directly the > RangerConfiguration, in an explicit, encapsulated way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1478) Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many times
Zsombor Gegesy created RANGER-1478: -- Summary: Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many times Key: RANGER-1478 URL: https://issues.apache.org/jira/browse/RANGER-1478 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: 0.7.0 Reporter: Zsombor Gegesy Assignee: Zsombor Gegesy Priority: Minor Fix For: 1.0.0 RangerPolicyEngineOptions has a lot of public fields, which is written from various places from the code base, which should be avoided. That object is configured from RangerConfiguration, but in the middle of the plugin initialization code, which makes this a bit more complex, than it should be. Suggestions: * RangerConfiguration should be treated as an object, not a static facade for a couple of config values * RangerPolicyEngineOptions should get his configuration from directly the RangerConfiguration, in an explicit, encapsulated way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
