[jira] [Commented] (RANGER-4753) Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33
[ https://issues.apache.org/jira/browse/RANGER-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832560#comment-17832560 ] Pradeep Agrawal commented on RANGER-4753: - Commit link : https://github.com/apache/ranger/commit/b209e61528b3d01d463e43c0b0bff02657939b11 > Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 > > > Key: RANGER-4753 > URL: https://issues.apache.org/jira/browse/RANGER-4753 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4753-Upgrade-Spring-Security-to-5.7.12-and-sp.patch > > > Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4753) Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33
[ https://issues.apache.org/jira/browse/RANGER-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4753: Attachment: 0001-RANGER-4753-Upgrade-Spring-Security-to-5.7.12-and-sp.patch > Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 > > > Key: RANGER-4753 > URL: https://issues.apache.org/jira/browse/RANGER-4753 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4753-Upgrade-Spring-Security-to-5.7.12-and-sp.patch > > > Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4753) Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33
Pradeep Agrawal created RANGER-4753: --- Summary: Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 Key: RANGER-4753 URL: https://issues.apache.org/jira/browse/RANGER-4753 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal Fix For: 3.0.0 Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4753) Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33
[ https://issues.apache.org/jira/browse/RANGER-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4753: Description: Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 (was: Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32) > Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 > > > Key: RANGER-4753 > URL: https://issues.apache.org/jira/browse/RANGER-4753 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > > Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4568: Fix Version/s: 3.0.0 > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4568-Upgrade-Spring-Security-to-5.7.11-and-sp.patch, > 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823073#comment-17823073 ] Pradeep Agrawal edited comment on RANGER-4568 at 3/4/24 8:24 AM: - commit link : https://github.com/apache/ranger/commit/c45a1c0a60b58a898f5b3387d11f5bc25e1f154e was (Author: pradeep.agrawal): commit link : https://github.com/apache/ranger/commits/master/ > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0001-RANGER-4568-Upgrade-Spring-Security-to-5.7.11-and-sp.patch, > 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17823073#comment-17823073 ] Pradeep Agrawal commented on RANGER-4568: - commit link : https://github.com/apache/ranger/commits/master/ > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0001-RANGER-4568-Upgrade-Spring-Security-to-5.7.11-and-sp.patch, > 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4476) trino filter
[
https://issues.apache.org/jira/browse/RANGER-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821933#comment-17821933
]
Pradeep Agrawal commented on RANGER-4476:
-
[~bpatel] / [~andreypilipyuk]
I am unable to build ranger with Open JDK-17.
Is there any way or specific JDKs which can be used for Building ranger on
JDK-17.
If we change (as done [here|https://github.com/apache/ranger/pull/291/files])
{code:java}
jdk.nashorn.api.scripting {code}
to
{code:java}
org.openjdk.nashorn.api.scripting {code}
Then build might work in openjdk-17 but it will fail in jdk8
> trino filter
>
>
> Key: RANGER-4476
> URL: https://issues.apache.org/jira/browse/RANGER-4476
> Project: Ranger
> Issue Type: Bug
> Components: plugins, Ranger
>Affects Versions: 3.0.0
>Reporter: Andrey Pilipyuk
>Priority: Major
> Labels: Trino
>
> hello there
> i trying to enable trino plugin, i have successful connect check
> but when i try to make policy i have an error in logs
> 2023-10-16 13:39:09,055 [https-jsse-nio-6182-exec-6] WARN
> [ServiceMgr.java:476] getFilesInDirectory('ranger-plugins/trino'): adding
> /opt/ranger-admin-3.0.0/ews/webapp/WEB-INF/classes/ranger-plugins/trino/trino-jdbc-423.jar
> 2023-10-16 13:39:09,055 [https-jsse-nio-6182-exec-6] WARN
> [ServiceMgr.java:476] getFilesInDirectory('ranger-plugins/trino'): adding
> /opt/ranger-admin-3.0.0/ews/webapp/WEB-INF/classes/ranger-plugins/trino/ranger-trino-plugin-3.0.0-SNAPSHOT.jar
> 2023-10-16 13:39:09,056 [https-jsse-nio-6182-exec-6] WARN
> [ServiceMgr.java:476] getFilesInDirectory('ranger-plugins/trino'): adding
> /opt/ranger-admin-3.0.0/ews/webapp/WEB-INF/classes/ranger-plugins/trino/trino-spi-423.jar
> 2023-10-16 13:39:09,078 [timed-executor-pool-0] WARN
> [SecureClientLogin.java:123] Can't find keyTab Path : null
> 2023-10-16 13:39:09,079 [timed-executor-pool-0] WARN
> [SecureClientLogin.java:127] Can't find principal : null
> 2023-10-16 13:39:09,084 [timed-executor-pool-0] INFO [BaseClient.java:126]
> Init Login: security not enabled, using username
> 2023-10-16 13:39:09,501 [timed-executor-pool-0] ERROR
> [TrinoResourceManager.java:168] Could not initiate a TrinoClient timedTask
> can you please tell me how i can debug it, or some prefirences to trino from
> ranger
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4568: Attachment: 0001-RANGER-4568-Upgrade-Spring-Security-to-5.7.11-and-sp.patch > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0001-RANGER-4568-Upgrade-Spring-Security-to-5.7.11-and-sp.patch, > 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821501#comment-17821501 ] Pradeep Agrawal commented on RANGER-4568: - [~bpatel] : I am stealing your this ticket rather creating a new one. > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4568: Description: Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 (was: Upgrade spring version to 5.3.31) > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4568) Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4568: Summary: Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 (was: Upgrade spring version to 5.3.31) > Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade spring version to 5.3.31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4568) Upgrade spring version to 5.3.31
[ https://issues.apache.org/jira/browse/RANGER-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal reassigned RANGER-4568: --- Assignee: Pradeep Agrawal (was: Bhavik Patel) > Upgrade spring version to 5.3.31 > > > Key: RANGER-4568 > URL: https://issues.apache.org/jira/browse/RANGER-4568 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Pradeep Agrawal >Priority: Major > Attachments: 0001-RANGER-4568-Upgrade-spring-version-to-5.3.31.patch > > > Upgrade spring version to 5.3.31 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3365) Trino/PrestoSQL URL Validation
[ https://issues.apache.org/jira/browse/RANGER-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3365: Labels: Trino (was: ) > Trino/PrestoSQL URL Validation > -- > > Key: RANGER-3365 > URL: https://issues.apache.org/jira/browse/RANGER-3365 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger >Reporter: Adnan Hemani >Priority: Major > Labels: Trino > > The Ranger-Presto/Trino plugin doesn't have filesystem URL authorization > builtin for relevant connectors (such as Hive and Iceberg) like the > Ranger-Hive plugin does. I understand that only a few of Trino's connectors > have locations that should be validated - but is there any reason we don't > have this for the connectors that should be validating URLs? > > From my understanding, this will require changes on both the Ranger-Presto > plugin and on the Trino side, so it probably won't be an easy change - but I > think it'd be a great addition to our current feature set. > > I mainly opened this ticket to see what the folks think about this - I'm > happy to look into it and contribute if there's no objections! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3182) Prestosql is renamed to Trino
[ https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3182: Labels: Trino (was: ) > Prestosql is renamed to Trino > - > > Key: RANGER-3182 > URL: https://issues.apache.org/jira/browse/RANGER-3182 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Viacheslav Kriuchkov >Assignee: Ramesh Mani >Priority: Blocker > Labels: Trino > Fix For: 3.0.0 > > Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino-master.patch, > 0001-RANGER-3182-Rename-Prestosql-to-Trino-ranger-2.3.patch, > ranger-commons-lang3-master.patch > > Time Spent: 3h > Remaining Estimate: 0h > > All "prestosql" classes are "trino" now and Presto plugin can't integrate > with Trino because of that. It means all Presto deployments that use Ranger > are stuck on version 350 and can't upgrade further. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3759) Add default logback configuration file for trino plugin
[ https://issues.apache.org/jira/browse/RANGER-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3759: Labels: Trino (was: ) > Add default logback configuration file for trino plugin > --- > > Key: RANGER-3759 > URL: https://issues.apache.org/jira/browse/RANGER-3759 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Labels: Trino > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3759-Add-default-logback-configuration-for-tr.patch > > > We have migrated from log4j to logback for plugins but the default log level > of logback configuration is set at DEBUG to Console. This produces > unnecessarily detailed logs in the trino server log file. To solve this I > will add a trino-ranger-plugin-logback.xml file where users can tune the log > level for the trino plugin according to their needs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3800) Add unimplemented checkCanSetTableAuthorization and checkCanSetTableProperties methods in trino-plugin
[
https://issues.apache.org/jira/browse/RANGER-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3800:
Labels: Trino (was: )
> Add unimplemented checkCanSetTableAuthorization and
> checkCanSetTableProperties methods in trino-plugin
> --
>
> Key: RANGER-3800
> URL: https://issues.apache.org/jira/browse/RANGER-3800
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Aakash Nand
>Priority: Major
> Labels: Trino
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-3800-Add-unimplemented-methods-for-trino-plug.patch
>
>
> {color:#de350b}checkCanSetTableAuthorization{color} and
> {color:#de350b}checkCanSetTableProperties{color} methods are not implemented
> in trino-ranger-plugin this gives `AccessDeniedException` when executing
> queries like
>
> {{ALTER TABLE XXX SET AUTHORIZATION}}
>
>
> and
>
> {{ALTER TABLE XXX SET PROPERTIES}}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3760) Make trino plugin configurable for trino environment running in docker
[ https://issues.apache.org/jira/browse/RANGER-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3760: Labels: Trino (was: ) > Make trino plugin configurable for trino environment running in docker > -- > > Key: RANGER-3760 > URL: https://issues.apache.org/jira/browse/RANGER-3760 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.1.0 >Reporter: Aakash Nand >Priority: Major > Labels: Trino > Fix For: 3.0.0, 2.3.0 > > Attachments: > 0001-RANGER-3760-Make-trino-plugin-configurable-when-trin.patch > > > Trino uses different plugin directories for server-type installation and > docker installation. > The plugin directory needs to be configured as /usr/lib/trino/plugin/ranger > when running in docker. > > Lets make this configurable in install.properties using new property > > INSTALL_ENV=docker > > If the user configures this property then trino-ranger-plugin will configure > the plugin directory to /usr/lib/trino/plugin/ranger > > otherwise, it will assume that trino is installed using a non-docker > environment and use the default plugin directory location -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3755) Build Plugin-Trino artifacts only with JDK 11
[ https://issues.apache.org/jira/browse/RANGER-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3755: Labels: Trino (was: ) > Build Plugin-Trino artifacts only with JDK 11 > - > > Key: RANGER-3755 > URL: https://issues.apache.org/jira/browse/RANGER-3755 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.2.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Labels: Trino > Fix For: 3.0.0, 2.3.0 > > > Plugin Trino needs jdk 11 and about to compile and build. In order to avoid > build issue in Apache Ranger when including Plugin Trino, we need to enable a > profile so that default build of Apache Ranger will use JDK 1.8 and Plugin > Trino and its artifacts can be build with JDK 11 profile. > To build Plugin Trino artifacts following command can be executed. > mvn clean compile package -P ranger-trino-plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3839) Ranger Tag based policy with ability to show metadata for covered resource
[
https://issues.apache.org/jira/browse/RANGER-3839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3839:
Labels: Trino (was: )
> Ranger Tag based policy with ability to show metadata for covered resource
> --
>
> Key: RANGER-3839
> URL: https://issues.apache.org/jira/browse/RANGER-3839
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Ramesh Bhanan Byndoor
>Priority: Major
> Labels: Trino
> Fix For: 2.3.0
>
> Attachments: resourceTags.json, test_ancestor_meta.json
>
>
> Have a use case around this for Trino where user should be able to see
> allowed parents along with child table
>
> For below case from here
> [https://github.com/apache/ranger/blob/release-ranger-2.3.0/agents-common/src/test/resources/policyengine/test_policyengine_tag_hive_filebased.json#L266]
>
> Resource
>
> {code:java}
> {
> "serviceName": "cl1_hive",
> "resourceElements": {
> "database": {
> "values": ["employee"]
> },
> "table": {
> "values": ["personal"]
> },
> "column": {
> "values": ["city"]
> }
> },
> "id": 3,
> "guid": "employee.personal.city-guid"
> }
> {code}
> Policy
> {code:java}
> {
> "id": 1,
> "name": "RESTRICTED_TAG_POLICY",
> "isEnabled": true,
> "isAuditEnabled": true,
> "resources": {
> "tag": {
> "values": ["RESTRICTED"],
> "isRecursive": false
> }
> },
> "policyItems": [{
> "accesses": [{
> "type": "hive:select",
> "isAllowed": true
> }],
> "users": ["hive", "user1"],
> "groups": [],
> "delegateAdmin": false,
> "conditions": [{
> "type": "expression",
> "values": ["if ( tagAttr.get('score') < 2 ) ctx.result = true;"]
> }]
> }]
> }{code}
> The test below is working as expected
> {code:java}
> {
> "name": "ALLOW 'select city from employee.personal;' for user1 using
> RESTRICTED tag",
> "request": {
> "resource": {
> "elements": {
> "database": "employee",
> "table": "personal",
> "column": "city"
> }
> },
> "accessType": "select",
> "user": "user1",
> "userGroups": [],
> "requestData": "select city from employee.personal;' for user1"
> },
> "result": {
> "isAudited": true,
> "isAllowed": true,
> "policyId": 101
> }
> }{code}
> The expectation is how to allow? (without {color:#ff}allowing access to
> anything apart from this{color})
> {*}show databases{*};— with results *employee*
> *use employee;*
> *show tables; –* with results *personal*
>
> Please suggest possible ways to solve this/policy creation.
> =
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3859) Fix the test failure for plugin-trino
[
https://issues.apache.org/jira/browse/RANGER-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3859:
Language: Trino (was: Java)
> Fix the test failure for plugin-trino
> -
>
> Key: RANGER-3859
> URL: https://issues.apache.org/jira/browse/RANGER-3859
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0, 2.2.0, 2.3.0
> Environment: macOS 12.5
> Java11
>Reporter: Alvin Wo
>Priority: Critical
> Labels: Trino
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> I ran tests for plugin-trino and got failure like:
> {code:java}
> // code placeholder
> [ERROR]
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlTest
> Time elapsed: 0.289 s <<< ERROR!
> java.lang.ExceptionInInitializerError
> at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:72)
> at org.slf4j.impl.StaticLoggerBinder.(StaticLoggerBinder.java:45)
> at org.slf4j.LoggerFactory.bind(LoggerFactory.java:150)
> at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:124)
> at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:417)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:362)
> at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:388)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControl.(RangerSystemAccessControl.java:61)
> at
> org.apache.ranger.authorization.trino.authorizer.RangerSystemAccessControlTest.setUpBeforeClass(RangerSystemAccessControlTest.java:70)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.RunBefores.invokeMethod(RunBefores.java:33)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:377)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:284)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:248)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:167)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:456)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581)
> Caused by: java.lang.IllegalStateException: Detected both
> log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on the class path,
> preempting StackOverflowError. See also
> http://www.slf4j.org/codes.html#log4jDelegationLoop for more details.
> at org.slf4j.impl.Log4jLoggerFactory.(Log4jLoggerFactory.java:54)
> ... 28 more {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3845) trino query `CREATE TABLE ... AS ...` got access denied
[
https://issues.apache.org/jira/browse/RANGER-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3845:
Labels: Trino (was: )
> trino query `CREATE TABLE ... AS ...` got access denied
> ---
>
> Key: RANGER-3845
> URL: https://issues.apache.org/jira/browse/RANGER-3845
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.3.0
>Reporter: Yufan Ho
>Priority: Major
> Labels: Trino
>
> Got permission denied when executing a `CREATE TABLE .. AS SELECT ..`
> statement.
> But if it was split into two statements - `CREATE TABLE ..` and `INSERT INTO
> ..` - both statements will success.
> logs
> {code:java}
> trino:tmp> create table test as select 1 as a;
> Query 20220729_093308_02076_gznsx failed: Access Denied: Cannot create table
> hive.tmp.test
> trino:tmp> create table test (a int);
> CREATE TABLE
> trino:tmp> insert into test select 1;
> INSERT: 1 row
> Query 20220729_093357_02089_gznsx, FINISHED, 16 nodes
> Splits: 94 total, 94 done (100.00%)
> 0.61 [0 rows, 0B] [0 rows/s, 0B/s]
> {code}
> Environment:
> Ranger 2.3.0 admin-server
> Trino 370 with ranger-2.3.0-trino-plugin installed
> Granted all permissions to public group, including all 4 levels (catalog,
> schema, table, column)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3850) Upgrade trino plugin to JDK17
[ https://issues.apache.org/jira/browse/RANGER-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3850: Labels: Trino (was: ) > Upgrade trino plugin to JDK17 > - > > Key: RANGER-3850 > URL: https://issues.apache.org/jira/browse/RANGER-3850 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.3.0 >Reporter: Aakash Nand >Priority: Major > Labels: Trino > Fix For: 3.0.0 > > Attachments: 0001-RANGER-3850-Upgrade-trino-plugin-to-JDK17.patch > > > From version 390 onwards, trino have started using JDK17 and from trino > version 393 onwards the language level will also be updated to JDK17. > Therefore trino plugin needs to be updated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3926) Ranger Trino plugin tar package do not create after successful build
[ https://issues.apache.org/jira/browse/RANGER-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3926: Labels: Trino (was: ) > Ranger Trino plugin tar package do not create after successful build > > > Key: RANGER-3926 > URL: https://issues.apache.org/jira/browse/RANGER-3926 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.3.0 >Reporter: Hasan >Priority: Major > Labels: Trino > > after successful build of Ranger 2.3.0 Trino tar package do not created -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3893) [trino-plugin]Could not create trino service on secure admin web
[ https://issues.apache.org/jira/browse/RANGER-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3893: Labels: Trino (was: ) > [trino-plugin]Could not create trino service on secure admin web > > > Key: RANGER-3893 > URL: https://issues.apache.org/jira/browse/RANGER-3893 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.3.0 >Reporter: ericsoul >Priority: Major > Labels: Trino > > I use web compiled by jdk1.8, and trino plugin compiled by jdk11 ,when create > a trino service on admin web,I got this: > msgDesc: "trino failed to find service class > org.apache.ranger.services.trino.RangerServiceTrino. Resource lookup will not > be available. Please make sure plugin jar is in the correct place." > > It seems do not have class RangerServiceTrino which in trino-plugin module > applied for admin web. So add trino-plugin module for jdk1.8 compile. > > While compile plugin-trino module with jdk1.8 , I got can not access the > trino spi class error. That seems trino spi jar is based on jdk11 > > The code for 2.3.0 release tag now can compile by jdk11. But the admin web > can not work well. > I got this error message seem to affect: > Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence > Services - 2.5.2.v20140319-9ad6abd): > org.eclipse.persistence.exceptions.ValidationException Exception Description: > Entity class [class org.apache.ranger.entity.XXAccessAuditV4] has no primary > key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If > you have defined PK using any of these annotations then make sure that you do > not have mixed access-type (both fields and properties annotated) in your > entity class hierarchy. at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1804) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620) > at > org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:542) > at > org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:335) > at > org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234) > at > org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:333) > at > org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:208) > at > org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1154) > at > org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:908) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:583) > at > org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:401) > at > org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:292) > at > org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:103) > at > org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4763) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5232) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1427) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1417) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:829) Caused by: > javax.persistence.PersistenceException: Exception [EclipseLink-28018] > (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): > org.eclipse.persistence.exceptions.EntityManagerSetupException Exception > Description: Predeployment of PersistenceUnit [defaultPU] failed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3967) Service creation failing for Trino
[
https://issues.apache.org/jira/browse/RANGER-3967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-3967:
Labels: Trino (was: )
> Service creation failing for Trino
> --
>
> Key: RANGER-3967
> URL: https://issues.apache.org/jira/browse/RANGER-3967
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Mugdha Varadkar
>Assignee: Mahesh Hanumant Bandal
>Priority: Major
> Labels: Trino
> Attachments: Screenshot 2022-11-14 at 14-02-02 Ranger.png
>
>
> Error -
> {code:java}
> 2022-11-14 09:23:52,944 [http-nio-6080-exec-4] WARN [ServiceMgr.java:467]
> getFilesInDirectory('ranger-plugins/trino'): could not find directory in
> CLASSPATH
> 2022-11-14 09:23:52,946 [http-nio-6080-exec-4] WARN [ServiceMgr.java:399]
> ServiceMgr.getClassForServiceType(trino): failed to find service-class
> 'org.apache.ranger.services.trino.RangerServiceTrino'. Resource lookup will
> not be available
> java.lang.ClassNotFoundException:
> org.apache.ranger.services.trino.RangerServiceTrino
> at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at
> org.apache.ranger.biz.ServiceMgr.getClassForServiceType(ServiceMgr.java:388)
> at
> org.apache.ranger.biz.ServiceMgr.getRangerServiceByService(ServiceMgr.java:318)
> at
> org.apache.ranger.biz.ServiceDBStore.populateDefaultPolicies(ServiceDBStore.java:3343)
> at
> org.apache.ranger.biz.ServiceDBStore.createDefaultPolicies(ServiceDBStore.java:3276)
> at
> org.apache.ranger.biz.ServiceDBStore.createService(ServiceDBStore.java:1574)
> at
> org.apache.ranger.rest.ServiceREST.createService(ServiceREST.java:773)
> at
> org.apache.ranger.rest.ServiceREST$$FastClassBySpringCGLIB$$92dab672.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> {code}
> {code}
> 2022-11-14 09:23:52,947 [http-nio-6080-exec-4] ERROR [ServiceREST.java:777]
> createService(RangerService={id={null} guid={null} isEnabled={true}
> createdBy={null} updatedBy={null} createTime={null} updateTime={null}
> version={1} name={cm_trino} displayName={cm_trino} type={trino}
> description={} tagService={cm_tag} configs={password={***}
> ranger.plugin.audit.filters={}
> jdbc.driverClassName={io.trino.jdbc.TrinoDriver} jdbc.url={localhost}
> username={trino} } policyVersion={null} policyUpdateTime={null}
> tagVersion={1} tagUpdateTime={null} }) failed
> java.lang.Exception: trino failed to find service class
> org.apache.ranger.services.trino.RangerServiceTrino. Resource lookup will not
> be available. Please make sure plugin jar is in the correct place.
> at
> org.apache.ranger.biz.ServiceMgr.getClassForServiceType(ServiceMgr.java:401)
> at
> org.apache.ranger.biz.ServiceMgr.getRangerServiceByService(ServiceMgr.java:318)
> at
> org.apache.ranger.biz.ServiceDBStore.populateDefaultPolicies(ServiceDBStore.java:3343)
> at
> org.apache.ranger.biz.ServiceDBStore.createDefaultPolicies(ServiceDBStore.java:3276)
> at
> org.apache.ranger.biz.ServiceDBStore.createService(ServiceDBStore.java:1574)
> at
> org.apache.ranger.rest.ServiceREST.createService(ServiceREST.java:773)
> at
> org.apache.ranger.rest.ServiceREST$$FastClassBySpringCGLIB$$92dab672.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3985) Trino plugin: Check table name when creating tables
[ https://issues.apache.org/jira/browse/RANGER-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3985: Labels: Trino (was: ) > Trino plugin: Check table name when creating tables > --- > > Key: RANGER-3985 > URL: https://issues.apache.org/jira/browse/RANGER-3985 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 2.3.0 >Reporter: Jonas Hartwig >Priority: Major > Labels: Trino > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The ranger rules to create tables in Trino currently check schema level to > create. > If this is set, anyone can create any table/view. There is no way to limit > the naming of tables. > However e.g. drop, alter rights are granted on table level. So user might > create any table, but not remove them. > To allow a more strict implementation view/table creation should verify table > name as well. > In that case the previous behaviour can be created by adding a rule to allow > create on catalog/schema/*. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3983) Support getColumnMasks and getRowFilters in Trino SPI 376+
[ https://issues.apache.org/jira/browse/RANGER-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3983: Labels: Trino (was: ) > Support getColumnMasks and getRowFilters in Trino SPI 376+ > -- > > Key: RANGER-3983 > URL: https://issues.apache.org/jira/browse/RANGER-3983 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: ziyue >Priority: Major > Labels: Trino > Fix For: 3.0.0, 2.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > [https://github.com/trinodb/trino/commit/827de57a50426e804761044d24d96b8877b62b7e] > > The functions `getColumnMask` and `getRowFilter` were deprecated since trino > 376, and were removed in 401. > > So we should adapt to that change in ranger implementation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3986) Upgrade trino guice dependency to 5.1.0
[ https://issues.apache.org/jira/browse/RANGER-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3986: Labels: Trino (was: ) > Upgrade trino guice dependency to 5.1.0 > --- > > Key: RANGER-3986 > URL: https://issues.apache.org/jira/browse/RANGER-3986 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: ziyue >Priority: Major > Labels: Trino > Fix For: 3.0.0, 2.4.0 > > > The latest trino SPI 403 is running on Java 17, which guice 4.x doesn't > support. we should upgrade the guice version to make ranger-trino-plugin > possible to running on JVM 17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3988) Trino plugin should differntiate between views and tables
[ https://issues.apache.org/jira/browse/RANGER-3988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-3988: Labels: Trino (was: ) > Trino plugin should differntiate between views and tables > - > > Key: RANGER-3988 > URL: https://issues.apache.org/jira/browse/RANGER-3988 > Project: Ranger > Issue Type: Improvement > Components: plugins, Ranger >Affects Versions: 2.3.0 >Reporter: Jonas Hartwig >Priority: Major > Labels: Trino > Fix For: 3.0.0 > > > The Trino plugin only "knows" tables. Views are validated against the same > rules "as" tables. Views and tables should be treated separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4075) Add support for table functions to trino ranger plugin
[
https://issues.apache.org/jira/browse/RANGER-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4075:
Labels: Trino (was: )
> Add support for table functions to trino ranger plugin
> --
>
> Key: RANGER-4075
> URL: https://issues.apache.org/jira/browse/RANGER-4075
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Mahebub Sayyed
>Assignee: Siddhant Sontakke
>Priority: Minor
> Labels: Trino
>
> Table functions were added to trino from 388 onwards and
> {{SystemAccessControl}} methods were updated to accommodate this change
> later. Therefore, to make the table function work with the Trino-Rangerplugin
> we need to re-implement method {{checkCanExecuteFunction}} with a new
> argument{{{}FunctionKind{}}}
> Relevant links
> Trino Slack: [https://trinodb.slack.com/archives/CGB0QHWSW/p1655456620535959]
> [trinodb/trino#12544|https://github.com/trinodb/trino/pull/12544]
> [trinodb/trino#12833|https://github.com/trinodb/trino/issues/12833]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4203) Add dev-support scripts for ranger-trino plugin
[ https://issues.apache.org/jira/browse/RANGER-4203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4203: Labels: Trino (was: ) > Add dev-support scripts for ranger-trino plugin > --- > > Key: RANGER-4203 > URL: https://issues.apache.org/jira/browse/RANGER-4203 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Jai Patel >Assignee: Siddhant Sontakke >Priority: Major > Labels: Trino > > Can we add scripts for installation of trino and trino plugin in our repo > similar to how we have for hive and hive-plugin in the > dev-support/ranger-docker dir? > It will help with development and testing of trino plugin faster -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4239) Upgrade trino version
[ https://issues.apache.org/jira/browse/RANGER-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4239: Labels: Trino (was: ) > Upgrade trino version > - > > Key: RANGER-4239 > URL: https://issues.apache.org/jira/browse/RANGER-4239 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: qingbo jiao >Assignee: Siddhant Sontakke >Priority: Minor > Labels: Trino > Time Spent: 0.5h > Remaining Estimate: 0h > > The current version of trino integrated in the ranger is 377, and the latest > version of trino has reached 417. Should the version of trino be upgraded to > 4XX? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4275) Trino audit not showing access type and client IP
[ https://issues.apache.org/jira/browse/RANGER-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4275: Labels: Trino (was: ) > Trino audit not showing access type and client IP > -- > > Key: RANGER-4275 > URL: https://issues.apache.org/jira/browse/RANGER-4275 > Project: Ranger > Issue Type: Bug > Components: audit >Reporter: sneha_surjuse >Assignee: sneha_surjuse >Priority: Major > Labels: Trino > Attachments: Screenshot 2023-06-08 at 3.28.08 PM.png, Screenshot > 2023-06-08 at 3.33.40 PM.png > > > When working with Trino and reviewing the audit logs, I've noticed that the > access type and client IP address information is not displayed, while its > displayed when working with hive. > I have attached a file below to see the difference > 1st for Trino > 2nd for Hive -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4260) In trino service while creating policy add permission is rendering incorrectly.
[ https://issues.apache.org/jira/browse/RANGER-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4260: Labels: Trino (was: ) > In trino service while creating policy add permission is rendering > incorrectly. > --- > > Key: RANGER-4260 > URL: https://issues.apache.org/jira/browse/RANGER-4260 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Siddhant Sontakke >Assignee: Stalin Nadar >Priority: Major > Labels: Trino > Attachments: image-2023-05-31-14-41-35-775.png, > image-2023-05-31-14-45-34-388.png, scrnli_31_05_2023_14-39-04.webm > > > h4. In trino service while creating policy add permission is rendering > incorrectly. > Actual : - > !image-2023-05-31-14-45-34-388.png|width=669,height=304! > Expected : - > !image-2023-05-31-14-41-35-775.png|width=664,height=298! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4279) while creating table in Trino , with specific table-name permission, getting an access denied
[
https://issues.apache.org/jira/browse/RANGER-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4279:
Labels: Trino (was: )
> while creating table in Trino , with specific table-name permission, getting
> an access denied
> -
>
> Key: RANGER-4279
> URL: https://issues.apache.org/jira/browse/RANGER-4279
> Project: Ranger
> Issue Type: Bug
> Components: audit
>Reporter: sneha_surjuse
>Assignee: sneha_surjuse
>Priority: Major
> Labels: Trino
>
> While granting permissions on * (all tables) in Trino worked as expected, I'm
> currently getting an issue when attempting to create tables using specific
> table-name permissions.
> The issue is related to the resource creation process and the permission
> checks performed by the {{checkCanCreateTable}} method.
> Currently, the {{checkCanCreateTable}} method creates a resource using the
> {{createResource}} method with two parameters: {{catalogName}} and
> {{{}schemaName{}}}. This resource represents the catalog and schema but does
> not include the specific table name.
> To resolve this issue, I have provided a patch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4501) creating a service will throw NPE when using service.check.user parameter
[
https://issues.apache.org/jira/browse/RANGER-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4501:
Labels: Trino (was: )
> creating a service will throw NPE when using service.check.user parameter
> -
>
> Key: RANGER-4501
> URL: https://issues.apache.org/jira/browse/RANGER-4501
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.4.0
>Reporter: Daqian Liao
>Assignee: Daqian Liao
>Priority: Major
> Labels: Trino
> Attachments: NEP.png, create_user.patch
>
>
> !NEP.png|width=899,height=487!
>
> {code:java}
> //代码占位符
> 2023-10-27 12:02:45,799 [http-nio-6080-exec-13] ERROR [ServiceREST.java:775]
> createService(RangerService={id={null} guid={null} isEnabled={true}
> createdBy={null} updatedBy={null} createTime={null} updateTime={null}
> version={1} name={trino-service-check-user}
> displayName={trino-service-check-user} type={trino}
> description={trino-service-check-user} tagService={} configs={password={}
> service.check.user={ii,oo} ranger.plugin.audit.filters={}
> jdbc.driverClassName={io.trino.jdbc.TrinoDriver}
> jdbc.url={jdbc:presto://localhost:9000} username={hadoop} }
> policyVersion={null} policyUpdateTime={null} tagVersion={1}
> tagUpdateTime={null} }) failed
> java.lang.NullPointerException: null
> at
> org.apache.ranger.biz.ServiceDBStore.populateDefaultPolicies(ServiceDBStore.java:3345)
> at
> org.apache.ranger.biz.ServiceDBStore.createDefaultPolicies(ServiceDBStore.java:3261)
> at
> org.apache.ranger.biz.ServiceDBStore.createService(ServiceDBStore.java:1576)
> at
> org.apache.ranger.rest.ServiceREST.createService(ServiceREST.java:771)
> at
> org.apache.ranger.rest.ServiceREST$$FastClassBySpringCGLIB$$92dab672.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:783)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
> at
> org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:61)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:753)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:698)
> at
> org.apache.ranger.rest.ServiceREST$$EnhancerBySpringCGLIB$$8c627be3.createService()
> at sun.reflect.GeneratedMethodAccessor844.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
>
[jira] [Updated] (RANGER-4503) Trino plugin is not published to maven central repo
[ https://issues.apache.org/jira/browse/RANGER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4503: Labels: Trino (was: ) > Trino plugin is not published to maven central repo > --- > > Key: RANGER-4503 > URL: https://issues.apache.org/jira/browse/RANGER-4503 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Affects Versions: 2.4.0 >Reporter: Roelof Naude >Priority: Minor > Labels: Trino > > Trying to use the ranger trino plugin with an instance of trino. The plugin > has not been published to a public repo, e.g.: > [https://repo1.maven.org/maven2/org/apache/ranger/ranger-distro/2.4.0/] > > Building the plugin results in an incomplete archive, ie no lib or > install/lib directories. This could very well be due to my own fault. > > Is there perhaps a different place where the artifact is published? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4626) Ranger don’t support trino to enable kerberos
[ https://issues.apache.org/jira/browse/RANGER-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4626: Labels: Trino (was: ) > Ranger don’t support trino to enable kerberos > - > > Key: RANGER-4626 > URL: https://issues.apache.org/jira/browse/RANGER-4626 > Project: Ranger > Issue Type: New Feature > Components: plugins >Reporter: Yanxiang Qin >Priority: Major > Labels: Trino > Attachments: ranger.png, trino.png > > Time Spent: 10m > Remaining Estimate: 0h > > When trino to enable kerberos, the range Test Connection failed -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4640) Ranger Support for Trino 433
[ https://issues.apache.org/jira/browse/RANGER-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820665#comment-17820665 ] Pradeep Agrawal commented on RANGER-4640: - [~shreyas-dview] Can we build ranger with jdk 8, 11 and 17 after this patch ? > Ranger Support for Trino 433 > - > > Key: RANGER-4640 > URL: https://issues.apache.org/jira/browse/RANGER-4640 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Shreyas B >Priority: Minor > Labels: Trino > Time Spent: 2h 40m > Remaining Estimate: 0h > > Trino has reached 4XX version whereas official ranger trino plugin support is > till 377 which was the trino version 2 years. Maybe it's time to update > ranger-trino plugin? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4640) Ranger Support for Trino 433
[ https://issues.apache.org/jira/browse/RANGER-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4640: Labels: Trino (was: ) > Ranger Support for Trino 433 > - > > Key: RANGER-4640 > URL: https://issues.apache.org/jira/browse/RANGER-4640 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Shreyas B >Priority: Minor > Labels: Trino > Time Spent: 2h 40m > Remaining Estimate: 0h > > Trino has reached 4XX version whereas official ranger trino plugin support is > till 377 which was the trino version 2 years. Maybe it's time to update > ranger-trino plugin? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4683) Trino Schema Creation Permission
[
https://issues.apache.org/jira/browse/RANGER-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4683:
Labels: Trino (was: )
> Trino Schema Creation Permission
>
>
> Key: RANGER-4683
> URL: https://issues.apache.org/jira/browse/RANGER-4683
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Semetey Coskun
>Priority: Major
> Labels: Trino
>
> Hi,
> I'm running Trino in docker (trinodb/trino:423) and this environment is
> integrated to Apache Ranger (2.4.0) for authz policies. Every permissions
> seem OK but "Create Schema" in a catalog. I've tried various configurations;
> specifying catalog names with "*" or exact name of the catalog which I'm
> trying to create schema in it but every time same error.
>
> {{io.cloudbeaver.DBWebException: Error executing query: SQL Error [4]: Query
> failed (#20240129_203356_00589_c9776): Access Denied: Cannot create schema
> delta.trino_poc at
> io.cloudbeaver.service.sql.WebSQLProcessor.processQuery(WebSQLProcessor.java:264)
> at
> io.cloudbeaver.service.sql.impl.WebServiceSQL$1.run(WebServiceSQL.java:377)
> at io.cloudbeaver.model.session.WebSession$1.run(WebSession.java:692) at
> org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105) at
> org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) Caused by:
> org.jkiss.dbeaver.model.sql.DBSQLException: SQL Error [4]: Query failed
> (#20240129_203356_00589_c9776): Access Denied: Cannot create schema
> delta.trino_poc at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:133)
> at
> io.cloudbeaver.service.sql.WebSQLProcessor.lambda$1(WebSQLProcessor.java:250)
> at
> org.jkiss.dbeaver.model.exec.DBExecUtils.tryExecuteRecover(DBExecUtils.java:190)
> at
> io.cloudbeaver.service.sql.WebSQLProcessor.processQuery(WebSQLProcessor.java:207)
> ... 4 more Caused by: java.sql.SQLException: Query failed
> (#20240129_203356_00589_c9776): Access Denied: Cannot create schema
> delta.trino_poc at
> io.trino.jdbc.AbstractTrinoResultSet.resultsException(AbstractTrinoResultSet.java:1937)
> at io.trino.jdbc.TrinoResultSet.getColumns(TrinoResultSet.java:318) at
> io.trino.jdbc.TrinoResultSet.create(TrinoResultSet.java:61) at
> io.trino.jdbc.TrinoStatement.internalExecute(TrinoStatement.java:262) at
> io.trino.jdbc.TrinoStatement.execute(TrinoStatement.java:240) at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.execute(JDBCStatementImpl.java:330)
> at
> org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCStatementImpl.executeStatement(JDBCStatementImpl.java:131)
> ... 7 more Caused by: io.trino.spi.security.AccessDeniedException: Access
> Denied: Cannot create schema delta.trino_poc at
> io.trino.spi.security.AccessDeniedException.denyCreateSchema(AccessDeniedException.java:150)
> at
> io.trino.spi.security.AccessDeniedException.denyCreateSchema(AccessDeniedException.java:145)
> at
> io.trino.spi.security.SystemAccessControl.checkCanCreateSchema(SystemAccessControl.java:286)
> at
> io.trino.security.AccessControlManager.lambda$checkCanCreateSchema$11(AccessControlManager.java:340)
> at
> io.trino.security.AccessControlManager.systemAuthorizationCheck(AccessControlManager.java:1363)
> at
> io.trino.security.AccessControlManager.checkCanCreateSchema(AccessControlManager.java:340)
> at
> io.trino.security.ForwardingAccessControl.checkCanCreateSchema(ForwardingAccessControl.java:125)
> at
> io.trino.tracing.TracingAccessControl.checkCanCreateSchema(TracingAccessControl.java:166)
> at
> io.trino.execution.CreateSchemaTask.internalExecute(CreateSchemaTask.java:117)
> at io.trino.execution.CreateSchemaTask.execute(CreateSchemaTask.java:82) at
> io.trino.execution.CreateSchemaTask.execute(CreateSchemaTask.java:54) at
> io.trino.execution.DataDefinitionExecution.start(DataDefinitionExecution.java:145)
> at io.trino.execution.SqlQueryManager.createQuery(SqlQueryManager.java:256)
> at
> io.trino.dispatcher.LocalDispatchQuery.startExecution(LocalDispatchQuery.java:145)
> at
> io.trino.dispatcher.LocalDispatchQuery.lambda$waitForMinimumWorkers$2(LocalDispatchQuery.java:129)
> at
> io.airlift.concurrent.MoreFutures.lambda$addSuccessCallback$12(MoreFutures.java:568)
> at io.airlift.concurrent.MoreFutures$3.onSuccess(MoreFutures.java:543) at
> com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1133)
> at io.trino.$gen.Trino_42320240129_094308_2.run(Unknown Source) at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)}}
>
> {{When I grep the coordinator
[jira] [Commented] (RANGER-4076) Support Java 17 for build and runtime
[ https://issues.apache.org/jira/browse/RANGER-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820661#comment-17820661 ] Pradeep Agrawal commented on RANGER-4076: - [~andrewluo] : After this patch can we build ranger on jdk 8 and 11 also ? > Support Java 17 for build and runtime > - > > Key: RANGER-4076 > URL: https://issues.apache.org/jira/browse/RANGER-4076 > Project: Ranger > Issue Type: New Feature > Components: admin, build-infra >Reporter: Andrew Luo >Priority: Major > Attachments: > 0001-RANGER-4076-Support-Java-17-for-build-and-runtime.patch > > > Currently only Java 8 and 11 are supported. Java 17 is a major LTS version > of Java and adding support would modernize our Java version support. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4689) Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB
[ https://issues.apache.org/jira/browse/RANGER-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4689: Fix Version/s: 3.0.0 > Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB > --- > > Key: RANGER-4689 > URL: https://issues.apache.org/jira/browse/RANGER-4689 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4689-Fix-Ranger-Javapatch-failure-even-if-ser.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4689) Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB
[ https://issues.apache.org/jira/browse/RANGER-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4689: Attachment: 0001-RANGER-4689-Fix-Ranger-Javapatch-failure-even-if-ser.patch > Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB > --- > > Key: RANGER-4689 > URL: https://issues.apache.org/jira/browse/RANGER-4689 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0001-RANGER-4689-Fix-Ranger-Javapatch-failure-even-if-ser.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4689) Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB
Pradeep Agrawal created RANGER-4689: --- Summary: Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB Key: RANGER-4689 URL: https://issues.apache.org/jira/browse/RANGER-4689 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 3.0.0 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4597) /users/{user_id}/emailchange API is not accessible by keyadmin user
[
https://issues.apache.org/jira/browse/RANGER-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal resolved RANGER-4597.
-
Resolution: Fixed
> /users/{user_id}/emailchange API is not accessible by keyadmin user
> ---
>
> Key: RANGER-4597
> URL: https://issues.apache.org/jira/browse/RANGER-4597
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> {color:#172b4d}/users/\{user_id}/emailchange API is not accessible by
> keyadmin user and it returns 403 forbidden status code.{color}
> {color:#172b4d}However, the keyadmin user can update the user email id using
> Ranger Admin UI,{color}
> {color:#172b4d}and using PUT request to other APIs like /xusers/users and
> /users.{color}
> {color:#172b4d}The behaviour has to be kept consistent and the user should be
> allowed access to the emailchange API{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4576) Implement best coding practice for the {BASE_URL}/plugins/policies/{service_type}/for-resource API
[
https://issues.apache.org/jira/browse/RANGER-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4576:
Attachment: 0016-RANGER-4576-User-without-access-to-policy-is-able-to.patch
> Implement best coding practice for the
> {BASE_URL}/plugins/policies/{service_type}/for-resource API
> --
>
> Key: RANGER-4576
> URL: https://issues.apache.org/jira/browse/RANGER-4576
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0016-RANGER-4576-User-without-access-to-policy-is-able-to.patch
>
>
> Implement best coding practice for the
> \{BASE_URL}/plugins/policies/\{service_type}/for-resource API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4573) /xaudit/trx_log API not accessible by keyadmin user
[
https://issues.apache.org/jira/browse/RANGER-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4573:
Attachment: 0012-RANGER-4573-xaudit-trx_log-API-not-accessible-by-key.patch
> /xaudit/trx_log API not accessible by keyadmin user
> ---
>
> Key: RANGER-4573
> URL: https://issues.apache.org/jira/browse/RANGER-4573
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0012-RANGER-4573-xaudit-trx_log-API-not-accessible-by-key.patch
>
>
> {color:#172b4d}If a keyadmin user makes a request to /xaudit/trx_log API
> endpoint,{color}
> {color:#172b4d}the response is 403 forbidden.{color}
> {color:#172b4d}However, the same function used in /xaudit/trx_log is called
> by the /assets/report API,{color}
> {color:#172b4d}and the /assets/report API is accessible by the keyadmin user,
> so ideally, the /xaudit/trx_log API should be accessible
> {color}{color:#172b4d}by the keyadmin user as well.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4574) Implement best coding practice for /public/v2/api/service/{service_name}/policy/{policy_name}
[
https://issues.apache.org/jira/browse/RANGER-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4574:
Attachment: 0014-RANGER-4574-public-v2-api-service-service_name-polic.patch
> Implement best coding practice for
> /public/v2/api/service/{service_name}/policy/{policy_name}
> -
>
> Key: RANGER-4574
> URL: https://issues.apache.org/jira/browse/RANGER-4574
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0014-RANGER-4574-public-v2-api-service-service_name-polic.patch
>
>
> Implement best coding practice for the
> /public/v2/api/service/\{service_name}/policy/\{policy_name} API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4588) /xaudit/trx_log/{trx_log_id} is not accessible by keyadmin user
[
https://issues.apache.org/jira/browse/RANGER-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4588:
Attachment: 0019-RANGER-4588-xaudit-trx_log-trx_log_id-is-not-accessi.patch
> /xaudit/trx_log/{trx_log_id} is not accessible by keyadmin user
> ---
>
> Key: RANGER-4588
> URL: https://issues.apache.org/jira/browse/RANGER-4588
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0019-RANGER-4588-xaudit-trx_log-trx_log_id-is-not-accessi.patch
>
>
> keyadmin users can access the trx_logs using the /assets/report and
> /assets/report/\{transaction_id} API.
> However, the keyadmin user is not allowed to access the /xaudit/trx_log/\{id}
> API and
> it results in 403 forbidden status code.
> Ideally, as the keyadmin user is allowed to access the kms related entities
> from other APIs, the user should be allowed to access the details using
> /xaudit/trx_log/\{id} API as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4591) Add improvements for /assets/report/{transaction_id} API
[
https://issues.apache.org/jira/browse/RANGER-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4591:
Attachment: 0020-RANGER-4591-keyadmin-user-can-access-non-kms-related.patch
> Add improvements for /assets/report/{transaction_id} API
> -
>
> Key: RANGER-4591
> URL: https://issues.apache.org/jira/browse/RANGER-4591
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0020-RANGER-4591-keyadmin-user-can-access-non-kms-related.patch
>
>
> Add improvements for /assets/report/\{transaction_id} API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4589) keyadmin user can update the user password via UI but cannot update the user password using /users/{user_id}/passwordchange API
[
https://issues.apache.org/jira/browse/RANGER-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4589:
Attachment: 0018-RANGER-4589-keyadmin-user-can-update-the-user-passwo.patch
> keyadmin user can update the user password via UI but cannot update the user
> password using /users/{user_id}/passwordchange API
> ---
>
> Key: RANGER-4589
> URL: https://issues.apache.org/jira/browse/RANGER-4589
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0018-RANGER-4589-keyadmin-user-can-update-the-user-passwo.patch
>
>
> keyadmin user can update the user password through /xusers API or via Ranger
> admin UI, however, if the keyadmin user tries to update the password through
> /users/\{user_id}/passwordchange API, the response is 403 forbidden.
> The behaviour has to be kept consistent for the keyadmin users across the
> APIs for passswordchange
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4595) Mask / remove some fields from GET /users API for keyadmin users
[ https://issues.apache.org/jira/browse/RANGER-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4595: Attachment: 0022-RANGER-4595-keyadmin-user-able-to-view-the-user-perm.patch > Mask / remove some fields from GET /users API for keyadmin users > > > Key: RANGER-4595 > URL: https://issues.apache.org/jira/browse/RANGER-4595 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0022-RANGER-4595-keyadmin-user-able-to-view-the-user-perm.patch > > > Mask / remove some fields from GET /users API for keyadmin users -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4594) Add improvement to PUT request for keyadmin user with respect to status field
[ https://issues.apache.org/jira/browse/RANGER-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4594: Attachment: 0021-RANGER-4594-keyadmin-user-can-mark-ROLE_USER-users-a.patch > Add improvement to PUT request for keyadmin user with respect to status field > - > > Key: RANGER-4594 > URL: https://issues.apache.org/jira/browse/RANGER-4594 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0021-RANGER-4594-keyadmin-user-can-mark-ROLE_USER-users-a.patch > > > Add improvement to PUT request for keyadmin user with respect to status field -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4586) Add improvement for UserREST and XUserREST APIs for keyadmin users
[ https://issues.apache.org/jira/browse/RANGER-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4586: Attachment: 0025-RANGER-4586-XUserREST-and-UserREST-API-improvement-f.patch > Add improvement for UserREST and XUserREST APIs for keyadmin users > -- > > Key: RANGER-4586 > URL: https://issues.apache.org/jira/browse/RANGER-4586 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0025-RANGER-4586-XUserREST-and-UserREST-API-improvement-f.patch > > > Add improvement for UserREST and XUserREST APIs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4596) Response of /users API for keyadmin users should be consistent with the UI behaviour for viewing users on the UI
[ https://issues.apache.org/jira/browse/RANGER-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4596: Attachment: 0023-RANGER-4596-keyadmin-can-fetch-the-details-of-admin-.patch > Response of /users API for keyadmin users should be consistent with the UI > behaviour for viewing users on the UI > > > Key: RANGER-4596 > URL: https://issues.apache.org/jira/browse/RANGER-4596 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0023-RANGER-4596-keyadmin-can-fetch-the-details-of-admin-.patch > > > Response of /users API for keyadmin users should be consistent with the UI > behaviour for viewing users on the UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4577) Implement best coding practice for the /xusers/users API for keyadmin users
[ https://issues.apache.org/jira/browse/RANGER-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4577: Attachment: 0017-RANGER-4577-UI-and-API-behaviour-for-fetching-users-.patch > Implement best coding practice for the /xusers/users API for keyadmin users > --- > > Key: RANGER-4577 > URL: https://issues.apache.org/jira/browse/RANGER-4577 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek >Assignee: Pradeep Agrawal >Priority: Major > Attachments: > 0017-RANGER-4577-UI-and-API-behaviour-for-fetching-users-.patch > > > Implement best coding practice for the /xusers/users API for keyadmin users -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4575) Implement best coding practice for /plugins/policy/{policy_id}/version/{version_number} API
[
https://issues.apache.org/jira/browse/RANGER-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4575:
Attachment: 0015-RANGER-4575-plugins-policy-policy_id-version-version.patch
> Implement best coding practice for
> /plugins/policy/{policy_id}/version/{version_number} API
>
>
> Key: RANGER-4575
> URL: https://issues.apache.org/jira/browse/RANGER-4575
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0015-RANGER-4575-plugins-policy-policy_id-version-version.patch
>
>
> Implement best coding practice for
> /plugins/policy/\{policy_id}/version/\{version_number} API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4578) /xuser/groupgroups and /xuser/groupusers APIs allow creation of entities even without groupId / userId fields in the request
[
https://issues.apache.org/jira/browse/RANGER-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4578:
Attachment: 0013-RANGER-4578-xuser-groupgroups-and-xuser-groupusers-A.patch
> /xuser/groupgroups and /xuser/groupusers APIs allow creation of entities even
> without groupId / userId fields in the request
>
>
> Key: RANGER-4578
> URL: https://issues.apache.org/jira/browse/RANGER-4578
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0013-RANGER-4578-xuser-groupgroups-and-xuser-groupusers-A.patch
>
>
> /xuser/groupgroups and /xuser/groupusers APIs allow creation of entities even
> without groupId / userId fields in the request.
> The typical request payload to create an entity using the /xusers/groupgroups
> API endpoint is :-
> {code:java|bgColor=#f4f5f7}
> {"name": {group_name}, "parentGroupId": {parent_group_id}, "groupId":
> {child_group_id}} {code}
> But if a POST request is performed without the groupId / parentGroupId, still
> the request succeeds.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4598) Add improvement for /xusers/groups/groupName/{group_name} API for ROLE_USER users
[
https://issues.apache.org/jira/browse/RANGER-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4598:
Attachment: 0024-RANGER-4598-ROLE_USER-cannot-acccess-xusers-groups-A.patch
> Add improvement for /xusers/groups/groupName/{group_name} API for ROLE_USER
> users
> -
>
> Key: RANGER-4598
> URL: https://issues.apache.org/jira/browse/RANGER-4598
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0024-RANGER-4598-ROLE_USER-cannot-acccess-xusers-groups-A.patch
>
>
> Add improvement for /xusers/groups/groupName/\{group_name} API for ROLE_USER
> users
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4607) Ranger REST API improvements
[ https://issues.apache.org/jira/browse/RANGER-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pradeep Agrawal updated RANGER-4607: Attachment: 0001-RANGER-4607-Ranger-REST-API-improvements.patch > Ranger REST API improvements > > > Key: RANGER-4607 > URL: https://issues.apache.org/jira/browse/RANGER-4607 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.4.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Attachments: 0001-RANGER-4607-Ranger-REST-API-improvements.patch > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4607) Ranger REST API improvements
Pradeep Agrawal created RANGER-4607: --- Summary: Ranger REST API improvements Key: RANGER-4607 URL: https://issues.apache.org/jira/browse/RANGER-4607 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 3.0.0, 2.4.1 Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4572) Upgrade Apache Derby to 10.17.1.0
Pradeep Agrawal created RANGER-4572: --- Summary: Upgrade Apache Derby to 10.17.1.0 Key: RANGER-4572 URL: https://issues.apache.org/jira/browse/RANGER-4572 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Pradeep Agrawal Assignee: Pradeep Agrawal -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4550) API request to /assets/resource/{id} returns no response
[
https://issues.apache.org/jira/browse/RANGER-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790528#comment-17790528
]
Pradeep Agrawal commented on RANGER-4550:
-
Review request link : https://reviews.apache.org/r/74763/
> API request to /assets/resource/{id} returns no response
>
>
> Key: RANGER-4550
> URL: https://issues.apache.org/jira/browse/RANGER-4550
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0011-RANGER-4550-API-request-to-assets-resource-id-return.patch
>
>
> When a request is made to the API endpoint /assets/resource/\{id}, no
> response is returned and the status code is 204 No response.
> Ideally, the response should contain the details for the resource with the
> given id
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4548) Return proper error message in the response for /tags/tags, /tags/resources and /tags/types API for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790526#comment-17790526
]
Pradeep Agrawal commented on RANGER-4548:
-
Review request link : https://reviews.apache.org/r/74763/
> Return proper error message in the response for /tags/tags, /tags/resources
> and /tags/types API for non admin users
> ---
>
> Key: RANGER-4548
> URL: https://issues.apache.org/jira/browse/RANGER-4548
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0003-RANGER-4548-Return-proper-error-message-in-the-respo.patch
>
>
> /tags/tags and /tags/types, /tags/resources APIs are not accessible by non
> admin users,
> but when the users make a request, a proper error message should be returned
> stating that the users do not have privilege.
> Currently, the error message returned is not explanatory.
> Response returned for non admin users :-
> {code:java}
>
> content="IE=edge,chrome=1"> Ranger - Sign In name="description" content=""> content="width=device-width"> href="images/favicon.ico"> media="all" rel="stylesheet" type="text/css" id="bootstrap-css"> rel="stylesheet" href="styles/font-awesome.min.css"> href="styles/xa.css" media="all" rel="stylesheet" type="text/css"> src="libs/bower/jquery/js/jquery-3.5.1.js"> src="scripts/prelogin/XAPrelogin.js"> type="text/javascript">$(document).ready(function() {
> var updateBoxPosition = function() {
> $('#signin-container').css({'margin-top' :
> ($(window).height() - $('#signin-container').height()) / 2
> });};$(window).resize(updateBoxPosition);
>var queryParams = JSON.parse('{"' +
> decodeURI((location.href.split('?')[1] || 'g=0').replace(/=/g, "\":\"")) +
> '"}');if(queryParams.sessionTimeout){
> window.alert('Session Timeout');
> location.replace("login.jsp");}
> setTimeout(updateBoxPosition, 50);});
>
> id="signin-container" style="margin-top: 4.5px;">
>
>
>
> Username:
>
> Password:
> tabindex="2" autocomplete="off">
> style="color:white;display:none;">
>
> id="errorBoxUnsynced" class="help-inline"
> style="color:white;display:none;">User is not available in HDP Admin Tool.
> Please contact your Administrator.
> Sign In
>style="display: none;">
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4553) Response metrics for /xaudit/trx_log not proper
[
https://issues.apache.org/jira/browse/RANGER-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790531#comment-17790531
]
Pradeep Agrawal commented on RANGER-4553:
-
Review request link : https://reviews.apache.org/r/74763/
> Response metrics for /xaudit/trx_log not proper
> ---
>
> Key: RANGER-4553
> URL: https://issues.apache.org/jira/browse/RANGER-4553
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0008-RANGER-4553-Response-metrics-for-xaudit-trx_log-not-.patch
>
>
> When a request is made to /xaudit/trx_log API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 200,"totalCount": 0,
> "resultSize": 0,"queryTimeMS": 1700214070565, ...} {code}
> Ideally, the total count value should reflect the total number of logs
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4549) Non admin users cannot access /public/v2/api/roles/names and /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
[
https://issues.apache.org/jira/browse/RANGER-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790527#comment-17790527
]
Pradeep Agrawal commented on RANGER-4549:
-
Review request link : https://reviews.apache.org/r/74763/
> Non admin users cannot access /public/v2/api/roles/names and
> /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
> ---
>
> Key: RANGER-4549
> URL: https://issues.apache.org/jira/browse/RANGER-4549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0005-RANGER-4549-Non-admin-users-cannot-access-public-v2-.patch
>
>
> Non admin users cannot access /public/v2/api/roles/names API, but can access
> the /public/v2/api/roles API and fetch the details of all the roles.
> Since the users can fetch the details from the roles API itself, the
> restriction for non admin users to access /roles/names and
> /roles/name/\{name} API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4552) Response metrics for /assets/report is not proper, and pagination does not work
[
https://issues.apache.org/jira/browse/RANGER-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790530#comment-17790530
]
Pradeep Agrawal commented on RANGER-4552:
-
Review request link : https://reviews.apache.org/r/74763/
> Response metrics for /assets/report is not proper, and pagination does not
> work
> ---
>
> Key: RANGER-4552
> URL: https://issues.apache.org/jira/browse/RANGER-4552
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0007-RANGER-4552-Response-metrics-for-assets-report-is-no.patch
>
>
> When a request is made to the /assets/report API endpoint, the response
> metrics like
> result size is incorrect. Ideally, it should reflect the total number of
> objects returned
> {code:java}
> {"startIndex": 2,"pageSize": 100,"totalCount": 178,
> "resultSize": 0,"queryTimeMS": 1700217495822 {code}
> Even the pagination for the API does not work properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4554) Response metrics for /assets/resources not proper
[
https://issues.apache.org/jira/browse/RANGER-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790532#comment-17790532
]
Pradeep Agrawal commented on RANGER-4554:
-
Review request link : https://reviews.apache.org/r/74763/
> Response metrics for /assets/resources not proper
> -
>
> Key: RANGER-4554
> URL: https://issues.apache.org/jira/browse/RANGER-4554
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0009-RANGER-4554-Response-metrics-for-assets-resources-no.patch
>
>
> When a request is made to /assets/resources API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of resources
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4555) Response metrics for /assets/assets API not proper
[
https://issues.apache.org/jira/browse/RANGER-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790534#comment-17790534
]
Pradeep Agrawal commented on RANGER-4555:
-
Review request link : https://reviews.apache.org/r/74763/
> Response metrics for /assets/assets API not proper
> --
>
> Key: RANGER-4555
> URL: https://issues.apache.org/jira/browse/RANGER-4555
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0010-RANGER-4555-Response-metrics-for-assets-assets-API-n.patch
>
>
> When a request is made to /assets/assets API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of assets (the
> value returned by /assets/assets/count API is proper).
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4551) No response returned for /assets/policyList/{service_name} API
[
https://issues.apache.org/jira/browse/RANGER-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790529#comment-17790529
]
Pradeep Agrawal commented on RANGER-4551:
-
Review request link : https://reviews.apache.org/r/74763/
> No response returned for /assets/policyList/{service_name} API
> --
>
> Key: RANGER-4551
> URL: https://issues.apache.org/jira/browse/RANGER-4551
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0006-RANGER-4551-No-response-returned-for-assets-policyLi.patch
>
>
> When a request is made to the /assets/policyList/\{service_name} API,
> the response is empty and the status code is 304 Not Modified.
> If there is no expected response, then the API has to be deprecated,
> otherwise the API has to be fixed to return the proper response
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4545) DELETE /assets/resources/{resource_id} API should return proper status code for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790523#comment-17790523
]
Pradeep Agrawal commented on RANGER-4545:
-
Review request link : https://reviews.apache.org/r/74763/
> DELETE /assets/resources/{resource_id} API should return proper status code
> for non admin users
> ---
>
> Key: RANGER-4545
> URL: https://issues.apache.org/jira/browse/RANGER-4545
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0001-RANGER-4545-DELETE-assets-resources-resource_id-API-.patch
>
>
> When a non admin user makes a DELETE request to
> /assets/resources/\{resource_id} endpoint, 405 method not allowed response is
> returned.
> The error message also contains HTML response.
> {code:java}
>
> HTTP Status 405 ? Method Not Allowed type="text/css">body {font-family: Tahoma, Arial,
> sans-serif;}
> h1,h2,h3,b {color: white;
>background-color: #525D76;}
> h1 {font-size: 22px;}
> h2 {font-size: 16px;}
> h3 {font-size: 14px;}
> p {font-size: 12px;}
> a {color: black;}
> .line {height: 1px;background-color: #525D76;
>border: none;}
> HTTP Status 405 ? Method Not Allowed
> {code}
> The status code / error message is not explanatory as ideally, a 403
> Forbidden or a 400 Bad Request status code with appropriate error message
> should be returned as the error should be related to the user permission.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4546) /assets/ugsyncAudits/{sync_source} API is accessible by user without permission on audit module
[
https://issues.apache.org/jira/browse/RANGER-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790524#comment-17790524
]
Pradeep Agrawal commented on RANGER-4546:
-
Review request link : https://reviews.apache.org/r/74763/
> /assets/ugsyncAudits/{sync_source} API is accessible by user without
> permission on audit module
> ---
>
> Key: RANGER-4546
> URL: https://issues.apache.org/jira/browse/RANGER-4546
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0002-RANGER-4546-assets-ugsyncAudits-sync_source-API-is-a.patch
>
>
> A user without permission on the audits module is able to access the
> /assets/ugsyncAudits/\{sync_source} API.
> Ideally, the user should not be allowed to access the API, and it should
> result in a 403 error.
> If the same user tries to access the /assets/ugsyncAudits API, it results in
> a 403 error (as expected).
> Similarly, the behaviour has to be changed for the
> /assets/ugsyncAudits/\{sync_source} API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4547) The reponse metrics (pagination values) for the /assets/ugsyncAudits/{sync_source} API is not proper
[
https://issues.apache.org/jira/browse/RANGER-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790525#comment-17790525
]
Pradeep Agrawal commented on RANGER-4547:
-
Review request link : https://reviews.apache.org/r/74763/
> The reponse metrics (pagination values) for the
> /assets/ugsyncAudits/{sync_source} API is not proper
>
>
> Key: RANGER-4547
> URL: https://issues.apache.org/jira/browse/RANGER-4547
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0
>
> Attachments:
> 0004-RANGER-4547-The-reponse-metrics-pagination-values-fo.patch
>
>
> When a request is made to the /assets/ugsyncAudits/\{sync_source} API,
> the metrics like total count, result size is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215450040,"vxUgsyncAuditInfoList": [{
> {code}
> Ideally, it should reflect the total number of audits.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4553) Response metrics for /xaudit/trx_log not proper
[
https://issues.apache.org/jira/browse/RANGER-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4553:
Attachment: 0008-RANGER-4553-Response-metrics-for-xaudit-trx_log-not-.patch
> Response metrics for /xaudit/trx_log not proper
> ---
>
> Key: RANGER-4553
> URL: https://issues.apache.org/jira/browse/RANGER-4553
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0008-RANGER-4553-Response-metrics-for-xaudit-trx_log-not-.patch
>
>
> When a request is made to /xaudit/trx_log API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 200,"totalCount": 0,
> "resultSize": 0,"queryTimeMS": 1700214070565, ...} {code}
> Ideally, the total count value should reflect the total number of logs
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4552) Response metrics for /assets/report is not proper, and pagination does not work
[
https://issues.apache.org/jira/browse/RANGER-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4552:
Attachment: 0007-RANGER-4552-Response-metrics-for-assets-report-is-no.patch
> Response metrics for /assets/report is not proper, and pagination does not
> work
> ---
>
> Key: RANGER-4552
> URL: https://issues.apache.org/jira/browse/RANGER-4552
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0007-RANGER-4552-Response-metrics-for-assets-report-is-no.patch
>
>
> When a request is made to the /assets/report API endpoint, the response
> metrics like
> result size is incorrect. Ideally, it should reflect the total number of
> objects returned
> {code:java}
> {"startIndex": 2,"pageSize": 100,"totalCount": 178,
> "resultSize": 0,"queryTimeMS": 1700217495822 {code}
> Even the pagination for the API does not work properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4554) Response metrics for /assets/resources not proper
[
https://issues.apache.org/jira/browse/RANGER-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4554:
Attachment: 0009-RANGER-4554-Response-metrics-for-assets-resources-no.patch
> Response metrics for /assets/resources not proper
> -
>
> Key: RANGER-4554
> URL: https://issues.apache.org/jira/browse/RANGER-4554
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0009-RANGER-4554-Response-metrics-for-assets-resources-no.patch
>
>
> When a request is made to /assets/resources API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of resources
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4555) Response metrics for /assets/assets API not proper
[
https://issues.apache.org/jira/browse/RANGER-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4555:
Attachment: 0010-RANGER-4555-Response-metrics-for-assets-assets-API-n.patch
> Response metrics for /assets/assets API not proper
> --
>
> Key: RANGER-4555
> URL: https://issues.apache.org/jira/browse/RANGER-4555
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0010-RANGER-4555-Response-metrics-for-assets-assets-API-n.patch
>
>
> When a request is made to /assets/assets API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of assets (the
> value returned by /assets/assets/count API is proper).
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4551) No response returned for /assets/policyList/{service_name} API
[
https://issues.apache.org/jira/browse/RANGER-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4551:
Attachment: 0006-RANGER-4551-No-response-returned-for-assets-policyLi.patch
> No response returned for /assets/policyList/{service_name} API
> --
>
> Key: RANGER-4551
> URL: https://issues.apache.org/jira/browse/RANGER-4551
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0006-RANGER-4551-No-response-returned-for-assets-policyLi.patch
>
>
> When a request is made to the /assets/policyList/\{service_name} API,
> the response is empty and the status code is 304 Not Modified.
> If there is no expected response, then the API has to be deprecated,
> otherwise the API has to be fixed to return the proper response
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4550) API request to /assets/resource/{id} returns no response
[
https://issues.apache.org/jira/browse/RANGER-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4550:
Attachment: 0011-RANGER-4550-API-request-to-assets-resource-id-return.patch
> API request to /assets/resource/{id} returns no response
>
>
> Key: RANGER-4550
> URL: https://issues.apache.org/jira/browse/RANGER-4550
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0011-RANGER-4550-API-request-to-assets-resource-id-return.patch
>
>
> When a request is made to the API endpoint /assets/resource/\{id}, no
> response is returned and the status code is 204 No response.
> Ideally, the response should contain the details for the resource with the
> given id
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4548) Return proper error message in the response for /tags/tags, /tags/resources and /tags/types API for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4548:
Attachment: 0003-RANGER-4548-Return-proper-error-message-in-the-respo.patch
> Return proper error message in the response for /tags/tags, /tags/resources
> and /tags/types API for non admin users
> ---
>
> Key: RANGER-4548
> URL: https://issues.apache.org/jira/browse/RANGER-4548
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0003-RANGER-4548-Return-proper-error-message-in-the-respo.patch
>
>
> /tags/tags and /tags/types, /tags/resources APIs are not accessible by non
> admin users,
> but when the users make a request, a proper error message should be returned
> stating that the users do not have privilege.
> Currently, the error message returned is not explanatory.
> Response returned for non admin users :-
> {code:java}
>
> content="IE=edge,chrome=1"> Ranger - Sign In name="description" content=""> content="width=device-width"> href="images/favicon.ico"> media="all" rel="stylesheet" type="text/css" id="bootstrap-css"> rel="stylesheet" href="styles/font-awesome.min.css"> href="styles/xa.css" media="all" rel="stylesheet" type="text/css"> src="libs/bower/jquery/js/jquery-3.5.1.js"> src="scripts/prelogin/XAPrelogin.js"> type="text/javascript">$(document).ready(function() {
> var updateBoxPosition = function() {
> $('#signin-container').css({'margin-top' :
> ($(window).height() - $('#signin-container').height()) / 2
> });};$(window).resize(updateBoxPosition);
>var queryParams = JSON.parse('{"' +
> decodeURI((location.href.split('?')[1] || 'g=0').replace(/=/g, "\":\"")) +
> '"}');if(queryParams.sessionTimeout){
> window.alert('Session Timeout');
> location.replace("login.jsp");}
> setTimeout(updateBoxPosition, 50);});
>
> id="signin-container" style="margin-top: 4.5px;">
>
>
>
> Username:
>
> Password:
> tabindex="2" autocomplete="off">
> style="color:white;display:none;">
>
> id="errorBoxUnsynced" class="help-inline"
> style="color:white;display:none;">User is not available in HDP Admin Tool.
> Please contact your Administrator.
> Sign In
>style="display: none;">
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4546) /assets/ugsyncAudits/{sync_source} API is accessible by user without permission on audit module
[
https://issues.apache.org/jira/browse/RANGER-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4546:
Attachment: 0002-RANGER-4546-assets-ugsyncAudits-sync_source-API-is-a.patch
> /assets/ugsyncAudits/{sync_source} API is accessible by user without
> permission on audit module
> ---
>
> Key: RANGER-4546
> URL: https://issues.apache.org/jira/browse/RANGER-4546
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0002-RANGER-4546-assets-ugsyncAudits-sync_source-API-is-a.patch
>
>
> A user without permission on the audits module is able to access the
> /assets/ugsyncAudits/\{sync_source} API.
> Ideally, the user should not be allowed to access the API, and it should
> result in a 403 error.
> If the same user tries to access the /assets/ugsyncAudits API, it results in
> a 403 error (as expected).
> Similarly, the behaviour has to be changed for the
> /assets/ugsyncAudits/\{sync_source} API
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4549) Non admin users cannot access /public/v2/api/roles/names and /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
[
https://issues.apache.org/jira/browse/RANGER-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4549:
Attachment: 0005-RANGER-4549-Non-admin-users-cannot-access-public-v2-.patch
> Non admin users cannot access /public/v2/api/roles/names and
> /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
> ---
>
> Key: RANGER-4549
> URL: https://issues.apache.org/jira/browse/RANGER-4549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0005-RANGER-4549-Non-admin-users-cannot-access-public-v2-.patch
>
>
> Non admin users cannot access /public/v2/api/roles/names API, but can access
> the /public/v2/api/roles API and fetch the details of all the roles.
> Since the users can fetch the details from the roles API itself, the
> restriction for non admin users to access /roles/names and
> /roles/name/\{name} API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4547) The reponse metrics (pagination values) for the /assets/ugsyncAudits/{sync_source} API is not proper
[
https://issues.apache.org/jira/browse/RANGER-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4547:
Attachment: 0004-RANGER-4547-The-reponse-metrics-pagination-values-fo.patch
> The reponse metrics (pagination values) for the
> /assets/ugsyncAudits/{sync_source} API is not proper
>
>
> Key: RANGER-4547
> URL: https://issues.apache.org/jira/browse/RANGER-4547
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0004-RANGER-4547-The-reponse-metrics-pagination-values-fo.patch
>
>
> When a request is made to the /assets/ugsyncAudits/\{sync_source} API,
> the metrics like total count, result size is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215450040,"vxUgsyncAuditInfoList": [{
> {code}
> Ideally, it should reflect the total number of audits.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4545) DELETE /assets/resources/{resource_id} API should return proper status code for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-4545:
Attachment: 0001-RANGER-4545-DELETE-assets-resources-resource_id-API-.patch
> DELETE /assets/resources/{resource_id} API should return proper status code
> for non admin users
> ---
>
> Key: RANGER-4545
> URL: https://issues.apache.org/jira/browse/RANGER-4545
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
> Attachments:
> 0001-RANGER-4545-DELETE-assets-resources-resource_id-API-.patch
>
>
> When a non admin user makes a DELETE request to
> /assets/resources/\{resource_id} endpoint, 405 method not allowed response is
> returned.
> The error message also contains HTML response.
> {code:java}
>
> HTTP Status 405 ? Method Not Allowed type="text/css">body {font-family: Tahoma, Arial,
> sans-serif;}
> h1,h2,h3,b {color: white;
>background-color: #525D76;}
> h1 {font-size: 22px;}
> h2 {font-size: 16px;}
> h3 {font-size: 14px;}
> p {font-size: 12px;}
> a {color: black;}
> .line {height: 1px;background-color: #525D76;
>border: none;}
> HTTP Status 405 ? Method Not Allowed
> {code}
> The status code / error message is not explanatory as ideally, a 403
> Forbidden or a 400 Bad Request status code with appropriate error message
> should be returned as the error should be related to the user permission.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790402#comment-17790402
]
Pradeep Agrawal commented on RANGER-4562:
-
Without docker case :
1. I tried "mvn clean install" command on a fresh jdk11 cluster and i was able
to reproduce the issue with following error
{code:java}
[INFO] --- frontend-maven-plugin:1.12.1:npm (npm install for tests) @
security-admin-web ---
[INFO] Running 'npm install' in /root/ranger/security-admin/target/jstest
[INFO]
[INFO] > phantomjs-prebuilt@2.1.16 install
/root/ranger/security-admin/target/jstest/node_modules/phantomjs-prebuilt
[INFO] > node install.js
[INFO]
[INFO] PhantomJS not found on PATH
[INFO] Download already available at
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] Verified checksum of previously downloaded file
[INFO] Extracting tar contents (via spawned process)
[INFO] Error extracting archive
[INFO] Phantom installation failed { Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] killed: false,
[INFO] code: 2,
[INFO] signal: null,
[INFO] cmd: 'tar jxf /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2' }
Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] npm WARN security-admin@2.0.0 No description
[INFO] npm WARN security-admin@2.0.0 No repository field.
[INFO] npm WARN security-admin@2.0.0 No license field.
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4
(node_modules/fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 1
[INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node install.js`
[INFO] npm ERR! Exit status 1
[INFO] npm ERR!
[INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16 install script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.
[INFO]
[INFO] npm ERR! A complete log of this run can be found in:
[INFO] npm ERR! /root/.npm/_logs/2023-11-28T07_05_28_779Z-debug.log {code}
2. After understanding above error i installed bzip2 by executing the
[command|https://github.com/apache/ranger/blob/master/build_ranger_using_docker.sh#L69]
3. Executed "mvn clean install" again and it succeeded.
{code:java}
[INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @
security-admin-web ---
[INFO] Skipping because packaging 'war' is not pom.
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.7:report (jacoco-site) @ security-admin-web
---
[INFO] Loading execution data file
/root/ranger/security-admin/target/jacoco.exec
[INFO] Analyzed bundle 'Security Admin Web Application' with 671 classes
[INFO]
[INFO] --- frontend-maven-plugin:1.12.1:karma (karma prd) @ security-admin-web
---
[INFO] Running 'karma start ../../src/test/javascript/karma-prd.conf.js' in
/root/ranger/security-admin/target/jstest
[INFO] 28 11 2023 06:32:51.840:INFO [karma-server]: Karma v3.1.4 server started
at http://0.0.0.0:9877/
[INFO] 28 11 2023 06:32:51.842:INFO [launcher]: Launching browsers PhantomJS
with concurrency unlimited
[INFO] 28 11 2023 06:32:51.863:INFO [launcher]: Starting browser PhantomJS
[INFO] 28 11 2023 06:32:51.951:ERROR [phantomjs.launcher]: Fontconfig warning:
ignoring UTF-8: not a valid region tag
[INFO]
[INFO] 28 11 2023 06:32:52.079:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected
on socket MuRdJUviuc4-IMkX with id 77739149
LOG: 'just
[jira] [Comment Edited] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790402#comment-17790402
]
Pradeep Agrawal edited comment on RANGER-4562 at 11/28/23 7:29 AM:
---
Without docker case :
1. I tried "mvn clean install" command on a fresh jdk11 cluster and i was able
to reproduce the issue with following error
{code:java}
[INFO] --- frontend-maven-plugin:1.12.1:npm (npm install for tests) @
security-admin-web ---
[INFO] Running 'npm install' in /root/ranger/security-admin/target/jstest
[INFO]
[INFO] > phantomjs-prebuilt@2.1.16 install
/root/ranger/security-admin/target/jstest/node_modules/phantomjs-prebuilt
[INFO] > node install.js
[INFO]
[INFO] PhantomJS not found on PATH
[INFO] Download already available at
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] Verified checksum of previously downloaded file
[INFO] Extracting tar contents (via spawned process)
[INFO] Error extracting archive
[INFO] Phantom installation failed { Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] killed: false,
[INFO] code: 2,
[INFO] signal: null,
[INFO] cmd: 'tar jxf /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2' }
Error: Command failed: tar jxf
/tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
[INFO] tar (child): bzip2: Cannot exec: No such file or directory
[INFO] tar (child): Error is not recoverable: exiting now
[INFO] tar: Child returned status 2
[INFO] tar: Error is not recoverable: exiting now
[INFO]
[INFO] at ChildProcess.exithandler (child_process.js:276:12)
[INFO] at emitTwo (events.js:126:13)
[INFO] at ChildProcess.emit (events.js:214:7)
[INFO] at maybeClose (internal/child_process.js:915:16)
[INFO] at Socket.stream.socket.on (internal/child_process.js:336:11)
[INFO] at emitOne (events.js:116:13)
[INFO] at Socket.emit (events.js:211:7)
[INFO] at Pipe._handle.close [as _onclose] (net.js:561:12)
[INFO] npm WARN security-admin@2.0.0 No description
[INFO] npm WARN security-admin@2.0.0 No repository field.
[INFO] npm WARN security-admin@2.0.0 No license field.
[INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4
(node_modules/fsevents):
[INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current:
{"os":"linux","arch":"x64"})
[INFO]
[INFO] npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 1
[INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node install.js`
[INFO] npm ERR! Exit status 1
[INFO] npm ERR!
[INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16 install script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.
[INFO]
[INFO] npm ERR! A complete log of this run can be found in:
[INFO] npm ERR! /root/.npm/_logs/2023-11-28T07_05_28_779Z-debug.log {code}
2. After understanding above error i installed bzip2 by executing the
[command|https://github.com/apache/ranger/blob/master/build_ranger_using_docker.sh#L69]
3. Executed "mvn clean install" again and it succeeded.
{code:java}
[INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @
security-admin-web ---
[INFO] Skipping because packaging 'war' is not pom.
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.7:report (jacoco-site) @ security-admin-web
---
[INFO] Loading execution data file
/root/ranger/security-admin/target/jacoco.exec
[INFO] Analyzed bundle 'Security Admin Web Application' with 671 classes
[INFO]
[INFO] --- frontend-maven-plugin:1.12.1:karma (karma prd) @ security-admin-web
---
[INFO] Running 'karma start ../../src/test/javascript/karma-prd.conf.js' in
/root/ranger/security-admin/target/jstest
[INFO] 28 11 2023 06:32:51.840:INFO [karma-server]: Karma v3.1.4 server started
at http://0.0.0.0:9877/
[INFO] 28 11 2023 06:32:51.842:INFO [launcher]: Launching browsers PhantomJS
with concurrency unlimited
[INFO] 28 11 2023 06:32:51.863:INFO [launcher]: Starting browser PhantomJS
[INFO] 28 11 2023 06:32:51.951:ERROR [phantomjs.launcher]: Fontconfig warning:
ignoring UTF-8: not a valid region tag
[INFO]
[INFO] 28 11 2023 06:32:52.079:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected
on socket
[jira] [Comment Edited] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790183#comment-17790183
]
Pradeep Agrawal edited comment on RANGER-4562 at 11/27/23 5:14 PM:
---
[~madhan]
Can you try with version
[1.11.3|https://mvnrepository.com/artifact/com.github.eirslett/frontend-maven-plugin/1.11.3]
here in security-admin/pom.xml file
[https://github.com/apache/ranger/blob/master/security-admin/pom.xml#L1043]
was (Author: pradeep.agrawal):
[~madhan]
Can you try with version 1.11.3 here in security-admin/pom.xml file
[https://github.com/apache/ranger/blob/master/security-admin/pom.xml#L1043]
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790183#comment-17790183
]
Pradeep Agrawal commented on RANGER-4562:
-
[~madhan]
Can you try with version 1.11.3 here in security-admin/pom.xml file
[https://github.com/apache/ranger/blob/master/security-admin/pom.xml#L1043]
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4562) Build fails in security-admin test while installing npm
[
https://issues.apache.org/jira/browse/RANGER-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790098#comment-17790098
]
Pradeep Agrawal commented on RANGER-4562:
-
[~madhan] :
Are you planning to build Ranger with trino plugin. It seems
[commit|https://github.com/apache/ranger/commit/c51bc9fad8b0897c067dd9c392709120fd87265e]
introduced ranger-jdk11 profile.
or
If you are planning to build Ranger with jdk11 only(without trino) then can you
run your command without "-Pranger-jdk11" option and post the error if any.
> Build fails in security-admin test while installing npm
> ---
>
> Key: RANGER-4562
> URL: https://issues.apache.org/jira/browse/RANGER-4562
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Build using {{mvn -Pranger-jdk11 -DskipTests=false clean compile package}}
> fails in security-admin module while installing npm:
>
> {noformat}
> ranger-build| [INFO]
> ranger-build| [INFO] --- frontend-maven-plugin:1.12.1:npm (npm install
> for tests) @ security-admin-web ---
> ranger-build| [INFO] Running 'npm install' in
> /home/ranger/src/security-admin/target/jstest
> ranger-build| [INFO]
> ranger-build| [INFO] > phantomjs-prebuilt@2.1.16 install
> /home/ranger/src/security-admin/target/jstest/node_modules/phantomjs-prebuilt
> ranger-build| [INFO] > node install.js
> ranger-build| [INFO]
> ranger-build| [INFO] PhantomJS not found on PATH
> ranger-build| [INFO] Downloading
> https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Saving to
> /tmp/phantomjs/phantomjs-2.1.1-linux-x86_64.tar.bz2
> ranger-build| [INFO] Receiving...
> ranger-build| [INFO]
> ranger-build| [INFO] Error making request.
> ranger-build| [INFO] Error: connect ETIMEDOUT 185.199.108.133:443
> ranger-build| [INFO] at TCPConnectWrap.afterConnect [as oncomplete]
> (net.js:1191:14)
> ranger-build| [INFO]
> ranger-build| [INFO] Please report this full log at
> https://github.com/Medium/phantomjs
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No description
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No repository field.
> ranger-build| [INFO] npm WARN security-admin@2.0.0 No license field.
> ranger-build| [INFO] npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
> fsevents@1.2.4 (node_modules/fsevents):
> ranger-build| [INFO] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY:
> Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"}
> (current: {"os":"linux","arch":"x64"})
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! code ELIFECYCLE
> ranger-build| [INFO] npm ERR! errno 1
> ranger-build| [INFO] npm ERR! phantomjs-prebuilt@2.1.16 install: `node
> install.js`
> ranger-build| [INFO] npm ERR! Exit status 1
> ranger-build| [INFO] npm ERR!
> ranger-build| [INFO] npm ERR! Failed at the phantomjs-prebuilt@2.1.16
> install script.
> ranger-build| [INFO] npm ERR! This is probably not a problem with npm.
> There is likely additional logging output above.
> ranger-build| [INFO]
> ranger-build| [INFO] npm ERR! A complete log of this run can be found in:
> ranger-build| [INFO] npm ERR!
> /home/ranger/.npm/_logs/2023-11-25T19_25_13_719Z-debug.log
> ranger-build| [INFO]
>
> {noformat}
> [~mugdha.varadkar], [~ankita], [~pradeep], [~mehul] - can you please help
> resolve this issue?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4555) Response metrics for /assets/assets API not proper
[
https://issues.apache.org/jira/browse/RANGER-4555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4555:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /assets/assets API not proper
> --
>
> Key: RANGER-4555
> URL: https://issues.apache.org/jira/browse/RANGER-4555
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to /assets/assets API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of assets (the
> value returned by /assets/assets/count API is proper).
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4547) The reponse metrics (pagination values) for the /assets/ugsyncAudits/{sync_source} API is not proper
[
https://issues.apache.org/jira/browse/RANGER-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4547:
---
Assignee: Pradeep Agrawal
> The reponse metrics (pagination values) for the
> /assets/ugsyncAudits/{sync_source} API is not proper
>
>
> Key: RANGER-4547
> URL: https://issues.apache.org/jira/browse/RANGER-4547
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the /assets/ugsyncAudits/\{sync_source} API,
> the metrics like total count, result size is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215450040,"vxUgsyncAuditInfoList": [{
> {code}
> Ideally, it should reflect the total number of audits.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4553) Response metrics for /xaudit/trx_log not proper
[
https://issues.apache.org/jira/browse/RANGER-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4553:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /xaudit/trx_log not proper
> ---
>
> Key: RANGER-4553
> URL: https://issues.apache.org/jira/browse/RANGER-4553
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to /xaudit/trx_log API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 200,"totalCount": 0,
> "resultSize": 0,"queryTimeMS": 1700214070565, ...} {code}
> Ideally, the total count value should reflect the total number of logs
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4554) Response metrics for /assets/resources not proper
[
https://issues.apache.org/jira/browse/RANGER-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4554:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /assets/resources not proper
> -
>
> Key: RANGER-4554
> URL: https://issues.apache.org/jira/browse/RANGER-4554
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to /assets/resources API, the values like total count,
> result size in the API response is always 0.
> {code:java}
> {"startIndex": 0,"pageSize": 0,"totalCount": 0,"resultSize":
> 0,"queryTimeMS": 1700215066880,{code}
> Ideally, the total count value should reflect the total number of resources
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4550) API request to /assets/resource/{id} returns no response
[
https://issues.apache.org/jira/browse/RANGER-4550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4550:
---
Assignee: Pradeep Agrawal
> API request to /assets/resource/{id} returns no response
>
>
> Key: RANGER-4550
> URL: https://issues.apache.org/jira/browse/RANGER-4550
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the API endpoint /assets/resource/\{id}, no
> response is returned and the status code is 204 No response.
> Ideally, the response should contain the details for the resource with the
> given id
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4549) Non admin users cannot access /public/v2/api/roles/names and /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
[
https://issues.apache.org/jira/browse/RANGER-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4549:
---
Assignee: Pradeep Agrawal
> Non admin users cannot access /public/v2/api/roles/names and
> /public/v2/api/roles/name/{name} API, but can access /public/v2/api/roles API
> ---
>
> Key: RANGER-4549
> URL: https://issues.apache.org/jira/browse/RANGER-4549
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> Non admin users cannot access /public/v2/api/roles/names API, but can access
> the /public/v2/api/roles API and fetch the details of all the roles.
> Since the users can fetch the details from the roles API itself, the
> restriction for non admin users to access /roles/names and
> /roles/name/\{name} API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4551) No response returned for /assets/policyList/{service_name} API
[
https://issues.apache.org/jira/browse/RANGER-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4551:
---
Assignee: Pradeep Agrawal
> No response returned for /assets/policyList/{service_name} API
> --
>
> Key: RANGER-4551
> URL: https://issues.apache.org/jira/browse/RANGER-4551
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the /assets/policyList/\{service_name} API,
> the response is empty and the status code is 304 Not Modified.
> If there is no expected response, then the API has to be deprecated,
> otherwise the API has to be fixed to return the proper response
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4548) Return proper error message in the response for /tags/tags, /tags/resources and /tags/types API for non admin users
[
https://issues.apache.org/jira/browse/RANGER-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4548:
---
Assignee: Pradeep Agrawal
> Return proper error message in the response for /tags/tags, /tags/resources
> and /tags/types API for non admin users
> ---
>
> Key: RANGER-4548
> URL: https://issues.apache.org/jira/browse/RANGER-4548
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> /tags/tags and /tags/types, /tags/resources APIs are not accessible by non
> admin users,
> but when the users make a request, a proper error message should be returned
> stating that the users do not have privilege.
> Currently, the error message returned is not explanatory.
> Response returned for non admin users :-
> {code:java}
>
> content="IE=edge,chrome=1"> Ranger - Sign In name="description" content=""> content="width=device-width"> href="images/favicon.ico"> media="all" rel="stylesheet" type="text/css" id="bootstrap-css"> rel="stylesheet" href="styles/font-awesome.min.css"> href="styles/xa.css" media="all" rel="stylesheet" type="text/css"> src="libs/bower/jquery/js/jquery-3.5.1.js"> src="scripts/prelogin/XAPrelogin.js"> type="text/javascript">$(document).ready(function() {
> var updateBoxPosition = function() {
> $('#signin-container').css({'margin-top' :
> ($(window).height() - $('#signin-container').height()) / 2
> });};$(window).resize(updateBoxPosition);
>var queryParams = JSON.parse('{"' +
> decodeURI((location.href.split('?')[1] || 'g=0').replace(/=/g, "\":\"")) +
> '"}');if(queryParams.sessionTimeout){
> window.alert('Session Timeout');
> location.replace("login.jsp");}
> setTimeout(updateBoxPosition, 50);});
>
> id="signin-container" style="margin-top: 4.5px;">
>
>
>
> Username:
>
> Password:
> tabindex="2" autocomplete="off">
> style="color:white;display:none;">
>
> id="errorBoxUnsynced" class="help-inline"
> style="color:white;display:none;">User is not available in HDP Admin Tool.
> Please contact your Administrator.
> Sign In
>style="display: none;">
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4552) Response metrics for /assets/report is not proper, and pagination does not work
[
https://issues.apache.org/jira/browse/RANGER-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal reassigned RANGER-4552:
---
Assignee: Pradeep Agrawal (was: Ramachandran)
> Response metrics for /assets/report is not proper, and pagination does not
> work
> ---
>
> Key: RANGER-4552
> URL: https://issues.apache.org/jira/browse/RANGER-4552
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Pradeep Agrawal
>Priority: Major
>
> When a request is made to the /assets/report API endpoint, the response
> metrics like
> result size is incorrect. Ideally, it should reflect the total number of
> objects returned
> {code:java}
> {"startIndex": 2,"pageSize": 100,"totalCount": 178,
> "resultSize": 0,"queryTimeMS": 1700217495822 {code}
> Even the pagination for the API does not work properly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
