[jira] [Updated] (RANGER-3973) LDAP incremental search not always available
[ https://issues.apache.org/jira/browse/RANGER-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonas Hartwig updated RANGER-3973: -- Fix Version/s: 2.4.0 Affects Version/s: 2.3.0 (was: 2.4.0) > LDAP incremental search not always available > > > Key: RANGER-3973 > URL: https://issues.apache.org/jira/browse/RANGER-3973 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.3.0 >Reporter: Jonas Hartwig >Priority: Blocker > Fix For: 2.4.0 > > > In certain situations the LDAP incremental user/groups search is not > available. There is a feature already to disable incremental loads. This is a > request to add a feature to disable using the delta fields for lookup. Our > LDAP does not have modifyTimestamp field. > When the flag ranger.usersync.ldap.deltasync is set ldap search should not > use properties > uSNChanged and modifyTimestamp (they are not needed). -- 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 ] Jonas Hartwig updated RANGER-3985: -- Description: The ranger rules to create tables in Trino only check data base level on create. They should check by table name as well. It easily get inconsistent, if users or groups are allowed to read, drop and alter certain tables like t__* but may create any. (was: The ranger rules to create tables in Trino only check data base level on create. They should check by table name as well.) > 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 > Fix For: 2.4.0 > > > The ranger rules to create tables in Trino only check data base level on > create. They should check by table name as well. It easily get inconsistent, > if users or groups are allowed to read, drop and alter certain tables like > t__* but may create any. -- 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 ] Jonas Hartwig updated RANGER-3985: -- Fix Version/s: 2.4.0 (was: 3.0.0) Description: The ranger rules to create tables in Trino only check data base level on create. They should check by table name as well. (was: 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) > 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 > Fix For: 2.4.0 > > > The ranger rules to create tables in Trino only check data base level on > create. They should check by table name as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-3985) Trino plugin: Check table name when creating tables
Jonas Hartwig created RANGER-3985: - Summary: 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 Fix For: 3.0.0 >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] [Created] (RANGER-3984) Support using TiDB as mysql-db in ranger
kirby zhou created RANGER-3984:
--
Summary: Support using TiDB as mysql-db in ranger
Key: RANGER-3984
URL: https://issues.apache.org/jira/browse/RANGER-3984
Project: Ranger
Issue Type: Improvement
Components: admin, kms
Affects Versions: 2.3.0, 3.0.0
Reporter: kirby zhou
TiDB is a 95% mysql-compatible NewSQL database. For legal reason, we have to
deploy ranger based on tidb. But TiDB is missing some features, which makes
ranger unable to install properly.
[https://docs.pingcap.com/tidb/stable/mysql-compatibility#unsupported-features]
The biggest problem affecting ranger is missing "Stored procedures and
functions".
ranger use Stored procedures in setup scripts to simplify SQL.
Some work is needed to remove the stored procedure.
{code:java}
ERROR 1064 (42000) at line 1595 in file: 'ranger_core_db_mysql.sql': You have
an error in your SQL syntax; check the manual that corresponds to your TiDB
version for the right syntax to use line 1 column 14 near "PROCEDURE if exists
getXportalUIdByLoginId"
ERROR 1064 (42000) at line 1596 in file: 'ranger_core_db_mysql.sql': You have
an error in your SQL syntax; check the manual that corresponds to your TiDB
version for the right syntax to use line 1 column 16 near "PROCEDURE
`getXportalUIdByLoginId`(IN input_val VARCHAR(100), OUT myid BIGINT)
BEGIN
SET myid = 0;
SELECT x_portal_user.id into myid FROM x_portal_user WHERE
x_portal_user.login_id = input_val;
END"
ERROR 1064 (42000) at line 1605 in file: 'ranger_core_db_mysql.sql': You have
an error in your SQL syntax; check the manual that corresponds to your TiDB
version for the right syntax to use line 1 column 14 near "PROCEDURE if exists
getModulesIdByName"
ERROR 1064 (42000) at line 1606 in file: 'ranger_core_db_mysql.sql': You have
an error in your SQL syntax; check the manual that corresponds to your TiDB
version for the right syntax to use line 1 column 16 near "PROCEDURE
`getModulesIdByName`(IN input_val VARCHAR(100), OUT myid BIGINT)
BEGIN
SET myid = 0;
SELECT x_modules_master.id into myid FROM x_modules_master WHERE
x_modules_master.module = input_val;
END"
ERROR 1064 (42000) at line 1679 in file: 'ranger_core_db_mysql.sql': You have
an error in your SQL syntax; check the manual that corresponds to your TiDB
version for the right syntax to use line 1 column 14 near "PROCEDURE if exists
insertRangerPrerequisiteEntries"
ERROR 1064 (42000) at line 1680 in file: 'ranger_core_db_mysql.sql': You have
an error in your SQL syntax; check the manual that corresponds to your TiDB
version for the right syntax to use line 1 column 16 near "PROCEDURE
`insertRangerPrerequisiteEntries`()
BEGIN
DECLARE adminID bigint;
DECLARE keyadminID bigint;
DECLARE rangerusersyncID bigint;
DECLARE rangertagsyncID bigint;
DECLARE moduleIdReports bigint;
DECLARE moduleIdResourceBasedPolicies bigint;
DECLARE moduleIdAudit bigint;
DECLARE moduleIdUG bigint;
DECLARE moduleIdTagBasedPolicies bigint;
DECLARE moduleIdKeyMana
ERROR 8108 (HY000) at line 1757 in file: 'ranger_core_db_mysql.sql':
Unsupported type *ast.CallStmt
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: Review Request 74215: RANGER-3976:Upgrade tomcat version to 8.5.83
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74215/#review224907 --- Ship it! Ship It! - Vishal Suvagia On Nov. 24, 2022, 3:07 a.m., bhavik patel wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74215/ > --- > > (Updated Nov. 24, 2022, 3:07 a.m.) > > > Review request for ranger. > > > Bugs: RANGER-3976 > https://issues.apache.org/jira/browse/RANGER-3976 > > > Repository: ranger > > > Description > --- > > Upgrade tomcat version to 8.5.83 > > > Diffs > - > > pom.xml bcb93ed74 > > > Diff: https://reviews.apache.org/r/74215/diff/1/ > > > Testing > --- > > 1. Junit passed. > 2. verified policy and user crud operations. > > > Thanks, > > bhavik patel > >
Re: Review Request 74210: RANGER-3974:Upgrade jackson version to 2.14.0
> On Nov. 24, 2022, 5:04 a.m., Pradeep Agrawal wrote: > > Can you confirm ranger-kms is working or not ? Able to perform keys operations - bhavik --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74210/#review224903 --- On Nov. 24, 2022, 2:59 a.m., bhavik patel wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74210/ > --- > > (Updated Nov. 24, 2022, 2:59 a.m.) > > > Review request for ranger. > > > Bugs: RANGER-3974 > https://issues.apache.org/jira/browse/RANGER-3974 > > > Repository: ranger > > > Description > --- > > Upgrade jackson version to 2.14.0 > > > Diffs > - > > pom.xml 44eef2a0ceba17d20bee69e441e7c05a90a53ae8 > > > Diff: https://reviews.apache.org/r/74210/diff/1/ > > > Testing > --- > > successfully able to build the package and Junit passed. > > Verified Policy and User CRUD Operations. > > > Thanks, > > bhavik patel > >
Re: Review Request 74214: RANGER-3978: Docker setup for Ranger KMS
> On Nov. 25, 2022, 2:01 a.m., Ramesh Mani wrote: > > Ship It! Verified docker setup and all services including KMS came up. - Ramesh --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74214/#review224904 --- On Nov. 23, 2022, 10 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74214/ > --- > > (Updated Nov. 23, 2022, 10 p.m.) > > > Review request for ranger, Abhishek Kumar, Kishor Gollapalliwar, Abhay > Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and > Velmurugan Periasamy. > > > Bugs: RANGER-3978 > https://issues.apache.org/jira/browse/RANGER-3978 > > > Repository: ranger > > > Description > --- > > updated docker setup to install and run Ranger KMS > > > Diffs > - > > dev-support/ranger-docker/.dockerignore 282c456d8 > dev-support/ranger-docker/Dockerfile.ranger-kms PRE-CREATION > dev-support/ranger-docker/docker-compose.ranger-kms.yml PRE-CREATION > dev-support/ranger-docker/scripts/create-ranger-services.py f329d1f29 > dev-support/ranger-docker/scripts/ranger-kms-install-mysql.properties > PRE-CREATION > dev-support/ranger-docker/scripts/ranger-kms-install-postgres.properties > PRE-CREATION > dev-support/ranger-docker/scripts/ranger-kms.sh PRE-CREATION > > > Diff: https://reviews.apache.org/r/74214/diff/1/ > > > Testing > --- > > - verified Ranger KMS is setup and runs with Postgres database > > > Thanks, > > Madhan Neethiraj > >
Re: Review Request 74214: RANGER-3978: Docker setup for Ranger KMS
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74214/#review224904 --- Ship it! Ship It! - Ramesh Mani On Nov. 23, 2022, 10 p.m., Madhan Neethiraj wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74214/ > --- > > (Updated Nov. 23, 2022, 10 p.m.) > > > Review request for ranger, Abhishek Kumar, Kishor Gollapalliwar, Abhay > Kulkarni, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and > Velmurugan Periasamy. > > > Bugs: RANGER-3978 > https://issues.apache.org/jira/browse/RANGER-3978 > > > Repository: ranger > > > Description > --- > > updated docker setup to install and run Ranger KMS > > > Diffs > - > > dev-support/ranger-docker/.dockerignore 282c456d8 > dev-support/ranger-docker/Dockerfile.ranger-kms PRE-CREATION > dev-support/ranger-docker/docker-compose.ranger-kms.yml PRE-CREATION > dev-support/ranger-docker/scripts/create-ranger-services.py f329d1f29 > dev-support/ranger-docker/scripts/ranger-kms-install-mysql.properties > PRE-CREATION > dev-support/ranger-docker/scripts/ranger-kms-install-postgres.properties > PRE-CREATION > dev-support/ranger-docker/scripts/ranger-kms.sh PRE-CREATION > > > Diff: https://reviews.apache.org/r/74214/diff/1/ > > > Testing > --- > > - verified Ranger KMS is setup and runs with Postgres database > > > Thanks, > > Madhan Neethiraj > >
[jira] [Updated] (RANGER-3982) Python client for Ranger KMS REST APIs
[ https://issues.apache.org/jira/browse/RANGER-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-3982: - Attachment: RANGER-3982-1.patch > Python client for Ranger KMS REST APIs > -- > > Key: RANGER-3982 > URL: https://issues.apache.org/jira/browse/RANGER-3982 > Project: Ranger > Issue Type: Improvement > Components: intg, kms >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.4.0 > > Attachments: RANGER-3982-1.patch, RANGER-3982.patch > > > This Jira tracks enhancement of Python client for Ranger to support Ranger > KMS REST APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74216: RANGER-3982: updated Python client to support Ranger KMS REST APIs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74216/ --- (Updated Nov. 24, 2022, 8:28 p.m.) Review request for ranger, Abhishek Kumar, Ankita Sinha, deepak sharma, Dhaval Shah, Kishor Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Monika Kachhadiya, Ramesh Mani, Siddhesh Phatak, Sailaja Polavarapu, Subhrat Chaudhary, and Velmurugan Periasamy. Changes --- - replaced RangerKMSClientHttp class with RangerClientHttp, to eliminate duplicate code Bugs: RANGER-3982 https://issues.apache.org/jira/browse/RANGER-3982 Repository: ranger Description --- - added classes RangerKMSClient, RangerKey, RangerKeyVersion, RangerKeyMetadata and RangerEncryptedKeyVersion - updated README.md with sample calls for each KMS API Diffs (updated) - intg/src/main/python/README.md f21628fb0 intg/src/main/python/apache_ranger/client/ranger_client.py 7bb6493a1 intg/src/main/python/apache_ranger/client/ranger_kms_client.py PRE-CREATION intg/src/main/python/apache_ranger/exceptions.py a2299479c intg/src/main/python/apache_ranger/model/ranger_base.py 83ec44dd4 intg/src/main/python/apache_ranger/model/ranger_kms.py PRE-CREATION intg/src/main/python/apache_ranger/utils.py b0ceb5c59 intg/src/main/python/setup.py 8ea476320 Diff: https://reviews.apache.org/r/74216/diff/2/ Changes: https://reviews.apache.org/r/74216/diff/1-2/ Testing (updated) --- - verified KMS API calls using test_ranger_kms.py (in README.md) - test Apache Ranger Python client (0.0.19) that includes this patch is available at https://test.pypi.org/project/apache-ranger/ Thanks, Madhan Neethiraj
[jira] [Commented] (RANGER-217) Add LDAPS support / fix incorrectly returning Bad Credentials for connection problem
[
https://issues.apache.org/jira/browse/RANGER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638351#comment-17638351
]
Ganesh Tripathi commented on RANGER-217:
Probably unselect starttls property will resolve this issue
> Add LDAPS support / fix incorrectly returning Bad Credentials for connection
> problem
>
>
> Key: RANGER-217
> URL: https://issues.apache.org/jira/browse/RANGER-217
> Project: Ranger
> Issue Type: Bug
> Components: documentation
>Affects Versions: 0.4.0
> Environment: HDP 2.2
>Reporter: Hari Sekhon
>Assignee: Velmurugan Periasamy
>Priority: Major
>
> When configuring ranger-admin to use LDAPS it seems to not be supported or
> breaks with incorrect error.
> In install.properties
> {code}xa_ldap_url="ldaps://host.domain.com:636"{code}
> While attempting to log in to ranger admin web ui,
> /var/log/ranger/admin/xa_portal.log shows: {code}2015-01-13 15:54:34,522
> [http-bio-6080-exec-3] INFO
> com.xasecure.security.listener.SpringEventListener
> (SpringEventListener.java:87) - Login Unsuccessful:hari | Ip Address:x.x.x.x
> | Bad Credentials
> {code} I could understand if this is because my LDAPS server uses a
> self-signed cert and I need to supply a trusted CA cert but I can't see any
> setting for that or find any documentation around Apache Ranger LDAPS. (I use
> this LDAPS server with trusted CA cert elsewhere so I know it works)
> That Bad Credentials error is clearly wrong because redeploying ranger-admin
> using straight LDAP allows login to succeed with the same password:
> {code}xa_ldap_url="ldap://host.domain.com:389"{code}
> However it's insecure to only work with plain LDAP.
> Required fixes:
> 1. Add LDAPS support + document
> 2. Fix error message to be accurate to the problem and not always report Bad
> Credentials as this will confuse users
> Regards,
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (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:comment-tabpanel=17638314#comment-17638314 ] ziyue commented on RANGER-3983: --- https://github.com/apache/ranger/pull/190 > 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 > 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)
[GitHub] [ranger] ttzztztz opened a new pull request, #190: [RANGER-3983] Support getColumnMasks and getRowFilters in Trino SPI 376+
ttzztztz opened a new pull request, #190: URL: https://github.com/apache/ranger/pull/190 - https://github.com/trinodb/trino/commit/827de57a50426e804761044d24d96b8877b62b7e - https://issues.apache.org/jira/browse/RANGER-3983 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 is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (RANGER-3983) Support getColumnMasks and getRowFilters in Trino SPI 376+
ziyue created RANGER-3983: - Summary: 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 [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)
Review Request 74217: RANGER-3981:Upgrade jetty-client version to 9.4.49.v20220914
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74217/ --- Review request for ranger. Bugs: RANGER-3981 https://issues.apache.org/jira/browse/RANGER-3981 Repository: ranger Description --- Upgrade jetty-client version to 9.4.49.v20220914 Diffs - pom.xml bcb93ed74 Diff: https://reviews.apache.org/r/74217/diff/1/ Testing --- 1. Passed junit tests. 2. Verified policy and user crude operations. 3. created keys in kms. Thanks, bhavik patel
[jira] [Updated] (RANGER-3981) Upgrade jetty-client version to "9.4.49.v20220914"
[ https://issues.apache.org/jira/browse/RANGER-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavik Patel updated RANGER-3981: - Attachment: 0001-RANGER-3981-Upgrade-jetty-client-version-to-9.4.49.v.patch > Upgrade jetty-client version to "9.4.49.v20220914" > -- > > Key: RANGER-3981 > URL: https://issues.apache.org/jira/browse/RANGER-3981 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Bhavik Patel >Assignee: Bhavik Patel >Priority: Major > Attachments: > 0001-RANGER-3981-Upgrade-jetty-client-version-to-9.4.49.v.patch > > > Upgrade jetty-client version to "9.4.49.v20220914" -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-3982) Python client for Ranger KMS REST APIs
[ https://issues.apache.org/jira/browse/RANGER-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhan Neethiraj updated RANGER-3982: - Attachment: RANGER-3982.patch > Python client for Ranger KMS REST APIs > -- > > Key: RANGER-3982 > URL: https://issues.apache.org/jira/browse/RANGER-3982 > Project: Ranger > Issue Type: Improvement > Components: intg, kms >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Attachments: RANGER-3982.patch > > > This Jira tracks enhancement of Python client for Ranger to support Ranger > KMS REST APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74216: RANGER-3982: updated Python client to support Ranger KMS REST APIs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74216/ --- Review request for ranger, Abhishek Kumar, deepak sharma, Dhaval Shah, Kishor Gollapalliwar, Abhay Kulkarni, Mehul Parikh, Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy. Bugs: RANGER-3982 https://issues.apache.org/jira/browse/RANGER-3982 Repository: ranger Description --- - added classes RangerKMSClient, RangerKey, RangerKeyVersion, RangerKeyMetadata and RangerEncryptedKeyVersion - updated README.md with sample calls for each KMS API Diffs - intg/src/main/python/README.md f21628fb0 intg/src/main/python/apache_ranger/client/ranger_kms_client.py PRE-CREATION intg/src/main/python/apache_ranger/exceptions.py a2299479c intg/src/main/python/apache_ranger/model/ranger_base.py 83ec44dd4 intg/src/main/python/apache_ranger/model/ranger_kms.py PRE-CREATION intg/src/main/python/apache_ranger/utils.py b0ceb5c59 intg/src/main/python/setup.py 8ea476320 Diff: https://reviews.apache.org/r/74216/diff/1/ Testing --- - verified KMS API calls using test_ranger_kms.py (in README.md) - test Apache Ranger Python client (0.0.18) that includes this patch is available at https://test.pypi.org/project/apache-ranger/ Thanks, Madhan Neethiraj
[jira] [Created] (RANGER-3982) Python client for Ranger KMS REST APIs
Madhan Neethiraj created RANGER-3982: Summary: Python client for Ranger KMS REST APIs Key: RANGER-3982 URL: https://issues.apache.org/jira/browse/RANGER-3982 Project: Ranger Issue Type: Improvement Components: intg, kms Reporter: Madhan Neethiraj Assignee: Madhan Neethiraj This Jira tracks enhancement of Python client for Ranger to support Ranger KMS REST APIs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-3981) Upgrade jetty-client version to "9.4.49.v20220914"
Bhavik Patel created RANGER-3981: Summary: Upgrade jetty-client version to "9.4.49.v20220914" Key: RANGER-3981 URL: https://issues.apache.org/jira/browse/RANGER-3981 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Bhavik Patel Assignee: Bhavik Patel Upgrade jetty-client version to "9.4.49.v20220914" -- This message was sent by Atlassian Jira (v8.20.10#820010)
