Re: Review Request 74976: RANGER-4782: Implement best coding practices for validating service configs

/ServiceMgr.java Lines 200 (patched) <https://reviews.apache.org/r/74976/#comment314630> connection has not failed, rather you should ask use to provide a valid host as "localhost" or "127.0.0.1" is not allowed. - Pradeep Agrawal On May 8, 2024, 2:4

Re: Review Request 74958: RANGER-4775 : Ranger Kms is failing with oracle23 Database

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74958/#review226413 --- Ship it! Ship It! - Pradeep Agrawal On April 18, 2024, 8:57

[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

[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 > Upgr

Review Request 74944: RANGER-4753: Upgrade Spring Security to 5.7.12 and spring framework to 5.3.33

. Thanks, Pradeep Agrawal

[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

[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

[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

[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

[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

[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

[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 > Upgr

Review Request 74905: RANGER-4568: Upgrade Spring Security to 5.7.11 and spring framework to 5.3.32

Security version to 5.7.11 and spring framework version to 5.3.32 Diffs - pom.xml b40fbcc5a Diff: https://reviews.apache.org/r/74905/diff/1/ Testing --- Tested ranger admin installation, password change, CRUD operation on Ranger service, policy, users and group. Thanks, Pradeep

[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

[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

[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

[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

[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 Validat

[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 Tr

[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 plu

[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 checkCanSetTableAuthorizat

[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 runn

[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

[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 metad

[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-tr

[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 den

[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 JD

[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 success

[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

[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 Tr

[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 tab

[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

[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.

[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 tab

[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 plu

[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 plu

[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 vers

[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

[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 permiss

[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-n

[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.u

[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 r

[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 kerbe

[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

[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

[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 Permiss

[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

[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 ex

[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 Ran

Review Request 74862: RANGER-4689: Fix Ranger Javapatch failure even if service-defs do not exist in ranger DB

ipt and all the java patches applied without any failure. 5) restarted ranger-admin and able to see the ranger ui. Thanks, Pradeep Agrawal

[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

Re: Review Request 74763: RANGER-4607: Ranger REST API improvements

/apache/ranger/rest/TestXUserREST.java 74744e6cf Diff: https://reviews.apache.org/r/74763/diff/4/ Changes: https://reviews.apache.org/r/74763/diff/3-4/ Testing --- Tested affected REST APIs using curl command and found the response as per the expectation. Thanks, Pradeep Agrawal

Re: Review Request 74763: RANGER-4607: Ranger REST API improvements

/apache/ranger/rest/TestXUserREST.java 74744e6cf Diff: https://reviews.apache.org/r/74763/diff/3/ Changes: https://reviews.apache.org/r/74763/diff/2-3/ Testing --- Tested affected REST APIs using curl command and found the response as per the expectation. Thanks, Pradeep Agrawal

[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 u

[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 > Implem

[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 > /xau

[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 > Implem

[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 > /xau

[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 >

[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 > keyad

[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 > M

[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 >

[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 >

[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 > Respo

[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 > Implem

[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 > Implem

[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 > /xu

[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 >

Re: Review Request 74763: RANGER-4607: Ranger REST API improvements

the expectation. Thanks, Pradeep Agrawal

[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

Re: Review Request 74782: RANGER-4600: Add improvement for /xaudit/access_audit API based on user role

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74782/#review226072 --- Ship it! Ship It! - Pradeep Agrawal On Dec. 12, 2023, 10:31

Re: Review Request 74752: RANGER-4543 : Add flink service user to default audit filters, and add spark3 path for default audit filters in HDFS

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74752/#review226071 --- Ship it! Ship It! - Pradeep Agrawal On Nov. 22, 2023, 12:14

Re: Review Request 74780: RANGER-4564: DELETE /groupsgroups/{id} API doesn't work as forceDelete is hardcoded to false

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74780/#review226070 --- Ship it! Ship It! - Pradeep Agrawal On Dec. 11, 2023, 4:10

Re: Review Request 74791: RANGER-4606 /assets/assets/count API does not return the proper count if the number of services is greater than 200

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74791/#review226068 --- Ship it! Ship It! - Pradeep Agrawal On Dec. 14, 2023, 4:24

Re: Review Request 74792: RANGER-4605: /assets/resources/count does not return proper count if policies are greater than 200

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74792/#review226067 --- Ship it! Ship It! - Pradeep Agrawal On Dec. 14, 2023, 4:41

Re: Review Request 74784: RANGER-4601: /xaudit/access_audit/count API does not return the proper value

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74784/#review226069 --- Ship it! Ship It! - Pradeep Agrawal On Dec. 12, 2023, 11:46

Re: Review Request 74657: RANGER-4467: User Agent info not logged under "Login sessions" when login fails

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74657/#review226058 --- Ship it! Ship It! - Pradeep Agrawal On Oct. 10, 2023, 11:03

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

Review Request 74763: RANGER-4545 To RANGER-4555 : Improve Ranger REST API response code, messages and response summary

/diff/1/ Testing --- Tested affected REST APIs using curl command and found the response as per the expectation. Thanks, Pradeep Agrawal

[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 > Respo

[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 > Respo

[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 > Respo

[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 > Respo

[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 respo

[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 requ

[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 > Ret

[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 > /ass

[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 ad

  1   2   3   4   5   6   7   8   9   10   >