[jira] [Updated] (RANGER-4927) Ranger security admin build fails as karma plugin fails to start in Ubuntu 22.04 LTS
[
https://issues.apache.org/jira/browse/RANGER-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-4927:
-
Description:
Hi Team, while building Ranger repository in Ubuntu 22.04 LTS it fails for
security-admin sub-module, as karma plugin fails to start.
{code:java}
[INFO] 06 09 2024 12:29:50.147:INFO [karma-server]: Karma v3.1.4 server started
at http://0.0.0.0:9876/
[INFO] 06 09 2024 12:29:50.150:INFO [launcher]: Launching browsers PhantomJS
with concurrency unlimited
[INFO] 06 09 2024 12:29:50.156:INFO [launcher]: Starting browser PhantomJS
[INFO] 06 09 2024 12:29:50.172:ERROR [phantomjs.launcher]: Auto configuration
failed
[INFO] 131752149018560:error:25066067:DSO support routines:DLFCN_LOAD:could not
load the shared library:dso_dlfcn.c:185:filename(libproviders.so):
libproviders.so: cannot open shared object file: No such file or directory
[INFO] 131752149018560:error:25070067:DSO support routines:DSO_load:could not
load the shared library:dso_lib.c:244:
[INFO] 131752149018560:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
[INFO] 131752149018560:error:0E076071:configuration file
routines:MODULE_RUN:unknown module name:conf_mod.c:222:module=providers
[INFO]
[INFO] 06 09 2024 12:29:50.174:ERROR [launcher]: Cannot start PhantomJS
[INFO] Auto configuration failed
[INFO] 131752149018560:error:25066067:DSO support routines:DLFCN_LOAD:could not
load the shared library:dso_dlfcn.c:185:filename(libproviders.so):
libproviders.so: cannot open shared object file: No such file or directory
[INFO] 131752149018560:error:25070067:DSO support routines:DSO_load:could not
load the shared library:dso_lib.c:244:
[INFO] 131752149018560:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
[INFO] 131752149018560:error:0E076071:configuration file
routines:MODULE_RUN:unknown module name:conf_mod.c:222:module=providers
[INFO]
[INFO] 06 09 2024 12:29:50.174:ERROR [launcher]: PhantomJS stdout:
[INFO] 06 09 2024 12:29:50.174:ERROR [launcher]: PhantomJS stderr: Auto
configuration failed
[INFO] 131752149018560:error:25066067:DSO support routines:DLFCN_LOAD:could not
load the shared library:dso_dlfcn.c:185:filename(libproviders.so):
libproviders.so: cannot open shared object file: No such file or directory
[INFO] 131752149018560:error:25070067:DSO support routines:DSO_load:could not
load the shared library:dso_lib.c:244:
[INFO] 131752149018560:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
[INFO] 131752149018560:error:0E076071:configuration file
routines:MODULE_RUN:unknown module name:conf_mod.c:222:module=providers
[INFO]
[INFO] 06 09 2024 12:29:50.177:INFO [launcher]: Trying to start PhantomJS again
(1/2).
[INFO] 06 09 2024 12:29:50.198:ERROR [phantomjs.launcher]: Auto configuration
failed
[INFO] 140049643886528:error:25066067:DSO support routines:DLFCN_LOAD:could not
load the shared library:dso_dlfcn.c:185:filename(libproviders.so):
libproviders.so: cannot open shared object file: No such file or directory
[INFO] 140049643886528:error:25070067:DSO support routines:DSO_load:could not
load the shared library:dso_lib.c:244:
[INFO] 140049643886528:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
[INFO] 140049643886528:error:0E076071:configuration file
routines:MODULE_RUN:unknown module name:conf_mod.c:222:module=providers
[INFO]
[INFO] 06 09 2024 12:29:50.199:ERROR [launcher]: Cannot start PhantomJS
[INFO] Auto configuration failed
[INFO] 140049643886528:error:25066067:DSO support routines:DLFCN_LOAD:could not
load the shared library:dso_dlfcn.c:185:filename(libproviders.so):
libproviders.so: cannot open shared object file: No such file or directory
[INFO] 140049643886528:error:25070067:DSO support routines:DSO_load:could not
load the shared library:dso_lib.c:244:
[INFO] 140049643886528:error:0E07506E:configuration file
routines:MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers,
path=providers
[INFO] 140049643886528:error:0E076071:configuration file
routines:MODULE_RUN:unknown module name:conf_mod.c:222:module=providers
[INFO]
[INFO] 06 09 2024 12:29:50.200:ERROR [launcher]: PhantomJS stdout:
[INFO] 06 09 2024 12:29:50.200:ERROR [launcher]: PhantomJS stderr: Auto
configuration failed
[INFO] 140049643886528:error:25066067:DSO support routines:DLFCN_LOAD:could not
load the shared library:dso_dlfcn.c:185:filename(libproviders.so):
libproviders.so: cannot open shared object file: No such file or directory
[INFO] 140049643886528:error:25070067:DSO support routines:DSO_load:could not
load the shared library:dso_lib.c:244:
[INFO] 140049643886528:error:0E07506E:con
[jira] [Assigned] (RANGER-4927) Ranger security admin build fails as karma plugin fails to start in Ubuntu 22.04 LTS
[ https://issues.apache.org/jira/browse/RANGER-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-4927: Assignee: Dhaval Rajpara > Ranger security admin build fails as karma plugin fails to start in Ubuntu > 22.04 LTS > > > Key: RANGER-4927 > URL: https://issues.apache.org/jira/browse/RANGER-4927 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Dhaval Rajpara >Priority: Major > > Hi Team, while building Ranger repository in Ubuntu 22.04 LTS it fails for > security-admin sub-module, as karma plugin fails to start. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4848) Migrate Ranger modules to junit5 - phase 3
[ https://issues.apache.org/jira/browse/RANGER-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4848: - Description: This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-plugins-audit # ranger-plugins-common # ranger-knox-plugin # ranger-kudu-plugin # ranger-kylin-plugin # ranger-nifi-registry-plugin # ranger-nifi-plugin was: This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-hbase-plugin # ranger-hbase-plugin-shim # ranger-hdfs-plugin # ranger-hdfs-plugin-shim > Migrate Ranger modules to junit5 - phase 3 > -- > > Key: RANGER-4848 > URL: https://issues.apache.org/jira/browse/RANGER-4848 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # ranger-plugins-audit > # ranger-plugins-common > # ranger-knox-plugin > # ranger-kudu-plugin > # ranger-kylin-plugin > # ranger-nifi-registry-plugin > # ranger-nifi-plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4848) Migrate Ranger modules to junit5 - phase 3
Kishor Gollapalliwar created RANGER-4848: Summary: Migrate Ranger modules to junit5 - phase 3 Key: RANGER-4848 URL: https://issues.apache.org/jira/browse/RANGER-4848 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Fix For: 3.0.0 This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-hbase-plugin # ranger-hbase-plugin-shim # ranger-hdfs-plugin # ranger-hdfs-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4781) Upgrade graalvm to 22.3.3
Kishor Gollapalliwar created RANGER-4781: Summary: Upgrade graalvm to 22.3.3 Key: RANGER-4781 URL: https://issues.apache.org/jira/browse/RANGER-4781 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Upgrade graalvm to 22.3.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4730) Migrate Ranger modules to junit5 - phase 2
[ https://issues.apache.org/jira/browse/RANGER-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar resolved RANGER-4730. -- Resolution: Fixed commit: https://github.com/apache/ranger/commit/8a3747edaf864ecbde3b48324663d668a81775ef > Migrate Ranger modules to junit5 - phase 2 > -- > > Key: RANGER-4730 > URL: https://issues.apache.org/jira/browse/RANGER-4730 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # ranger-kms > # ranger-kms-plugin > # ranger-kms-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4730) Migrate Ranger modules to junit5 - phase 2
[ https://issues.apache.org/jira/browse/RANGER-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823040#comment-17823040 ] Kishor Gollapalliwar commented on RANGER-4730: -- RR: https://reviews.apache.org/r/74923/ > Migrate Ranger modules to junit5 - phase 2 > -- > > Key: RANGER-4730 > URL: https://issues.apache.org/jira/browse/RANGER-4730 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # ranger-kms > # ranger-kms-plugin > # ranger-kms-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4731) Migrate Ranger modules to junit5 - hdfs, hbase
[ https://issues.apache.org/jira/browse/RANGER-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823028#comment-17823028 ] Kishor Gollapalliwar commented on RANGER-4731: -- These plugins are using underline component (hdfs/ hbase) classes in test classes. Hence they are dependent on underline classes. Since underline dependant classes are not using junit 5, we can not migrated these sub-modules/ plugins to junit 5 now. > Migrate Ranger modules to junit5 - hdfs, hbase > -- > > Key: RANGER-4731 > URL: https://issues.apache.org/jira/browse/RANGER-4731 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # ranger-hbase-plugin > # ranger-hbase-plugin-shim > # ranger-hdfs-plugin > # ranger-hdfs-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4731) Migrate Ranger modules to junit5 - hdfs, hbase
[ https://issues.apache.org/jira/browse/RANGER-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4731: - Description: This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-hbase-plugin # ranger-hbase-plugin-shim # ranger-hdfs-plugin # ranger-hdfs-plugin-shim was: This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-kms # ranger-kms-plugin # ranger-kms-plugin-shim > Migrate Ranger modules to junit5 - hdfs, hbase > -- > > Key: RANGER-4731 > URL: https://issues.apache.org/jira/browse/RANGER-4731 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # ranger-hbase-plugin > # ranger-hbase-plugin-shim > # ranger-hdfs-plugin > # ranger-hdfs-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4731) Migrate Ranger modules to junit5 - hdfs, hbase
Kishor Gollapalliwar created RANGER-4731: Summary: Migrate Ranger modules to junit5 - hdfs, hbase Key: RANGER-4731 URL: https://issues.apache.org/jira/browse/RANGER-4731 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Fix For: 3.0.0 This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-kms # ranger-kms-plugin # ranger-kms-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4730) Migrate Ranger modules to junit5 - phase 2
[ https://issues.apache.org/jira/browse/RANGER-4730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4730: - Description: This sub-task is responsible to migrate following maven sub-modules to junit5. # ranger-kms # ranger-kms-plugin # ranger-kms-plugin-shim was: This sub-task is responsible to migrate following maven sub-modules to junit5. # conditions-enrichers # credentialsbuilder # embeddedwebserver # jisql # ldapconfigcheck # ranger-atlas-plugin # ranger-atlas-plugin-shim # ranger-authn # ranger-common-ha # ranger-elasticsearch-plugin # ranger-elasticsearch-plugin-shim # ranger-hive-plugin # ranger-hive-plugin-shim # ranger-intg # ranger-kafka-plugin # ranger-kafka-plugin-shim > Migrate Ranger modules to junit5 - phase 2 > -- > > Key: RANGER-4730 > URL: https://issues.apache.org/jira/browse/RANGER-4730 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # ranger-kms > # ranger-kms-plugin > # ranger-kms-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4730) Migrate Ranger modules to junit5 - phase 2
Kishor Gollapalliwar created RANGER-4730: Summary: Migrate Ranger modules to junit5 - phase 2 Key: RANGER-4730 URL: https://issues.apache.org/jira/browse/RANGER-4730 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Fix For: 3.0.0 This sub-task is responsible to migrate following maven sub-modules to junit5. # conditions-enrichers # credentialsbuilder # embeddedwebserver # jisql # ldapconfigcheck # ranger-atlas-plugin # ranger-atlas-plugin-shim # ranger-authn # ranger-common-ha # ranger-elasticsearch-plugin # ranger-elasticsearch-plugin-shim # ranger-hive-plugin # ranger-hive-plugin-shim # ranger-intg # ranger-kafka-plugin # ranger-kafka-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4467) User Agent info not logged under "Login sessions" when login fails
[ https://issues.apache.org/jira/browse/RANGER-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798517#comment-17798517 ] Kishor Gollapalliwar commented on RANGER-4467: -- commit: https://github.com/apache/ranger/commit/5cfe87313bbd67af20f3c8b68f60f0af08e7d73c > User Agent info not logged under "Login sessions" when login fails > -- > > Key: RANGER-4467 > URL: https://issues.apache.org/jira/browse/RANGER-4467 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: suja s >Assignee: Rakesh Gupta >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4467.patch > > > STEPS TO REPRODUCE: > Provide wrong uname or password on Ranger admin UI so that login fails > Verify login sessions under Audits page > CURRENT BEHAVIOUR: > User Agent info is missing when login fails > EXPECTED BEHAVIOUR: > User Agent info should be displayed > IMPACT: > User Agent info missing when login fails. Its good to display this detail as > it helps in knowing how the login was tried in case of failed login attempts -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4559) Migrate Ranger modules to junit5 - phase 1
[ https://issues.apache.org/jira/browse/RANGER-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789802#comment-17789802 ] Kishor Gollapalliwar commented on RANGER-4559: -- RR: https://reviews.apache.org/r/74756/ > Migrate Ranger modules to junit5 - phase 1 > -- > > Key: RANGER-4559 > URL: https://issues.apache.org/jira/browse/RANGER-4559 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > This sub-task is responsible to migrate following maven sub-modules to junit5. > # conditions-enrichers > # credentialsbuilder > # embeddedwebserver > # jisql > # ldapconfigcheck > # ranger-atlas-plugin > # ranger-atlas-plugin-shim > # ranger-authn > # ranger-common-ha > # ranger-elasticsearch-plugin > # ranger-elasticsearch-plugin-shim > # ranger-hive-plugin > # ranger-hive-plugin-shim > # ranger-intg > # ranger-kafka-plugin > # ranger-kafka-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4559) Migrate Ranger modules to junit5 - phase 1
Kishor Gollapalliwar created RANGER-4559: Summary: Migrate Ranger modules to junit5 - phase 1 Key: RANGER-4559 URL: https://issues.apache.org/jira/browse/RANGER-4559 Project: Ranger Issue Type: Sub-task Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar This sub-task is responsible to migrate following maven sub-modules to junit5. # conditions-enrichers # credentialsbuilder # embeddedwebserver # jisql # ldapconfigcheck # ranger-atlas-plugin # ranger-atlas-plugin-shim # ranger-authn # ranger-common-ha # ranger-elasticsearch-plugin # ranger-elasticsearch-plugin-shim # ranger-hive-plugin # ranger-hive-plugin-shim # ranger-intg # ranger-kafka-plugin # ranger-kafka-plugin-shim -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4528) Add JUnit 5 support
[ https://issues.apache.org/jira/browse/RANGER-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-4528: Assignee: Kishor Gollapalliwar > Add JUnit 5 support > --- > > Key: RANGER-4528 > URL: https://issues.apache.org/jira/browse/RANGER-4528 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Goal of this phase is to add support for JUnit 5, so that JUnit 4 & JUnit 5 > both test should be supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4528) Add JUnit 5 support
Kishor Gollapalliwar created RANGER-4528: Summary: Add JUnit 5 support Key: RANGER-4528 URL: https://issues.apache.org/jira/browse/RANGER-4528 Project: Ranger Issue Type: Sub-task Components: Ranger Reporter: Kishor Gollapalliwar Goal of this phase is to add support for JUnit 5, so that JUnit 4 & JUnit 5 both test should be supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4527) Migrate to JUnit 5
Kishor Gollapalliwar created RANGER-4527: Summary: Migrate to JUnit 5 Key: RANGER-4527 URL: https://issues.apache.org/jira/browse/RANGER-4527 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Currently Ranger repository is using JUnit 4, and we should consider migrating to JUnit 5 due to following reasons. * JUnit 4 is not actively maintained * Everything which can be achieve in JUnit 4 can also be achieved in JUnit 5 * JUnit 5 has new features which not only give us more granular control but also help us better organise test The migration will be done in following phases # Add support for JUnit 5: In this phase we will add support for JUnit 5, hence JUnit 4 & JUnit 5 both supported # Migrate each maven sub-module at a time to JUnit 5 # Remove support for JUnit 4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4482) Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services
[ https://issues.apache.org/jira/browse/RANGER-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783614#comment-17783614 ] Kishor Gollapalliwar commented on RANGER-4482: -- master commit: https://github.com/apache/ranger/commit/cd8a752d008b417f3f7f01dccbcc6893571be629 > Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services > --- > > Key: RANGER-4482 > URL: https://issues.apache.org/jira/browse/RANGER-4482 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Attachments: 0001-RANGER-4482.patch > > > Tomcat needs be upgraded to 8.5.94 to address the below CVE. > CVE-2023-45648 > [https://nvd.nist.gov/vuln/detail/CVE-2023-45648] > CVE-2023-42795 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42795] > CVE-2023-42794 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42794] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4482) Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services
[ https://issues.apache.org/jira/browse/RANGER-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4482: - Fix Version/s: 3.0.0 > Upgrade Tomcat to 8.5.94 (for CVE fixes) in all Ranger services > --- > > Key: RANGER-4482 > URL: https://issues.apache.org/jira/browse/RANGER-4482 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Sanket Shelar >Assignee: Sanket Shelar >Priority: Major > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4482.patch > > > Tomcat needs be upgraded to 8.5.94 to address the below CVE. > CVE-2023-45648 > [https://nvd.nist.gov/vuln/detail/CVE-2023-45648] > CVE-2023-42795 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42795] > CVE-2023-42794 > [https://nvd.nist.gov/vuln/detail/CVE-2023-42794] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4495) Upgrade netty to 4.1.100-final
[ https://issues.apache.org/jira/browse/RANGER-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780826#comment-17780826 ] Kishor Gollapalliwar commented on RANGER-4495: -- RR: https://reviews.apache.org/r/74704/ > Upgrade netty to 4.1.100-final > -- > > Key: RANGER-4495 > URL: https://issues.apache.org/jira/browse/RANGER-4495 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Upgrade netty to 4.1.100-final or higher -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4495) Upgrade netty to 4.1.100-final
[ https://issues.apache.org/jira/browse/RANGER-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-4495: Assignee: Kishor Gollapalliwar (was: Pradeep Agrawal) > Upgrade netty to 4.1.100-final > -- > > Key: RANGER-4495 > URL: https://issues.apache.org/jira/browse/RANGER-4495 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Upgrade netty to 4.1.100-final or higher -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4402) Active role version is not updated while plugin download
[ https://issues.apache.org/jira/browse/RANGER-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4402: - Fix Version/s: 3.0.0 > Active role version is not updated while plugin download > > > Key: RANGER-4402 > URL: https://issues.apache.org/jira/browse/RANGER-4402 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > When plugin download, the active role version is not getting updated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4401) Configurable Graalvm features
[ https://issues.apache.org/jira/browse/RANGER-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766315#comment-17766315 ] Kishor Gollapalliwar commented on RANGER-4401: -- RR: https://reviews.apache.org/r/74588/ > Configurable Graalvm features > - > > Key: RANGER-4401 > URL: https://issues.apache.org/jira/browse/RANGER-4401 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Currently the only way of enabling GraalVm features/ options is by passing > JVM options. Which might not be feasible always. Hence we need a plugin > config, which will make GraalVm feature enabling configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4402) Active role version is not updated while plugin download
[ https://issues.apache.org/jira/browse/RANGER-4402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-4402: Assignee: Kishor Gollapalliwar > Active role version is not updated while plugin download > > > Key: RANGER-4402 > URL: https://issues.apache.org/jira/browse/RANGER-4402 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > When plugin download, the active role version is not getting updated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4402) Active role version is not updated while plugin download
Kishor Gollapalliwar created RANGER-4402: Summary: Active role version is not updated while plugin download Key: RANGER-4402 URL: https://issues.apache.org/jira/browse/RANGER-4402 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar When plugin download, the active role version is not getting updated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4401) Configurable Graalvm features
Kishor Gollapalliwar created RANGER-4401: Summary: Configurable Graalvm features Key: RANGER-4401 URL: https://issues.apache.org/jira/browse/RANGER-4401 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Currently the only way of enabling GraalVm features/ options is by passing JVM options. Which might not be feasible always. Hence we need a plugin config, which will make GraalVm feature enabling configurable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4371) Ranger authn - add doAs support for JWT authentication
[ https://issues.apache.org/jira/browse/RANGER-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4371: - Fix Version/s: 3.0.0 > Ranger authn - add doAs support for JWT authentication > -- > > Key: RANGER-4371 > URL: https://issues.apache.org/jira/browse/RANGER-4371 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > add doAs support for JWT based authentication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4371) Ranger authn - add doAs support for JWT authentication
Kishor Gollapalliwar created RANGER-4371: Summary: Ranger authn - add doAs support for JWT authentication Key: RANGER-4371 URL: https://issues.apache.org/jira/browse/RANGER-4371 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar add doAs support for JWT based authentication -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4310) Add group extracting from JWT functionality in Ranger
Kishor Gollapalliwar created RANGER-4310: Summary: Add group extracting from JWT functionality in Ranger Key: RANGER-4310 URL: https://issues.apache.org/jira/browse/RANGER-4310 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Currently the JWT support we have in Ranger does not offer, group extraction functionality/ feature. We need code to extract group information if present for JWT. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4182) Ranger Admin - Enable isRecursive option to additional default policies while service creation
[
https://issues.apache.org/jira/browse/RANGER-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-4182:
-
Fix Version/s: 3.0.0
> Ranger Admin - Enable isRecursive option to additional default policies while
> service creation
> --
>
> Key: RANGER-4182
> URL: https://issues.apache.org/jira/browse/RANGER-4182
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
> Fix For: 3.0.0
>
>
> Currently while service creation when we create additional default policies
> via curl we do not have option to support isRecursive. This is mostly due to
> [https://github.com/apache/ranger/blob/2d9af00153e8326c7b5eb80e7c86e1e8988dfbdc/agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBaseService.java#L209,]
> where we are setting it explicitly false. We need a mechanism where in user
> should be able to dynamically enable/ disable is-isRecursive option for a
> resource using JSON provided.
>
> Sample curl command to create service & additional default policies
> {code:java}
> curl -u admin: -ivk -H "Accept:application/json" -H
> "Content-Type:application/json" -X POST
> 'http://localhost:6080/service/plugins/services' -d @hive_test.json {code}
> {code:java}
> vim hive_test.json
> { "isEnabled": "true", "type": "hive", "configs": { "username":
> "hive", "password": "hive", "cluster.name": "My Dummy Cluster",
> "jdbc.driverClassName": "org.apache.hive.jdbc.HiveDriver", "jdbc.url":
> "none", "enable.hive.metastore.lookup": "true",
> "hive.site.file.path": "/etc/hive/conf/hive-site.xml",
> "policy.download.auth.users": "hive,hdfs,impala",
> "tag.download.auth.users": "hive,hdfs,impala",
> "policy.grantrevoke.auth.users": "hive,impala",
> "setup.additional.default.policies": "true", "default-policy.1.name":
> "User URL Policy", "default-policy.1.resource.url": "/test/kishor",
> "default-policy.1.policyItem.1.users": "kishor",
> "default-policy.1.policyItem.1.accessTypes": "read,write",
> "default-policy.1.resource-flag.is-recursive": "true",
> "default.policy.users": "impala,hive,hue,beacon,admin,dpprofiler" },
> "name": "hive_test", "displayName": "Hive service", "description": "Hive
> repository/ service for Kishor" }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3739) Add JWT filter in Ranger Admin
[
https://issues.apache.org/jira/browse/RANGER-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713473#comment-17713473
]
Kishor Gollapalliwar commented on RANGER-3739:
--
master commit:
https://github.com/apache/ranger/commit/2734df910286df939a3260ba54b0204346b73611
> Add JWT filter in Ranger Admin
> --
>
> Key: RANGER-3739
> URL: https://issues.apache.org/jira/browse/RANGER-3739
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
> Fix For: 3.0.0
>
>
> Add JWT auth filter in Ranger Admin, which authenticates browser &
> non-browser JWT requests without altering existing authentication filters.
> The existing authorization process must be alter to incorporate following
> cases
> |*Token*|*SSO Enabled*|*First Authorizer / Filter*|
> |Present|Yes|RangerSSOAuthenticationFilter|
> |Absent|Yes|RangerSSOAuthenticationFilter|
> |Present|No|RangerJwtAuthFilter ({*}NEW{*})|
> |Absent|No|RangerJwtAuthFilter ({*}NEW{*})|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3739) Add JWT filter in Ranger Admin
[
https://issues.apache.org/jira/browse/RANGER-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713473#comment-17713473
]
Kishor Gollapalliwar edited comment on RANGER-3739 at 4/18/23 8:24 AM:
---
follow-up patch master commit:
[https://github.com/apache/ranger/commit/2734df910286df939a3260ba54b0204346b73611]
was (Author: kishor.gollapalliwar):
master commit:
https://github.com/apache/ranger/commit/2734df910286df939a3260ba54b0204346b73611
> Add JWT filter in Ranger Admin
> --
>
> Key: RANGER-3739
> URL: https://issues.apache.org/jira/browse/RANGER-3739
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
> Fix For: 3.0.0
>
>
> Add JWT auth filter in Ranger Admin, which authenticates browser &
> non-browser JWT requests without altering existing authentication filters.
> The existing authorization process must be alter to incorporate following
> cases
> |*Token*|*SSO Enabled*|*First Authorizer / Filter*|
> |Present|Yes|RangerSSOAuthenticationFilter|
> |Absent|Yes|RangerSSOAuthenticationFilter|
> |Present|No|RangerJwtAuthFilter ({*}NEW{*})|
> |Absent|No|RangerJwtAuthFilter ({*}NEW{*})|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4152) Create common module for metrics and add metrics in Admin
[ https://issues.apache.org/jira/browse/RANGER-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710959#comment-17710959 ] Kishor Gollapalliwar edited comment on RANGER-4152 at 4/11/23 1:38 PM: --- master-commit: [https://github.com/apache/ranger/commit/932bc3404eb760148e4458071faba1c29baa7dcc] was (Author: kishor.gollapalliwar): commit: https://github.com/apache/ranger/commit/932bc3404eb760148e4458071faba1c29baa7dcc > Create common module for metrics and add metrics in Admin > - > > Key: RANGER-4152 > URL: https://issues.apache.org/jira/browse/RANGER-4152 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create common sub-module which will be responsible to handle/ incorporate > common metrics in project. Individual sub-modules leveraging this common > module, can have their specific metrics apart making it complete. Also add > metrics in Ranger Admin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4152) Create common module for metrics and add metrics in Admin
[ https://issues.apache.org/jira/browse/RANGER-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4152: - Fix Version/s: 3.0.0 > Create common module for metrics and add metrics in Admin > - > > Key: RANGER-4152 > URL: https://issues.apache.org/jira/browse/RANGER-4152 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create common sub-module which will be responsible to handle/ incorporate > common metrics in project. Individual sub-modules leveraging this common > module, can have their specific metrics apart making it complete. Also add > metrics in Ranger Admin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4182) Ranger Admin - Enable isRecursive option to additional default policies while service creation
Kishor Gollapalliwar created RANGER-4182:
Summary: Ranger Admin - Enable isRecursive option to additional
default policies while service creation
Key: RANGER-4182
URL: https://issues.apache.org/jira/browse/RANGER-4182
Project: Ranger
Issue Type: Improvement
Components: Ranger
Reporter: Kishor Gollapalliwar
Assignee: Kishor Gollapalliwar
Currently while service creation when we create additional default policies via
curl we do not have option to support isRecursive. This is mostly due to
[https://github.com/apache/ranger/blob/2d9af00153e8326c7b5eb80e7c86e1e8988dfbdc/agents-common/src/main/java/org/apache/ranger/plugin/service/RangerBaseService.java#L209,]
where we are setting it explicitly false. We need a mechanism where in user
should be able to dynamically enable/ disable is-isRecursive option for a
resource using JSON provided.
Sample curl command to create service & additional default policies
{code:java}
curl -u admin: -ivk -H "Accept:application/json" -H
"Content-Type:application/json" -X POST
'http://localhost:6080/service/plugins/services' -d @hive_test.json {code}
{code:java}
vim hive_test.json
{ "isEnabled": "true", "type": "hive", "configs": { "username":
"hive", "password": "hive", "cluster.name": "My Dummy Cluster",
"jdbc.driverClassName": "org.apache.hive.jdbc.HiveDriver", "jdbc.url":
"none", "enable.hive.metastore.lookup": "true", "hive.site.file.path":
"/etc/hive/conf/hive-site.xml", "policy.download.auth.users":
"hive,hdfs,impala", "tag.download.auth.users": "hive,hdfs,impala",
"policy.grantrevoke.auth.users": "hive,impala",
"setup.additional.default.policies": "true", "default-policy.1.name": "User
URL Policy", "default-policy.1.resource.url": "/test/kishor",
"default-policy.1.policyItem.1.users": "kishor",
"default-policy.1.policyItem.1.accessTypes": "read,write",
"default-policy.1.resource-flag.is-recursive": "true",
"default.policy.users": "impala,hive,hue,beacon,admin,dpprofiler" },
"name": "hive_test", "displayName": "Hive service", "description": "Hive
repository/ service for Kishor" }
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4137) Add yarn and impala users to audit filter for solr servicedef to avoid logging of audits
[ https://issues.apache.org/jira/browse/RANGER-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704207#comment-17704207 ] Kishor Gollapalliwar commented on RANGER-4137: -- master: https://github.com/apache/ranger/commit/f1a4aa22c4069d09049b4e108e00f7e4d65245dc > Add yarn and impala users to audit filter for solr servicedef to avoid > logging of audits > > > Key: RANGER-4137 > URL: https://issues.apache.org/jira/browse/RANGER-4137 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Rakesh Gupta >Assignee: Rakesh Gupta >Priority: Major > Attachments: 0001-RANGER-4137.patch, solr_auditfilter.png > > > Currently, service users other than yarn and impala are included in audit > filters to avoid logging of audits for solr access (query and update - for > audits collection). This JIRA is filed to include yarn and impala users to > the list of users -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4152) Create common module for metrics and add metrics in Admin
[ https://issues.apache.org/jira/browse/RANGER-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4152: - Summary: Create common module for metrics and add metrics in Admin (was: Create common module for handling metrics) > Create common module for metrics and add metrics in Admin > - > > Key: RANGER-4152 > URL: https://issues.apache.org/jira/browse/RANGER-4152 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create common sub-module which will be responsible to handle/ incorporate > common metrics in project. Individual sub-modules leveraging this common > module, can have their specific metrics apart making it complete. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4152) Create common module for metrics and add metrics in Admin
[ https://issues.apache.org/jira/browse/RANGER-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-4152: - Description: Create common sub-module which will be responsible to handle/ incorporate common metrics in project. Individual sub-modules leveraging this common module, can have their specific metrics apart making it complete. Also add metrics in Ranger Admin. (was: Create common sub-module which will be responsible to handle/ incorporate common metrics in project. Individual sub-modules leveraging this common module, can have their specific metrics apart making it complete. ) > Create common module for metrics and add metrics in Admin > - > > Key: RANGER-4152 > URL: https://issues.apache.org/jira/browse/RANGER-4152 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create common sub-module which will be responsible to handle/ incorporate > common metrics in project. Individual sub-modules leveraging this common > module, can have their specific metrics apart making it complete. Also add > metrics in Ranger Admin. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4152) Create common module for handling metrics
[ https://issues.apache.org/jira/browse/RANGER-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-4152: Assignee: Kishor Gollapalliwar > Create common module for handling metrics > - > > Key: RANGER-4152 > URL: https://issues.apache.org/jira/browse/RANGER-4152 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create common sub-module which will be responsible to handle/ incorporate > common metrics in project. Individual sub-modules leveraging this common > module, can have their specific metrics apart making it complete. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4152) Create common module for handling metrics
Kishor Gollapalliwar created RANGER-4152: Summary: Create common module for handling metrics Key: RANGER-4152 URL: https://issues.apache.org/jira/browse/RANGER-4152 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Create common sub-module which will be responsible to handle/ incorporate common metrics in project. Individual sub-modules leveraging this common module, can have their specific metrics apart making it complete. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4089) Getting browser specific pop-up message if try to delete policy after edit
[ https://issues.apache.org/jira/browse/RANGER-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696857#comment-17696857 ] Kishor Gollapalliwar commented on RANGER-4089: -- master commit : https://github.com/apache/ranger/commit/f77be0acc7b9b2f6a5dde5c9cb2fd63c36d92426 > Getting browser specific pop-up message if try to delete policy after edit > --- > > Key: RANGER-4089 > URL: https://issues.apache.org/jira/browse/RANGER-4089 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Brijesh Bhalala >Priority: Critical > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4089.patch, Screenshot 2023-02-15 at 5.44.05 > PM.png > > > Getting browser specific pop-up message if try to delete policy after edit > Steps to reproduce : > 1. Create a policy > 2. Edit policy , instead of save click on delete , user is getting browser > specic pop-up . > 3. If move to different tab Policy is deleted & user will be present on > Deleted policy edit page . > Expected : Behaviour should be like old UI , Once system specific Delete > confirmation popup should be enough. > Thanks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3739) Add JWT filter in Ranger Admin
[
https://issues.apache.org/jira/browse/RANGER-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551667#comment-17551667
]
Kishor Gollapalliwar commented on RANGER-3739:
--
RR follow-up patch: https://reviews.apache.org/r/74014/
> Add JWT filter in Ranger Admin
> --
>
> Key: RANGER-3739
> URL: https://issues.apache.org/jira/browse/RANGER-3739
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
> Fix For: 3.0.0
>
>
> Add JWT auth filter in Ranger Admin, which authenticates browser &
> non-browser JWT requests without altering existing authentication filters.
> The existing authorization process must be alter to incorporate following
> cases
> |*Token*|*SSO Enabled*|*First Authorizer / Filter*|
> |Present|Yes|RangerSSOAuthenticationFilter|
> |Absent|Yes|RangerSSOAuthenticationFilter|
> |Present|No|RangerJwtAuthFilter ({*}NEW{*})|
> |Absent|No|RangerJwtAuthFilter ({*}NEW{*})|
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (RANGER-3740) Create Ranger Admin API to refresh tag cache
[ https://issues.apache.org/jira/browse/RANGER-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551593#comment-17551593 ] Kishor Gollapalliwar commented on RANGER-3740: -- master follow-up commit: https://github.com/apache/ranger/commit/2a057768fc6a345fce013a89c72d5d67d0df666d > Create Ranger Admin API to refresh tag cache > > > Key: RANGER-3740 > URL: https://issues.apache.org/jira/browse/RANGER-3740 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create Ranger Admin API to refresh tag cache, which will help refreshing > cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3740) Create Ranger Admin API to refresh tag cache
[ https://issues.apache.org/jira/browse/RANGER-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544965#comment-17544965 ] Kishor Gollapalliwar commented on RANGER-3740: -- follow-up patch RR : https://reviews.apache.org/r/74006/ > Create Ranger Admin API to refresh tag cache > > > Key: RANGER-3740 > URL: https://issues.apache.org/jira/browse/RANGER-3740 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create Ranger Admin API to refresh tag cache, which will help refreshing > cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3724) Create Ranger Admin API to refresh policy cache
[ https://issues.apache.org/jira/browse/RANGER-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536567#comment-17536567 ] Kishor Gollapalliwar commented on RANGER-3724: -- master follow-up commit: https://github.com/apache/ranger/commit/2f776deceaccd94ec4402679acbf528af42b1c76 > Create Ranger Admin API to refresh policy cache > --- > > Key: RANGER-3724 > URL: https://issues.apache.org/jira/browse/RANGER-3724 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create Ranger Admin API to refresh policy cache, which will help refreshing > cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3740) Create Ranger Admin API to refresh tag cache
[ https://issues.apache.org/jira/browse/RANGER-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3740: - Fix Version/s: 3.0.0 > Create Ranger Admin API to refresh tag cache > > > Key: RANGER-3740 > URL: https://issues.apache.org/jira/browse/RANGER-3740 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create Ranger Admin API to refresh tag cache, which will help refreshing > cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3739) Add JWT filter in Ranger Admin
[
https://issues.apache.org/jira/browse/RANGER-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-3739:
-
Fix Version/s: 3.0.0
> Add JWT filter in Ranger Admin
> --
>
> Key: RANGER-3739
> URL: https://issues.apache.org/jira/browse/RANGER-3739
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
> Fix For: 3.0.0
>
>
> Add JWT auth filter in Ranger Admin, which authenticates browser &
> non-browser JWT requests without altering existing authentication filters.
> The existing authorization process must be alter to incorporate following
> cases
> |*Token*|*SSO Enabled*|*First Authorizer / Filter*|
> |Present|Yes|RangerSSOAuthenticationFilter|
> |Absent|Yes|RangerSSOAuthenticationFilter|
> |Present|No|RangerJwtAuthFilter ({*}NEW{*})|
> |Absent|No|RangerJwtAuthFilter ({*}NEW{*})|
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (RANGER-3740) Create Ranger Admin API to refresh tag cache
Kishor Gollapalliwar created RANGER-3740: Summary: Create Ranger Admin API to refresh tag cache Key: RANGER-3740 URL: https://issues.apache.org/jira/browse/RANGER-3740 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Create Ranger Admin API to refresh tag cache, which will help refreshing cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (RANGER-3739) Add JWT filter in Ranger Admin
Kishor Gollapalliwar created RANGER-3739:
Summary: Add JWT filter in Ranger Admin
Key: RANGER-3739
URL: https://issues.apache.org/jira/browse/RANGER-3739
Project: Ranger
Issue Type: Improvement
Components: Ranger
Reporter: Kishor Gollapalliwar
Assignee: Kishor Gollapalliwar
Add JWT auth filter in Ranger Admin, which authenticates browser & non-browser
JWT requests without altering existing authentication filters.
The existing authorization process must be alter to incorporate following cases
|*Token*|*SSO Enabled*|*First Authorizer / Filter*|
|Present|Yes|RangerSSOAuthenticationFilter|
|Absent|Yes|RangerSSOAuthenticationFilter|
|Present|No|RangerJwtAuthFilter ({*}NEW{*})|
|Absent|No|RangerJwtAuthFilter ({*}NEW{*})|
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (RANGER-3727) Create common module for handling authentication
Kishor Gollapalliwar created RANGER-3727: Summary: Create common module for handling authentication Key: RANGER-3727 URL: https://issues.apache.org/jira/browse/RANGER-3727 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Create common sub-module which will be responsible to handle authentication in project -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (RANGER-3724) Create Ranger Admin API to refresh policy cache
[ https://issues.apache.org/jira/browse/RANGER-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3724: - Description: Create Ranger Admin API to refresh policy cache, which will help refreshing cache externally. (was: Create Ranger Admin API to refresh policy cache) > Create Ranger Admin API to refresh policy cache > --- > > Key: RANGER-3724 > URL: https://issues.apache.org/jira/browse/RANGER-3724 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create Ranger Admin API to refresh policy cache, which will help refreshing > cache externally. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (RANGER-3724) Create Ranger Admin API to refresh policy cache
[ https://issues.apache.org/jira/browse/RANGER-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-3724: Assignee: Kishor Gollapalliwar > Create Ranger Admin API to refresh policy cache > --- > > Key: RANGER-3724 > URL: https://issues.apache.org/jira/browse/RANGER-3724 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create Ranger Admin API to refresh policy cache -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (RANGER-3724) Create Ranger Admin API to refresh policy cache
Kishor Gollapalliwar created RANGER-3724: Summary: Create Ranger Admin API to refresh policy cache Key: RANGER-3724 URL: https://issues.apache.org/jira/browse/RANGER-3724 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Create Ranger Admin API to refresh policy cache -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (RANGER-3675) Upgrade tomcat due to intermittent READ TIMEOUT
[ https://issues.apache.org/jira/browse/RANGER-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509917#comment-17509917 ] Kishor Gollapalliwar commented on RANGER-3675: -- RR: https://reviews.apache.org/r/73905/ > Upgrade tomcat due to intermittent READ TIMEOUT > --- > > Key: RANGER-3675 > URL: https://issues.apache.org/jira/browse/RANGER-3675 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > There are intermittent READ-TIMEOUTs observed in tomcat 8.5.75 upgrade it to > 8.5.76 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3675) Upgrade tomcat due to intermittent READ TIMEOUT
Kishor Gollapalliwar created RANGER-3675: Summary: Upgrade tomcat due to intermittent READ TIMEOUT Key: RANGER-3675 URL: https://issues.apache.org/jira/browse/RANGER-3675 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar There are intermittent READ-TIMEOUTs observed in tomcat 8.5.75 upgrade it to 8.5.76 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (RANGER-3655) Add JWT capability to REST Clients
[ https://issues.apache.org/jira/browse/RANGER-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502338#comment-17502338 ] Kishor Gollapalliwar commented on RANGER-3655: -- RR : https://reviews.apache.org/r/73893/ > Add JWT capability to REST Clients > -- > > Key: RANGER-3655 > URL: https://issues.apache.org/jira/browse/RANGER-3655 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Current Ranger REST clients do not support JWT capabilities. Add JWT > capabilities to Ranger REST clients -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3655) Add JWT capability to REST Clients
Kishor Gollapalliwar created RANGER-3655: Summary: Add JWT capability to REST Clients Key: RANGER-3655 URL: https://issues.apache.org/jira/browse/RANGER-3655 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Current Ranger REST clients do not support JWT capabilities. Add JWT capabilities to Ranger REST clients -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3502) Make GET zone APIs accessible to authorized users only
[
https://issues.apache.org/jira/browse/RANGER-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-3502:
-
Description:
Currently get
[zones|https://ranger.apache.org/apidocs/resource_SecurityZoneREST.html#resource_SecurityZoneREST_getAllZones_GET]
API returns all zones even for users who are not authorized to zone modules.
Restrict this API to only users who are authorized to zone module.
Steps to reproduce:
# Create a internal user name, test_user1
# Remove the permission on Security Zone module for a user
# Login as test_user1 user to Ranger Admin, user should not be able to see
Security Zone tab
# Access the API using curl
{code:java}
curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
"Content-Type:application/json"
"https://:6182/service/zones/zones"
{code}
{code:java}
curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
"Content-Type:application/json"
"https://:6182/service/zones/zones/{ID}"
{code}
{code:java}
curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
"Content-Type:application/json"
"https://:6182/service/zones/zones/name/{ZONE_NAME}"
{code}
was:
Currently get
[zones|https://ranger.apache.org/apidocs/resource_SecurityZoneREST.html#resource_SecurityZoneREST_getAllZones_GET]
API returns all zones even for users who are not authorized to zone modules.
Restrict this API to only users who are authorized to zone module.
Steps to reproduce:
# Create a internal user name, test_user1
# Remove the permission on Security Zone module for a user
# Login as test_user1 user to Ranger Admin, user should not be able to see
Security Zone tab
# Access the API using curl
{code:java}
curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
"Content-Type:application/json"
"https://:6182/service/zones/zones"
{code}
> Make GET zone APIs accessible to authorized users only
> --
>
> Key: RANGER-3502
> URL: https://issues.apache.org/jira/browse/RANGER-3502
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
>
> Currently get
> [zones|https://ranger.apache.org/apidocs/resource_SecurityZoneREST.html#resource_SecurityZoneREST_getAllZones_GET]
> API returns all zones even for users who are not authorized to zone modules.
> Restrict this API to only users who are authorized to zone module.
> Steps to reproduce:
> # Create a internal user name, test_user1
> # Remove the permission on Security Zone module for a user
> # Login as test_user1 user to Ranger Admin, user should not be able to see
> Security Zone tab
> # Access the API using curl
> {code:java}
> curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
> "Content-Type:application/json"
> "https://:6182/service/zones/zones"
> {code}
> {code:java}
> curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
> "Content-Type:application/json"
> "https://:6182/service/zones/zones/{ID}"
> {code}
> {code:java}
> curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
> "Content-Type:application/json"
> "https://:6182/service/zones/zones/name/{ZONE_NAME}"
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3502) Make GET zone APIs accessible to authorized users only
[
https://issues.apache.org/jira/browse/RANGER-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-3502:
-
Summary: Make GET zone APIs accessible to authorized users only (was: Make
GET zones API accessible to authorized users only)
> Make GET zone APIs accessible to authorized users only
> --
>
> Key: RANGER-3502
> URL: https://issues.apache.org/jira/browse/RANGER-3502
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
>
> Currently get
> [zones|https://ranger.apache.org/apidocs/resource_SecurityZoneREST.html#resource_SecurityZoneREST_getAllZones_GET]
> API returns all zones even for users who are not authorized to zone modules.
> Restrict this API to only users who are authorized to zone module.
> Steps to reproduce:
> # Create a internal user name, test_user1
> # Remove the permission on Security Zone module for a user
> # Login as test_user1 user to Ranger Admin, user should not be able to see
> Security Zone tab
> # Access the API using curl
> {code:java}
> curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
> "Content-Type:application/json"
> "https://:6182/service/zones/zones"
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3502) Make GET zones API accessible to authorized users only
[
https://issues.apache.org/jira/browse/RANGER-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-3502:
-
Summary: Make GET zones API accessible to authorized users only (was: Make
get zones API accessible to authorized users)
> Make GET zones API accessible to authorized users only
> --
>
> Key: RANGER-3502
> URL: https://issues.apache.org/jira/browse/RANGER-3502
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
>
> Currently get
> [zones|https://ranger.apache.org/apidocs/resource_SecurityZoneREST.html#resource_SecurityZoneREST_getAllZones_GET]
> API returns all zones even for users who are not authorized to zone modules.
> Restrict this API to only users who are authorized to zone module.
> Steps to reproduce:
> # Create a internal user name, test_user1
> # Remove the permission on Security Zone module for a user
> # Login as test_user1 user to Ranger Admin, user should not be able to see
> Security Zone tab
> # Access the API using curl
> {code:java}
> curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
> "Content-Type:application/json"
> "https://:6182/service/zones/zones"
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3502) Make get zones API accessible to authorized users
Kishor Gollapalliwar created RANGER-3502:
Summary: Make get zones API accessible to authorized users
Key: RANGER-3502
URL: https://issues.apache.org/jira/browse/RANGER-3502
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Kishor Gollapalliwar
Assignee: Kishor Gollapalliwar
Currently get
[zones|https://ranger.apache.org/apidocs/resource_SecurityZoneREST.html#resource_SecurityZoneREST_getAllZones_GET]
API returns all zones even for users who are not authorized to zone modules.
Restrict this API to only users who are authorized to zone module.
Steps to reproduce:
# Create a internal user name, test_user1
# Remove the permission on Security Zone module for a user
# Login as test_user1 user to Ranger Admin, user should not be able to see
Security Zone tab
# Access the API using curl
{code:java}
curl -ikv -u test_user1:pass@123 -X GET -H "Accept:application/json" -H
"Content-Type:application/json"
"https://:6182/service/zones/zones"
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3433) Null Dereference in ServiceREST getPolicyByName method
[ https://issues.apache.org/jira/browse/RANGER-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3433: - Summary: Null Dereference in ServiceREST getPolicyByName method (was: Null Dereference in ServiceREST.java) > Null Dereference in ServiceREST getPolicyByName method > -- > > Key: RANGER-3433 > URL: https://issues.apache.org/jira/browse/RANGER-3433 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Kishor Gollapalliwar >Priority: Minor > > Null Dereference in ServiceREST.java at line 4110. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-3433) Null Dereference in ServiceREST.java
[ https://issues.apache.org/jira/browse/RANGER-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-3433: Assignee: Kishor Gollapalliwar > Null Dereference in ServiceREST.java > > > Key: RANGER-3433 > URL: https://issues.apache.org/jira/browse/RANGER-3433 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Kishor Gollapalliwar >Priority: Minor > > Null Dereference in ServiceREST.java at line 4110. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3398) Duplicate JAVA patch suffix should not be allowed
[ https://issues.apache.org/jira/browse/RANGER-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3398: - Fix Version/s: (was: 2.2.0) (was: 3.0.0) > Duplicate JAVA patch suffix should not be allowed > - > > Key: RANGER-3398 > URL: https://issues.apache.org/jira/browse/RANGER-3398 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Duplicate JAVA suffix is allowed. Currently we need a manual human > intervention to find and correct. Use case in details as follows. > Use-Case: > # Say user1 & user2 working on a fix in Ranger and they both need JAVA patch > changes. > # Assume user1 needs to update table1 and user2 needs to update table2 using > java. > # Both Checked latest JAVA patch suffix (say it is *_J10050*). And used > suffix *_J10051* for their JAVA files > If both commits ends up merging. The setup script will apply ONLY one of the > both JAVA files (suffixed *_J10051*) randomly. > Reproduce Steps: > # cd /security-admin/src/main/java/org/apache/ranger/patch/ > # Update suffix of last 2 patches such that both contains same suffix > # mvn clean compile package install -U #build ranger > # setup ranger > To avoid this, we need to fail maven build itself if there are duplicate > suffix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3398) Duplicate JAVA patch suffix should not be allowed
[ https://issues.apache.org/jira/browse/RANGER-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3398: - Description: Duplicate JAVA suffix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows. Use-Case: # Say user1 & user2 working on a fix in Ranger and they both need JAVA patch changes. # Assume user1 needs to update table1 and user2 needs to update table2 using java. # Both Checked latest JAVA patch suffix (say it is *_J10050*). And used suffix *_J10051* for their JAVA files If both commits ends up merging. The setup script will apply ONLY one of the both JAVA files (suffixed *_J10051*) randomly. Reproduce Steps: # cd /security-admin/src/main/java/org/apache/ranger/patch/ # Update suffix of last 2 patches such that both contains same suffix # mvn clean compile package install -U #build ranger # setup ranger To avoid this, we need to fail maven build itself if there are duplicate suffix. was: Duplicate SQL prefix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows. Use-Case: # Say user1 & user2 working on a fix in Ranger and they both need DB changes. # Assume user1 needs to update table1 and user2 needs to update table2. # Both Checked latest DB patch prefix (say it is *056-*). And used prefix *057-* for their SQL files If both commits ends up merging. The setup script will apply ONLY one of the both SQL files (prefixed *057-*) randomly. Reproduce Steps: # cd /security-admin/db/mysql/patches # Update prefix of last 2 patches such that both contains same prefix # mvn clean compile package install -U #build ranger # setup ranger To avoid this, we need to fail maven build itself if there are duplicate prefix. > Duplicate JAVA patch suffix should not be allowed > - > > Key: RANGER-3398 > URL: https://issues.apache.org/jira/browse/RANGER-3398 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Duplicate JAVA suffix is allowed. Currently we need a manual human > intervention to find and correct. Use case in details as follows. > Use-Case: > # Say user1 & user2 working on a fix in Ranger and they both need JAVA patch > changes. > # Assume user1 needs to update table1 and user2 needs to update table2 using > java. > # Both Checked latest JAVA patch suffix (say it is *_J10050*). And used > suffix *_J10051* for their JAVA files > If both commits ends up merging. The setup script will apply ONLY one of the > both JAVA files (suffixed *_J10051*) randomly. > Reproduce Steps: > # cd /security-admin/src/main/java/org/apache/ranger/patch/ > # Update suffix of last 2 patches such that both contains same suffix > # mvn clean compile package install -U #build ranger > # setup ranger > To avoid this, we need to fail maven build itself if there are duplicate > suffix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3398) Duplicate JAVA patch suffix should not be allowed
Kishor Gollapalliwar created RANGER-3398: Summary: Duplicate JAVA patch suffix should not be allowed Key: RANGER-3398 URL: https://issues.apache.org/jira/browse/RANGER-3398 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Fix For: 3.0.0, 2.2.0 Duplicate SQL prefix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows. Use-Case: # Say user1 & user2 working on a fix in Ranger and they both need DB changes. # Assume user1 needs to update table1 and user2 needs to update table2. # Both Checked latest DB patch prefix (say it is *056-*). And used prefix *057-* for their SQL files If both commits ends up merging. The setup script will apply ONLY one of the both SQL files (prefixed *057-*) randomly. Reproduce Steps: # cd /security-admin/db/mysql/patches # Update prefix of last 2 patches such that both contains same prefix # mvn clean compile package install -U #build ranger # setup ranger To avoid this, we need to fail maven build itself if there are duplicate prefix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3385) Duplicate SQL prefix should not be allowed
[ https://issues.apache.org/jira/browse/RANGER-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3385: - Description: Duplicate SQL prefix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows. Use-Case: # Say user1 & user2 working on a fix in Ranger and they both need DB changes. # Assume user1 needs to update table1 and user2 needs to update table2. # Both Checked latest DB patch prefix (say it is *056-*). And used prefix *057-* for their SQL files If both commits ends up merging. The setup script will apply ONLY one of the both SQL files (prefixed *057-*) randomly. Reproduce Steps: # cd /security-admin/db/mysql/patches # Update prefix of last 2 patches such that both contains same prefix # mvn clean compile package install -U #build ranger # setup ranger To avoid this, we need to fail maven build itself if there are duplicate prefix. was: Duplicate SQL prefix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows. Use-Case: # Say user1 & user2 working on a fix in Ranger and they both need DB changes. # Assume user1 needs to update table1 and user2 needs to update table2. # Both Checked latest DB patch prefix (say it is *056-*). And used prefix *057-* for their SQL files If case is not taken and both commits ends up merging. The setup script will apply ONLY one of the both SQL files (prefixed *057-*) randomly. Reproduce Steps: # cd /security-admin/db/mysql/patches # Update prefix of last 2 patches such that both contains same prefix # mvn clean compile package install -U #build ranger # setup ranger To avoid this, we need to fail maven build itself if there are duplicate prefix. > Duplicate SQL prefix should not be allowed > -- > > Key: RANGER-3385 > URL: https://issues.apache.org/jira/browse/RANGER-3385 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Duplicate SQL prefix is allowed. Currently we need a manual human > intervention to find and correct. Use case in details as follows. > Use-Case: > # Say user1 & user2 working on a fix in Ranger and they both need DB changes. > # Assume user1 needs to update table1 and user2 needs to update table2. > # Both Checked latest DB patch prefix (say it is *056-*). And used prefix > *057-* for their SQL files > If both commits ends up merging. The setup script will apply ONLY one of the > both SQL files (prefixed *057-*) randomly. > Reproduce Steps: > # cd /security-admin/db/mysql/patches > # Update prefix of last 2 patches such that both contains same prefix > # mvn clean compile package install -U #build ranger > # setup ranger > To avoid this, we need to fail maven build itself if there are duplicate > prefix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3385) Duplicate SQL prefix should not be allowed
Kishor Gollapalliwar created RANGER-3385: Summary: Duplicate SQL prefix should not be allowed Key: RANGER-3385 URL: https://issues.apache.org/jira/browse/RANGER-3385 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Duplicate SQL prefix is allowed. Currently we need a manual human intervention to find and correct. Use case in details as follows. Use-Case: # Say user1 & user2 working on a fix in Ranger and they both need DB changes. # Assume user1 needs to update table1 and user2 needs to update table2. # Both Checked latest DB patch prefix (say it is *056-*). And used prefix *057-* for their SQL files If case is not taken and both commits ends up merging. The setup script will apply ONLY one of the both SQL files (prefixed *057-*) randomly. Reproduce Steps: # cd /security-admin/db/mysql/patches # Update prefix of last 2 patches such that both contains same prefix # mvn clean compile package install -U #build ranger # setup ranger To avoid this, we need to fail maven build itself if there are duplicate prefix. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3384) Metric Get API add input validation
[
https://issues.apache.org/jira/browse/RANGER-3384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishor Gollapalliwar updated RANGER-3384:
-
Description:
Add input validation to metric GET api. Currently this API is not doing any
sort of input validation. The input is passed as is to service layer.
*Class*=ServiceREST
*API*=/plugins/metrics/type/{type}
was:Add input validation to metric GET api
> Metric Get API add input validation
> ---
>
> Key: RANGER-3384
> URL: https://issues.apache.org/jira/browse/RANGER-3384
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Kishor Gollapalliwar
>Assignee: Kishor Gollapalliwar
>Priority: Major
>
> Add input validation to metric GET api. Currently this API is not doing any
> sort of input validation. The input is passed as is to service layer.
> *Class*=ServiceREST
> *API*=/plugins/metrics/type/{type}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3384) Metric Get API add input validation
Kishor Gollapalliwar created RANGER-3384: Summary: Metric Get API add input validation Key: RANGER-3384 URL: https://issues.apache.org/jira/browse/RANGER-3384 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Add input validation to metric GET api -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3348) Add user & group delete functionality in Apache Ranger Python APIs
[ https://issues.apache.org/jira/browse/RANGER-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17403220#comment-17403220 ] Kishor Gollapalliwar commented on RANGER-3348: -- Created follow-up RR: https://reviews.apache.org/r/73539/ > Add user & group delete functionality in Apache Ranger Python APIs > -- > > Key: RANGER-3348 > URL: https://issues.apache.org/jira/browse/RANGER-3348 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create class named *RangerClientPrivate* in > [ranger_client.py|https://github.com/apache/ranger/blob/master/intg/src/main/python/apache_ranger/client/ranger_client.py], > which will contains delete user/group defs with implementation using > non-public user/ group delete Ranger Admin APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3366) Cluster type is missed in copy constructor of RangerAccessRequestImpl
[ https://issues.apache.org/jira/browse/RANGER-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399643#comment-17399643 ] Kishor Gollapalliwar commented on RANGER-3366: -- ranger-2.2 commit: https://github.com/apache/ranger/commit/10f51810b37062b3a2dc7c90e92dd6a25b8d88d1 > Cluster type is missed in copy constructor of RangerAccessRequestImpl > - > > Key: RANGER-3366 > URL: https://issues.apache.org/jira/browse/RANGER-3366 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Copy constructor of RangerAccessRequestImpl is not setting cluster-type. > https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerAccessRequestImpl.java#L81 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3366) Cluster type is missed in copy constructor of RangerAccessRequestImpl
[ https://issues.apache.org/jira/browse/RANGER-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3366: - Fix Version/s: 2.2.0 > Cluster type is missed in copy constructor of RangerAccessRequestImpl > - > > Key: RANGER-3366 > URL: https://issues.apache.org/jira/browse/RANGER-3366 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Copy constructor of RangerAccessRequestImpl is not setting cluster-type. > https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerAccessRequestImpl.java#L81 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3366) Cluster type is missed in copy constructor of RangerAccessRequestImpl
[ https://issues.apache.org/jira/browse/RANGER-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396738#comment-17396738 ] Kishor Gollapalliwar commented on RANGER-3366: -- Review: https://reviews.apache.org/r/73512/ > Cluster type is missed in copy constructor of RangerAccessRequestImpl > - > > Key: RANGER-3366 > URL: https://issues.apache.org/jira/browse/RANGER-3366 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Copy constructor of RangerAccessRequestImpl is not setting cluster-type. > https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerAccessRequestImpl.java#L81 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3329) Request for _any access-type is denied only when on all access-types are denied
[ https://issues.apache.org/jira/browse/RANGER-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17396692#comment-17396692 ] Kishor Gollapalliwar commented on RANGER-3329: -- master commit: https://github.com/apache/ranger/commit/91545f7ce2772887465a4d28fb373494ea418d3a 2.2 commit: https://github.com/apache/ranger/commit/df73558c0f7000a942b08e6e2fee056b16c8846f > Request for _any access-type is denied only when on all access-types are > denied > --- > > Key: RANGER-3329 > URL: https://issues.apache.org/jira/browse/RANGER-3329 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Abhay Kulkarni >Priority: Major > > Currently a request for _any access-type is denied only if all access-types > in the service-def are denied by policies. Instead of this, the policy-engine > should deny _any access if there are no allowed accesses, and at least one of > the access-type is denied. This will help address following usecase: > - when accessTypeRestrictions is defined on a resource i.e. only a subset of > access-types are shown in policy-UI, it will not be possible to create > policies that deny all accesses. In such cases, the proposed change will > enable denying _any access-type with only subset of access-types denied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3366) Cluster type is missed in copy constructor of RangerAccessRequestImpl
Kishor Gollapalliwar created RANGER-3366: Summary: Cluster type is missed in copy constructor of RangerAccessRequestImpl Key: RANGER-3366 URL: https://issues.apache.org/jira/browse/RANGER-3366 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Copy constructor of RangerAccessRequestImpl is not setting cluster-type. https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerAccessRequestImpl.java#L81 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3347) Add default policy for hbase user in hdfs services
[ https://issues.apache.org/jira/browse/RANGER-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391342#comment-17391342 ] Kishor Gollapalliwar commented on RANGER-3347: -- Commit Ids: * master: https://github.com/apache/ranger/commit/16c5145ebfdd92345b6f90d4e2fb3c7c88f87413 * 2.2 : https://github.com/apache/ranger/commit/77163ee10568a15621ca1efd2291741f1f9e9dc2 > Add default policy for hbase user in hdfs services > -- > > Key: RANGER-3347 > URL: https://issues.apache.org/jira/browse/RANGER-3347 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Add default policy for hbase user in hdfs services as follows. > *Details:* > * User = hbase > * Permissions = read + write + execute > * path = /hbase/archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3347) Add default policy for hbase user in hdfs services
[ https://issues.apache.org/jira/browse/RANGER-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3347: - Fix Version/s: 2.2.0 3.0.0 > Add default policy for hbase user in hdfs services > -- > > Key: RANGER-3347 > URL: https://issues.apache.org/jira/browse/RANGER-3347 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Add default policy for hbase user in hdfs services as follows. > *Details:* > * User = hbase > * Permissions = read + write + execute > * path = /hbase/archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3347) Add default policy for hbase user in hdfs services
[ https://issues.apache.org/jira/browse/RANGER-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391339#comment-17391339 ] Kishor Gollapalliwar commented on RANGER-3347: -- Patch is available at the review board: https://reviews.apache.org/r/73482/ > Add default policy for hbase user in hdfs services > -- > > Key: RANGER-3347 > URL: https://issues.apache.org/jira/browse/RANGER-3347 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Add default policy for hbase user in hdfs services as follows. > *Details:* > * User = hbase > * Permissions = read + write + execute > * path = /hbase/archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3329) Request for _any access-type is denied only when on all access-types are denied
[ https://issues.apache.org/jira/browse/RANGER-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17391331#comment-17391331 ] Kishor Gollapalliwar commented on RANGER-3329: -- [~abhayk]/ [~madhan] Created follow-up / addendum patch. Patch is available at the review board: https://reviews.apache.org/r/73495/ > Request for _any access-type is denied only when on all access-types are > denied > --- > > Key: RANGER-3329 > URL: https://issues.apache.org/jira/browse/RANGER-3329 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Abhay Kulkarni >Priority: Major > > Currently a request for _any access-type is denied only if all access-types > in the service-def are denied by policies. Instead of this, the policy-engine > should deny _any access if there are no allowed accesses, and at least one of > the access-type is denied. This will help address following usecase: > - when accessTypeRestrictions is defined on a resource i.e. only a subset of > access-types are shown in policy-UI, it will not be possible to create > policies that deny all accesses. In such cases, the proposed change will > enable denying _any access-type with only subset of access-types denied. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3348) Add user & group delete functionality in Apache Ranger Python APIs
[ https://issues.apache.org/jira/browse/RANGER-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17387441#comment-17387441 ] Kishor Gollapalliwar commented on RANGER-3348: -- [~mad...@apache.org] Created this task to track Ranger Python client API changes. > Add user & group delete functionality in Apache Ranger Python APIs > -- > > Key: RANGER-3348 > URL: https://issues.apache.org/jira/browse/RANGER-3348 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create class named *RangerClientPrivate* in > [ranger_client.py|https://github.com/apache/ranger/blob/master/intg/src/main/python/apache_ranger/client/ranger_client.py], > which will contains delete user/group defs with implementation using > non-public user/ group delete Ranger Admin APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3348) Add user & group delete functionality in Apache Ranger Python APIs
Kishor Gollapalliwar created RANGER-3348: Summary: Add user & group delete functionality in Apache Ranger Python APIs Key: RANGER-3348 URL: https://issues.apache.org/jira/browse/RANGER-3348 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Create class named *RangerClientPrivate* in [ranger_client.py|https://github.com/apache/ranger/blob/master/intg/src/main/python/apache_ranger/client/ranger_client.py], which will contains delete user/group defs with implementation using non-public user/ group delete Ranger Admin APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-3348) Add user & group delete functionality in Apache Ranger Python APIs
[ https://issues.apache.org/jira/browse/RANGER-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-3348: Assignee: Kishor Gollapalliwar > Add user & group delete functionality in Apache Ranger Python APIs > -- > > Key: RANGER-3348 > URL: https://issues.apache.org/jira/browse/RANGER-3348 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create class named *RangerClientPrivate* in > [ranger_client.py|https://github.com/apache/ranger/blob/master/intg/src/main/python/apache_ranger/client/ranger_client.py], > which will contains delete user/group defs with implementation using > non-public user/ group delete Ranger Admin APIs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3347) Add default policy for hbase user in hdfs services
Kishor Gollapalliwar created RANGER-3347: Summary: Add default policy for hbase user in hdfs services Key: RANGER-3347 URL: https://issues.apache.org/jira/browse/RANGER-3347 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Add default policy for hbase user in hdfs services as follows. *Details:* * User = hbase * Permissions = read + write + execute * path = /hbase/archive -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3308) Create python script to test stability of policy CRUD
[ https://issues.apache.org/jira/browse/RANGER-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3308: - Description: Create a python script which will create & delete policies multiple times based on input. This script will be more helpful testing stability of Ranger Admin policy creation framework. The bash script will execute python script concurrently (default=5), each execution will run for few cycles(default=10), each cycle will create/get, update/get, delete/get policy items for given ranger service.(was: Create a python script which will create & delete policies multiple times based on input) > Create python script to test stability of policy CRUD > - > > Key: RANGER-3308 > URL: https://issues.apache.org/jira/browse/RANGER-3308 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create a python script which will create & delete policies multiple times > based on input. This script will be more helpful testing stability of Ranger > Admin policy creation framework. The bash script will execute python script > concurrently (default=5), each execution will run for few cycles(default=10), > each cycle will create/get, update/get, delete/get policy items for given > ranger service. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3308) Create python script to test stability of policy CRUD
[ https://issues.apache.org/jira/browse/RANGER-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385599#comment-17385599 ] Kishor Gollapalliwar commented on RANGER-3308: -- RR: https://reviews.apache.org/r/73472/ > Create python script to test stability of policy CRUD > - > > Key: RANGER-3308 > URL: https://issues.apache.org/jira/browse/RANGER-3308 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create a python script which will create & delete policies multiple times > based on input -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3308) Create python script to test stability of policy CRUD
[ https://issues.apache.org/jira/browse/RANGER-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3308: - Summary: Create python script to test stability of policy CRUD (was: Create python script to create, delete policies multiple times) > Create python script to test stability of policy CRUD > - > > Key: RANGER-3308 > URL: https://issues.apache.org/jira/browse/RANGER-3308 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create a python script which will create & delete policies multiple times > based on input -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3308) Create python script to create, delete policies multiple times
Kishor Gollapalliwar created RANGER-3308: Summary: Create python script to create, delete policies multiple times Key: RANGER-3308 URL: https://issues.apache.org/jira/browse/RANGER-3308 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Create a python script which will create & delete policies multiple times based on input -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3305) Service version update improvements
Kishor Gollapalliwar created RANGER-3305: Summary: Service version update improvements Key: RANGER-3305 URL: https://issues.apache.org/jira/browse/RANGER-3305 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar If multiple concurrent thread tried to update x_service_version_info, sometimes some updates lost due to lost [update phenomena/ anomaly|https://vladmihalcea.com/a-beginners-guide-to-database-locking-and-the-lost-update-phenomena/]. Add preventive measure in x_service_version_info updates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3251) [Ranger Audit Filters UI] Tag, KMS service not showing the audit filters in UI section
[ https://issues.apache.org/jira/browse/RANGER-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3251: - Fix Version/s: 3.0.0 > [Ranger Audit Filters UI] Tag, KMS service not showing the audit filters in > UI section > -- > > Key: RANGER-3251 > URL: https://issues.apache.org/jira/browse/RANGER-3251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.2.0, 2.1.1 >Reporter: Abhishek Shukla >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > Attachments: kms service audit filters.png, tag service audit > filters.png > > > Observed that for Tag and KMS service, while clicking on view service button, > we are not displaying the audit filters in UI section, instead, we are > displaying it as configs. [While the same works for other services like hdfs, > hive, etc] > > Attached screenshots. > cc [~nitin.galave] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3283) Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry
[ https://issues.apache.org/jira/browse/RANGER-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3283: - Fix Version/s: 3.0.0 > Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, > nifi-registry & schema-registry > - > > Key: RANGER-3283 > URL: https://issues.apache.org/jira/browse/RANGER-3283 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Create basic default audit filter for following services > * yarn > * kudu > * nifi > * nifi-registry > * schema-registry -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-3283) Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry
[ https://issues.apache.org/jira/browse/RANGER-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar resolved RANGER-3283. -- Resolution: Fixed Commit ID: https://github.com/apache/ranger/commit/d992bb4173043cc5f61ce54ed898a519bf7e38d1 > Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, > nifi-registry & schema-registry > - > > Key: RANGER-3283 > URL: https://issues.apache.org/jira/browse/RANGER-3283 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create basic default audit filter for following services > * yarn > * kudu > * nifi > * nifi-registry > * schema-registry -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3283) Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry
[ https://issues.apache.org/jira/browse/RANGER-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342697#comment-17342697 ] Kishor Gollapalliwar commented on RANGER-3283: -- Apache RR: https://reviews.apache.org/r/73349/ > Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, > nifi-registry & schema-registry > - > > Key: RANGER-3283 > URL: https://issues.apache.org/jira/browse/RANGER-3283 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create basic default audit filter for following services > * yarn > * kudu > * nifi > * nifi-registry > * schema-registry -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (RANGER-3283) Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry
[ https://issues.apache.org/jira/browse/RANGER-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar updated RANGER-3283: - Comment: was deleted (was: Created RR : https://reviews.apache.org/r/73348/) > Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, > nifi-registry & schema-registry > - > > Key: RANGER-3283 > URL: https://issues.apache.org/jira/browse/RANGER-3283 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create basic default audit filter for following services > * yarn > * kudu > * nifi > * nifi-registry > * schema-registry -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3251) [Ranger Audit Filters UI] Tag, KMS service not showing the audit filters in UI section
[ https://issues.apache.org/jira/browse/RANGER-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342693#comment-17342693 ] Kishor Gollapalliwar commented on RANGER-3251: -- Created RR: https://reviews.apache.org/r/73348/ > [Ranger Audit Filters UI] Tag, KMS service not showing the audit filters in > UI section > -- > > Key: RANGER-3251 > URL: https://issues.apache.org/jira/browse/RANGER-3251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.2.0, 2.1.1 >Reporter: Abhishek Shukla >Assignee: Kishor Gollapalliwar >Priority: Major > Attachments: kms service audit filters.png, tag service audit > filters.png > > > Observed that for Tag and KMS service, while clicking on view service button, > we are not displaying the audit filters in UI section, instead, we are > displaying it as configs. [While the same works for other services like hdfs, > hive, etc] > > Attached screenshots. > cc [~nitin.galave] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3283) Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry
[ https://issues.apache.org/jira/browse/RANGER-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342690#comment-17342690 ] Kishor Gollapalliwar commented on RANGER-3283: -- Created RR : https://reviews.apache.org/r/73348/ > Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, > nifi-registry & schema-registry > - > > Key: RANGER-3283 > URL: https://issues.apache.org/jira/browse/RANGER-3283 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0 >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > > Create basic default audit filter for following services > * yarn > * kudu > * nifi > * nifi-registry > * schema-registry -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3283) Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry
Kishor Gollapalliwar created RANGER-3283: Summary: Ranger Audit Filter: Basic Default Audit Filter for yarn, kudu, nifi, nifi-registry & schema-registry Key: RANGER-3283 URL: https://issues.apache.org/jira/browse/RANGER-3283 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 2.2.0 Reporter: Kishor Gollapalliwar Assignee: Kishor Gollapalliwar Create basic default audit filter for following services * yarn * kudu * nifi * nifi-registry * schema-registry -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-3251) [Ranger Audit Filters UI] Tag, KMS service not showing the audit filters in UI section
[ https://issues.apache.org/jira/browse/RANGER-3251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishor Gollapalliwar reassigned RANGER-3251: Assignee: Kishor Gollapalliwar > [Ranger Audit Filters UI] Tag, KMS service not showing the audit filters in > UI section > -- > > Key: RANGER-3251 > URL: https://issues.apache.org/jira/browse/RANGER-3251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.2.0, 2.1.1 >Reporter: Abhishek Shukla >Assignee: Kishor Gollapalliwar >Priority: Major > Attachments: kms service audit filters.png, tag service audit > filters.png > > > Observed that for Tag and KMS service, while clicking on view service button, > we are not displaying the audit filters in UI section, instead, we are > displaying it as configs. [While the same works for other services like hdfs, > hive, etc] > > Attached screenshots. > cc [~nitin.galave] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-3194) Ranger Access Audits page not loading
[ https://issues.apache.org/jira/browse/RANGER-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297096#comment-17297096 ] Kishor Gollapalliwar commented on RANGER-3194: -- Commit ID : https://github.com/apache/ranger/commit/6c5336da05ba64cd993005077034c872b73416a3 > Ranger Access Audits page not loading > - > > Key: RANGER-3194 > URL: https://issues.apache.org/jira/browse/RANGER-3194 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kishor Gollapalliwar >Assignee: Kishor Gollapalliwar >Priority: Major > Fix For: 3.0.0 > > > Ranger Access Audits page stop loading after few days. The jstack trace > suggest threads keep getting blocked on solr client which trying to fetch > records from solr collection. -- This message was sent by Atlassian Jira (v8.3.4#803005)
