Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Lal, Alok]

+1

From: Nixon Rodrigues 
Date: Tuesday, March 28, 2023 at 9:24 PM
To: dev@ranger.apache.org 
Subject: Re: [VOTE] Apache Ranger 2.4.0 Release - rc2
External Email

+1 Apache Ranger 2.4.0 - rc2 release.

Thanks & Regards
Nixon

On Wed, 29 Mar 2023 at 07:43, Balaji Ganesan 
wrote:

> +1
>
> On Tue, Mar 28, 2023 at 7:46 AM Ramesh Mani  wrote:
>
> > +1 for Apache Ranger 2.4.0 rc2
> >
> > - Build from the source
> >
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Franger%2F2.4.0-rc2%2Fapache-ranger-2.4.0.tar.gz=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2BxbBgt52Rg3vkrd%2FV5ZpPG6u%2BWkOsf%2FPHzd9%2Bxymni8%3D=0
> > file was
> > successful.
> > - Verified some of the source code in tar files built.
> > - Verified PGP signature.
> > - Verified SHA256 / 512 hash.
> >
> > Thank you Selva for Apache Ranger 2.4.0 release candidate #2
> >
> > Thanks,
> > Ramesh
> >
> > On Mon, Mar 27, 2023 at 8:41 PM Selvamohan Neethiraj <
> sneet...@apache.org>
> > wrote:
> >
> > > Rangers:
> > >
> > > Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> > > within the dev community.
> > > Links to the release artifacts are given below. Please review and vote.
> > >
> > > The vote will be open for at least 72 hours or until necessary votes
> are
> > > reached.
> > > [   ] +1 approve
> > > [   ] +0 no opinion
> > > [   ] -1 disapprove (and reason why)
> > >
> > > Thanks,
> > > Selva-
> > > Ranger PMC
> > >
> > > List of issues / improvements addressed in this release:  click-here <
> > >
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FRANGER-4154%3Fjql%3Dproject%3DRANGER%2520and%2520fixVersion%2520%2520%3D%25202.4.0%2520and%2520status%2520%3D%2520Resolved%2520ORDER%2520BY%2520key%2520desc=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=H42RhUWcfSS4LRu2skKK9Rt8paoyI1YhqTfbOd28Sis%3D=0
> > > >
> > >
> > > Git tag for the release:
> > > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Franger%2Ftree%2Frelease-2.4.0-rc2=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=c22lMDnnCju4IwyVdGGJaUDvA2PVj33m44Eg2iRuJ8M%3D=0
> > > Sources for the release:
> > >
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Franger%2F2.4.0-rc2%2Fapache-ranger-2.4.0.tar.gz=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2BxbBgt52Rg3vkrd%2FV5ZpPG6u%2BWkOsf%2FPHzd9%2Bxymni8%3D=0
> > >
> > > Source release verification:
> > > PGP Signature:
> > >
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Franger%2F2.4.0-rc2%2Fapache-ranger-2.4.0.tar.gz.asc=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=5jH%2Fk3%2Fw50JTnAS8e2wgtmXGIFrs%2FHUA3NdRWlVOwME%3D=0
> > > SHA256
> > > <
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Franger%2F2.4.0-rc2%2Fapache-ranger-2.4.0.tar.gz.ascSHA256=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=PwhcCLghs2DU6XT4gnRy3UHIrxyS4qAP1FB4CspOBX0%3D=0
> > >
> > > Hash:
> > >
> >
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Franger%2F2.4.0-rc2%2Fapache-ranger-2.4.0.tar.gz.sha256=05%7C01%7Callal%40ebay.com%7C254226ed78094cb90e0008db300d6f10%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C638156606761905173%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=m5lrRE6MUfPuik8pPg5JGQjcMMxJTu6hd2Bok%2FeZzJE%3D=0
> > > SHA512
> > > <
> >
> 

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Mehul Parikh]

+1 for Apache Ranger 2.4.0 rc2 release.

- Verified successful build .
- Verified PGP signature.
- Verified SHA256 / 512 hash.
- Verified CRUD operations of services, policies, security zones.


Thanks & Regards,
Mehul Parikh



On Wed, Mar 29, 2023 at 9:54 AM Nixon Rodrigues  wrote:

> +1 Apache Ranger 2.4.0 - rc2 release.
>
> Thanks & Regards
> Nixon
>
> On Wed, 29 Mar 2023 at 07:43, Balaji Ganesan 
> wrote:
>
> > +1
> >
> > On Tue, Mar 28, 2023 at 7:46 AM Ramesh Mani  wrote:
> >
> > > +1 for Apache Ranger 2.4.0 rc2
> > >
> > > - Build from the source
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> > > file was
> > > successful.
> > > - Verified some of the source code in tar files built.
> > > - Verified PGP signature.
> > > - Verified SHA256 / 512 hash.
> > >
> > > Thank you Selva for Apache Ranger 2.4.0 release candidate #2
> > >
> > > Thanks,
> > > Ramesh
> > >
> > > On Mon, Mar 27, 2023 at 8:41 PM Selvamohan Neethiraj <
> > sneet...@apache.org>
> > > wrote:
> > >
> > > > Rangers:
> > > >
> > > > Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> > > > within the dev community.
> > > > Links to the release artifacts are given below. Please review and
> vote.
> > > >
> > > > The vote will be open for at least 72 hours or until necessary votes
> > are
> > > > reached.
> > > > [   ] +1 approve
> > > > [   ] +0 no opinion
> > > > [   ] -1 disapprove (and reason why)
> > > >
> > > > Thanks,
> > > > Selva-
> > > > Ranger PMC
> > > >
> > > > List of issues / improvements addressed in this release:  click-here
> <
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/RANGER-4154?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20ORDER%20BY%20key%20desc
> > > > >
> > > >
> > > > Git tag for the release:
> > > > https://github.com/apache/ranger/tree/release-2.4.0-rc2
> > > > Sources for the release:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> > > >
> > > > Source release verification:
> > > > PGP Signature:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> > > > SHA256
> > > > <
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.ascSHA256
> > > >
> > > > Hash:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> > > > SHA512
> > > > <
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256SHA512
> > > >
> > > > Hash:
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
> > > >
> > > > Keys to verify the signature:
> > > > https://dist.apache.org/repos/dist/release/ranger/KEYS
> > > >
> > > > Click Here <
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20and%20type%20in%20(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc
> > > >
> > > > to view New Features/Enhancements in this release.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
>


-- 

Thanks and regards,
Mehul Parikh

M: +91 98191 54446
E: xsme...@gmail.com

[jira] [Commented] (RANGER-2894) Plugins cannot interact with Solr with basic auth as audit targer

[Jiayi Liu (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706210#comment-17706210
 ] 

Jiayi Liu commented on RANGER-2894:
---

[~rmani] I submitted a patch, can you take a look?

> Plugins cannot interact with Solr with basic auth as audit targer
> -
>
> Key: RANGER-2894
> URL: https://issues.apache.org/jira/browse/RANGER-2894
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Nikita Ilyushkin
>Priority: Major
> Attachments: 001-RANGER-2894.patch
>
>
> There seems to be a problem with audit to Solr with [basic 
> authentication|https://lucene.apache.org/solr/guide/8_1/basic-authentication-plugin.html].
>  With the simple Solr cloud setup with basic auth every plugin I tried (HDFS, 
> YARN, HBase, Hive) failed to write audit to it with the similar errors:
> {code:java}
> 2020-06-25T19:39:35,248 ERROR 
> [hiveServer2.async.batch_hiveServer2.async.batch.solr_destWriter] 
> impl.CloudSolrClient: Request to collection [ranger_audits] failed due to 
> (401) org.apache.solr.client.solrj.impl.H
> ttpSolrClient$RemoteSolrException: Error from server at 
> http://nilyushkin-hadoop-dev-0.ru-central1.internal:8983/solr/ranger_audits_shard1_replica_n1:
>  Expected mime type application/octet-stream but got text/htm
> l. 
> 
> 
> Error 401 require authentication
> 
> HTTP ERROR 401
> Problem accessing /solr/ranger_audits_shard1_replica_n1/update. Reason:
> require authentication
> 
> 
> {code}
> tcpdump confirms that no auth headers are in requests.
>  Content of ranger--audit.xml:
> {code:java}
> 
> xasecure.audit.is.enabled
> true
> 
> 
> xasecure.audit.destination.solr
> true
> 
> 
> xasecure.audit.destination.solr.urls
> http://fqdn:8983/solr/ranger_audits
> 
> 
> xasecure.audit.destination.solr.user
> rangeraudit
> 
> 
> xasecure.audit.destination.solr.password
> admin
> 
> 
> xasecure.audit.destination.solr.zookeepers
> fqdn:2181/solr.server
> 
> 
> xasecure.audit.destination.solr.batch.filespool.dir
> /srv/audit_solr_spool
> 
> {code}
> The same results with xasecure.audit.destination.solr.urls instead 
> xasecure.audit.destination.solr.zookeepers.
> Ranger Admin on the other hand writes audit just fine with given credentials 
> to the same Solr.
>  Unsurprisingly, following Solr documentation (underlying solrj really) and 
> adding:
> {code:java}
> -Dsolr.httpclient.builder.factory=org.apache.solr.client.solrj.impl.PreemptiveBasicAuthClientBuilderFactory
>  -Dbasicauth=rangeraudit:admin
> {code}
> to the audited daemon (like HiveServer2) solves the problem.
>  I also haven't found setBasicAuthCredentials (the second method of auth 
> solrj provides) in the plugin sources or packages, so I assume it's just not 
> implemented or bugged.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (RANGER-2894) Plugins cannot interact with Solr with basic auth as audit targer

[Jiayi Liu (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jiayi Liu updated RANGER-2894:
--
Attachment: 001-RANGER-2894.patch

> Plugins cannot interact with Solr with basic auth as audit targer
> -
>
> Key: RANGER-2894
> URL: https://issues.apache.org/jira/browse/RANGER-2894
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Nikita Ilyushkin
>Priority: Major
> Attachments: 001-RANGER-2894.patch
>
>
> There seems to be a problem with audit to Solr with [basic 
> authentication|https://lucene.apache.org/solr/guide/8_1/basic-authentication-plugin.html].
>  With the simple Solr cloud setup with basic auth every plugin I tried (HDFS, 
> YARN, HBase, Hive) failed to write audit to it with the similar errors:
> {code:java}
> 2020-06-25T19:39:35,248 ERROR 
> [hiveServer2.async.batch_hiveServer2.async.batch.solr_destWriter] 
> impl.CloudSolrClient: Request to collection [ranger_audits] failed due to 
> (401) org.apache.solr.client.solrj.impl.H
> ttpSolrClient$RemoteSolrException: Error from server at 
> http://nilyushkin-hadoop-dev-0.ru-central1.internal:8983/solr/ranger_audits_shard1_replica_n1:
>  Expected mime type application/octet-stream but got text/htm
> l. 
> 
> 
> Error 401 require authentication
> 
> HTTP ERROR 401
> Problem accessing /solr/ranger_audits_shard1_replica_n1/update. Reason:
> require authentication
> 
> 
> {code}
> tcpdump confirms that no auth headers are in requests.
>  Content of ranger--audit.xml:
> {code:java}
> 
> xasecure.audit.is.enabled
> true
> 
> 
> xasecure.audit.destination.solr
> true
> 
> 
> xasecure.audit.destination.solr.urls
> http://fqdn:8983/solr/ranger_audits
> 
> 
> xasecure.audit.destination.solr.user
> rangeraudit
> 
> 
> xasecure.audit.destination.solr.password
> admin
> 
> 
> xasecure.audit.destination.solr.zookeepers
> fqdn:2181/solr.server
> 
> 
> xasecure.audit.destination.solr.batch.filespool.dir
> /srv/audit_solr_spool
> 
> {code}
> The same results with xasecure.audit.destination.solr.urls instead 
> xasecure.audit.destination.solr.zookeepers.
> Ranger Admin on the other hand writes audit just fine with given credentials 
> to the same Solr.
>  Unsurprisingly, following Solr documentation (underlying solrj really) and 
> adding:
> {code:java}
> -Dsolr.httpclient.builder.factory=org.apache.solr.client.solrj.impl.PreemptiveBasicAuthClientBuilderFactory
>  -Dbasicauth=rangeraudit:admin
> {code}
> to the audited daemon (like HiveServer2) solves the problem.
>  I also haven't found setBasicAuthCredentials (the second method of auth 
> solrj provides) in the plugin sources or packages, so I assume it's just not 
> implemented or bugged.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [ranger] liujiayi771 closed pull request #46: [RANGER-2671] unlink core-site.xml in usersync conf before chown and chmod

[via GitHub]

liujiayi771 closed pull request #46: [RANGER-2671] unlink core-site.xml in 
usersync conf before chown and chmod
URL: https://github.com/apache/ranger/pull/46


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

[GitHub] [ranger] liujiayi771 closed pull request #45: [RANGER-2667] set controlName to allow-all when disable presto plugin

[via GitHub]

liujiayi771 closed pull request #45: [RANGER-2667] set controlName to allow-all 
when disable presto plugin
URL: https://github.com/apache/ranger/pull/45


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

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Nixon Rodrigues]

+1 Apache Ranger 2.4.0 - rc2 release.

Thanks & Regards
Nixon

On Wed, 29 Mar 2023 at 07:43, Balaji Ganesan 
wrote:

> +1
>
> On Tue, Mar 28, 2023 at 7:46 AM Ramesh Mani  wrote:
>
> > +1 for Apache Ranger 2.4.0 rc2
> >
> > - Build from the source
> >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> > file was
> > successful.
> > - Verified some of the source code in tar files built.
> > - Verified PGP signature.
> > - Verified SHA256 / 512 hash.
> >
> > Thank you Selva for Apache Ranger 2.4.0 release candidate #2
> >
> > Thanks,
> > Ramesh
> >
> > On Mon, Mar 27, 2023 at 8:41 PM Selvamohan Neethiraj <
> sneet...@apache.org>
> > wrote:
> >
> > > Rangers:
> > >
> > > Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> > > within the dev community.
> > > Links to the release artifacts are given below. Please review and vote.
> > >
> > > The vote will be open for at least 72 hours or until necessary votes
> are
> > > reached.
> > > [   ] +1 approve
> > > [   ] +0 no opinion
> > > [   ] -1 disapprove (and reason why)
> > >
> > > Thanks,
> > > Selva-
> > > Ranger PMC
> > >
> > > List of issues / improvements addressed in this release:  click-here <
> > >
> >
> https://issues.apache.org/jira/browse/RANGER-4154?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20ORDER%20BY%20key%20desc
> > > >
> > >
> > > Git tag for the release:
> > > https://github.com/apache/ranger/tree/release-2.4.0-rc2
> > > Sources for the release:
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> > >
> > > Source release verification:
> > > PGP Signature:
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> > > SHA256
> > > <
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.ascSHA256
> > >
> > > Hash:
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> > > SHA512
> > > <
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256SHA512
> > >
> > > Hash:
> > >
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
> > >
> > > Keys to verify the signature:
> > > https://dist.apache.org/repos/dist/release/ranger/KEYS
> > >
> > > Click Here <
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20and%20type%20in%20(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc
> > >
> > > to view New Features/Enhancements in this release.
> > >
> > >
> > >
> > >
> > >
> > >
> >
>

[GitHub] [ranger] mneethiraj merged pull request #238: RANGER-4158: Update README.md

[via GitHub]

mneethiraj merged PR #238:
URL: https://github.com/apache/ranger/pull/238


-- 
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] [Updated] (RANGER-4158) Update python client README

[Abhishek Kumar (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Kumar updated RANGER-4158:
---
Affects Version/s: 2.3.0

> Update python client README
> ---
>
> Key: RANGER-4158
> URL: https://issues.apache.org/jira/browse/RANGER-4158
> Project: Ranger
>  Issue Type: Task
>  Components: intg
>Affects Versions: 2.3.0
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Minor
>
> An external dependency needs to be installed manually via pip to allow python 
> client to be used in kerberos environments.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4158) Update python client README

[Abhishek Kumar (Jira)]

Abhishek Kumar created RANGER-4158:
--

 Summary: Update python client README
 Key: RANGER-4158
 URL: https://issues.apache.org/jira/browse/RANGER-4158
 Project: Ranger
  Issue Type: Task
  Components: intg
Reporter: Abhishek Kumar
Assignee: Abhishek Kumar


An external dependency needs to be installed manually via pip to allow python 
client to be used in kerberos environments.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [ranger] kumaab opened a new pull request, #238: Update README.md

[via GitHub]

kumaab opened a new pull request, #238:
URL: https://github.com/apache/ranger/pull/238

   ## What changes were proposed in this pull request?
   
   Updating python client README
   
   ## How was this patch tested?
   
   Skipped, regular build only.


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

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Balaji Ganesan]

+1

On Tue, Mar 28, 2023 at 7:46 AM Ramesh Mani  wrote:

> +1 for Apache Ranger 2.4.0 rc2
>
> - Build from the source
>
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> file was
> successful.
> - Verified some of the source code in tar files built.
> - Verified PGP signature.
> - Verified SHA256 / 512 hash.
>
> Thank you Selva for Apache Ranger 2.4.0 release candidate #2
>
> Thanks,
> Ramesh
>
> On Mon, Mar 27, 2023 at 8:41 PM Selvamohan Neethiraj 
> wrote:
>
> > Rangers:
> >
> > Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> > within the dev community.
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> > [   ] +1 approve
> > [   ] +0 no opinion
> > [   ] -1 disapprove (and reason why)
> >
> > Thanks,
> > Selva-
> > Ranger PMC
> >
> > List of issues / improvements addressed in this release:  click-here <
> >
> https://issues.apache.org/jira/browse/RANGER-4154?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20ORDER%20BY%20key%20desc
> > >
> >
> > Git tag for the release:
> > https://github.com/apache/ranger/tree/release-2.4.0-rc2
> > Sources for the release:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> >
> > Source release verification:
> > PGP Signature:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> > SHA256
> > <
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.ascSHA256
> >
> > Hash:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> > SHA512
> > <
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256SHA512
> >
> > Hash:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
> >
> > Keys to verify the signature:
> > https://dist.apache.org/repos/dist/release/ranger/KEYS
> >
> > Click Here <
> >
> https://issues.apache.org/jira/issues/?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20and%20type%20in%20(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc
> >
> > to view New Features/Enhancements in this release.
> >
> >
> >
> >
> >
> >
>

Re: Review Request 74366: RANGER-4136: Incorrect processing of tag-deltas by RangerTagEnricher - Part 2

[Abhay Kulkarni]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74366/
---

(Updated March 29, 2023, 1:46 a.m.)


Review request for ranger, madhan, Madhan Neethiraj, Ramesh Mani, Sailaja 
Polavarapu, and Velmurugan Periasamy.


Bugs: RANGER-4136
https://issues.apache.org/jira/browse/RANGER-4136


Repository: ranger


Description
---

Ranger supports incremental tag downloads when configured. When a mapping for a 
service-resource is changed, the tag download request provides only the updated 
service-resource. RangerTagEnricher is expected to remove the existing 
service-resource and the associated tags from its cache and add it back with 
updated associated tags.

Current code does not remove the existing service-resource and its associated 
tags correctly leading to incorrect tags to be retrieved for the 
service-resource.

More debugging help is added to monitor the process flow for the incremental 
tag processing.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagEnricher.java
 198d24d97 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyRepository.java
 b5b26702c 
  agents-common/src/main/java/org/apache/ranger/plugin/util/ServiceTags.java 
9b902789a 


Diff: https://reviews.apache.org/r/74366/diff/2/

Changes: https://reviews.apache.org/r/74366/diff/1-2/


Testing
---

Passed all unit tests. Verified that incremental tagged entities are correctly 
processed and properly cleaned up.


Thanks,

Abhay Kulkarni

[jira] [Updated] (RANGER-4157) implicit expression condition not added to service-defs having existing conditions

[Madhan Neethiraj (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj updated RANGER-4157:
-
Attachment: RANGER-4157.patch

> implicit expression condition not added to service-defs having existing 
> conditions
> --
>
> Key: RANGER-4157
> URL: https://issues.apache.org/jira/browse/RANGER-4157
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: RANGER-4157.patch
>
>
> RANGER-4117 introduced implicit addition of expression condition to all 
> service-defs. However, this update does not add expression condition to 
> service-defs that already have any condition, like Knox, Solr, Kafka. This 
> needs to be fixed so that the expression condition will be available in all 
> service-defs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Review Request 74367: RANGER-4157: fixed handling of implicit addition of expression condition

[Madhan Neethiraj]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74367/
---

Review request for ranger, Ankita Sinha, Kishor Gollapalliwar, Abhay Kulkarni, 
Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, Subhrat 
Chaudhary, and Velmurugan Periasamy.


Bugs: RANGER-4157
https://issues.apache.org/jira/browse/RANGER-4157


Repository: ranger


Description
---

moved from RangerServiceDefService.mapEntityToViewBean() to 
RangerServiceDefServiceBase.populateViewBean() many fields are overwriten in 
populateViewBean() method


Diffs
-

  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceDefService.java
 328d8baa6 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceDefServiceBase.java
 656bc0184 


Diff: https://reviews.apache.org/r/74367/diff/1/


Testing
---

- verified that expression condition is added to all service-defs, including 
knox/kafka/solr
- verified that existing tests pass successfully


Thanks,

Madhan Neethiraj

[jira] [Assigned] (RANGER-4157) implicit expression condition not added to service-defs having existing conditions

[Madhan Neethiraj (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj reassigned RANGER-4157:


Assignee: Madhan Neethiraj

> implicit expression condition not added to service-defs having existing 
> conditions
> --
>
> Key: RANGER-4157
> URL: https://issues.apache.org/jira/browse/RANGER-4157
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
>
> RANGER-4117 introduced implicit addition of expression condition to all 
> service-defs. However, this update does not add expression condition to 
> service-defs that already have any condition, like Knox, Solr, Kafka. This 
> needs to be fixed so that the expression condition will be available in all 
> service-defs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (RANGER-4157) implicit expression condition not added to service-defs having existing conditions

[Madhan Neethiraj (Jira)]

Madhan Neethiraj created RANGER-4157:


 Summary: implicit expression condition not added to service-defs 
having existing conditions
 Key: RANGER-4157
 URL: https://issues.apache.org/jira/browse/RANGER-4157
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 3.0.0, 2.4.0
Reporter: Madhan Neethiraj


RANGER-4117 introduced implicit addition of expression condition to all 
service-defs. However, this update does not add expression condition to 
service-defs that already have any condition, like Knox, Solr, Kafka. This 
needs to be fixed so that the expression condition will be available in all 
service-defs.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Request to add as Contributor to Apache Ranger

[Madhan Neethiraj]

Dharmesh,

Thank you for your interest in contributing to Apache Ranger. You now have 
contributor access in Apache Ranger.

Welcome to Apache Ranger.

Thanks,
Madhan
Apache Ranger PMC



On 3/28/23, 8:28 AM, "Dharmesh Makwana" mailto:dharmeshbmakw...@gmail.com>> wrote:


Hi community,


I would like to contribute to the Apache Ranger project, please add me
as a contributor.My Jira User Id is *mdharmesh.*


Thanks and Regards,
Dharmesh M

Request to add as Contributor to Apache Ranger

[Dharmesh Makwana]

Hi community,

I would like to contribute to the Apache Ranger project, please add me
as a contributor.My Jira User Id is *mdharmesh.*

Thanks and Regards,
Dharmesh M

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Ramesh Mani]

+1 for Apache Ranger 2.4.0 rc2

- Build from the source
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
file was
successful.
- Verified some of the source code in tar files built.
- Verified PGP signature.
- Verified SHA256 / 512 hash.

Thank you Selva for Apache Ranger 2.4.0 release candidate #2

Thanks,
Ramesh

On Mon, Mar 27, 2023 at 8:41 PM Selvamohan Neethiraj 
wrote:

> Rangers:
>
> Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> within the dev community.
> Links to the release artifacts are given below. Please review and vote.
>
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
> [   ] +1 approve
> [   ] +0 no opinion
> [   ] -1 disapprove (and reason why)
>
> Thanks,
> Selva-
> Ranger PMC
>
> List of issues / improvements addressed in this release:  click-here <
> https://issues.apache.org/jira/browse/RANGER-4154?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20ORDER%20BY%20key%20desc
> >
>
> Git tag for the release:
> https://github.com/apache/ranger/tree/release-2.4.0-rc2
> Sources for the release:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
>
> Source release verification:
> PGP Signature:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> SHA256
> 
> Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> SHA512
> 
> Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
>
> Keys to verify the signature:
> https://dist.apache.org/repos/dist/release/ranger/KEYS
>
> Click Here <
> https://issues.apache.org/jira/issues/?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20and%20type%20in%20(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc>
> to view New Features/Enhancements in this release.
>
>
>
>
>
>

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Nitin Galave]

+1 Apache Ranger 2.4.0-rc2

 - Verified the build.
 - Ranger modules have been tested for basic CRUD operations.

Thanks,
Nitin

On Tue, Mar 28, 2023 at 7:33 PM Jai Patel 
wrote:

> +1 for Ranger Release 2.4.0-rc2
>
> Verified signature.
> Verified build.
>
> Thanks,
> Jai.
>
> On Tue, Mar 28, 2023 at 7:31 PM Selvamohan Neethiraj 
> wrote:
>
> >
> >
> > Begin forwarded message:
> >
> > *From: *Selvamohan Neethiraj 
> > *Subject: **[VOTE] Apache Ranger 2.4.0 Release - rc2*
> > *Date: *March 27, 2023 at 11:40:16 PM EDT
> > *To: *dev@ranger.apache.org
> >
> > Rangers:
> >
> > Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> > within the dev community.
> > Links to the release artifacts are given below. Please review and vote.
> >
> > The vote will be open for at least 72 hours or until necessary votes are
> > reached.
> > [   ] +1 approve
> > [   ] +0 no opinion
> > [   ] -1 disapprove (and reason why)
> >
> > Thanks,
> > Selva-
> > Ranger PMC
> >
> > List of issues / improvements addressed in this release:  click-here
> > <
> https://issues.apache.org/jira/browse/RANGER-4154?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20ORDER%20BY%20key%20desc
> >
> >
> > Git tag for the release:
> > https://github.com/apache/ranger/tree/release-2.4.0-rc2
> > Sources for the release:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
> >
> > Source release verification:
> > PGP Signature:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> > SHA256 Hash:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> > SHA512 Hash:
> >
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
> >
> > Keys to verify the signature:
> > https://dist.apache.org/repos/dist/release/ranger/KEYS
> >
> > Click Here
> > <
> https://issues.apache.org/jira/issues/?jql=project=RANGER%20and%20fixVersion%20%20=%202.4.0%20and%20status%20=%20Resolved%20and%20type%20in%20(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc>
> to
> > view *New Features/Enhancements *in this release.
> >
> >
> >
> >
> >
> >
> >
>
> --
>
> <
> https://download.privacera.com/modernizing-data-governance-faster-insights-webinar-email
> >
>
>
>
> *This electronically transmitted message may contain information that is
> privileged and confidential and subject to legal restrictions and
> penalties
> regarding its unauthorized disclosure or other use.  You are prohibited
> from copying, distributing, or otherwise using this information if you are
> not the intended recipient.*
>
>

-- 


*Thanks,Nitin Galave.*

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Jai Patel]

+1 for Ranger Release 2.4.0-rc2

Verified signature.
Verified build.

Thanks,
Jai.

On Tue, Mar 28, 2023 at 7:31 PM Selvamohan Neethiraj 
wrote:

>
>
> Begin forwarded message:
>
> *From: *Selvamohan Neethiraj 
> *Subject: **[VOTE] Apache Ranger 2.4.0 Release - rc2*
> *Date: *March 27, 2023 at 11:40:16 PM EDT
> *To: *dev@ranger.apache.org
>
> Rangers:
>
> Apache Ranger 2.4.0 release candidate #2 is now available for a vote
> within the dev community.
> Links to the release artifacts are given below. Please review and vote.
>
> The vote will be open for at least 72 hours or until necessary votes are
> reached.
> [   ] +1 approve
> [   ] +0 no opinion
> [   ] -1 disapprove (and reason why)
>
> Thanks,
> Selva-
> Ranger PMC
>
> List of issues / improvements addressed in this release:  click-here
> 
>
> Git tag for the release:
> https://github.com/apache/ranger/tree/release-2.4.0-rc2
> Sources for the release:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
>
> Source release verification:
> PGP Signature:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
> SHA256 Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
> SHA512 Hash:
> https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
>
> Keys to verify the signature:
> https://dist.apache.org/repos/dist/release/ranger/KEYS
>
> Click Here
> 
>  to
> view *New Features/Enhancements *in this release.
>
>
>
>
>
>
>

-- 
 




*This electronically transmitted message may contain information that is 
privileged and confidential and subject to legal restrictions and penalties 
regarding its unauthorized disclosure or other use.  You are prohibited 
from copying, distributing, or otherwise using this information if you are 
not the intended recipient.*

[jira] [Commented] (RANGER-2894) Plugins cannot interact with Solr with basic auth as audit targer

[Jiayi Liu (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705984#comment-17705984
 ] 

Jiayi Liu commented on RANGER-2894:
---

[~rmani] Hi, I solved this problem by using System.setProperty to set 
solr.httpclient.builder.factory and basicauth  in SolrAuditDestination. Do you 
think it's ok to do this? I can submit a PR, thanks.

> Plugins cannot interact with Solr with basic auth as audit targer
> -
>
> Key: RANGER-2894
> URL: https://issues.apache.org/jira/browse/RANGER-2894
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 1.1.0, 2.0.0
>Reporter: Nikita Ilyushkin
>Priority: Major
>
> There seems to be a problem with audit to Solr with [basic 
> authentication|https://lucene.apache.org/solr/guide/8_1/basic-authentication-plugin.html].
>  With the simple Solr cloud setup with basic auth every plugin I tried (HDFS, 
> YARN, HBase, Hive) failed to write audit to it with the similar errors:
> {code:java}
> 2020-06-25T19:39:35,248 ERROR 
> [hiveServer2.async.batch_hiveServer2.async.batch.solr_destWriter] 
> impl.CloudSolrClient: Request to collection [ranger_audits] failed due to 
> (401) org.apache.solr.client.solrj.impl.H
> ttpSolrClient$RemoteSolrException: Error from server at 
> http://nilyushkin-hadoop-dev-0.ru-central1.internal:8983/solr/ranger_audits_shard1_replica_n1:
>  Expected mime type application/octet-stream but got text/htm
> l. 
> 
> 
> Error 401 require authentication
> 
> HTTP ERROR 401
> Problem accessing /solr/ranger_audits_shard1_replica_n1/update. Reason:
> require authentication
> 
> 
> {code}
> tcpdump confirms that no auth headers are in requests.
>  Content of ranger--audit.xml:
> {code:java}
> 
> xasecure.audit.is.enabled
> true
> 
> 
> xasecure.audit.destination.solr
> true
> 
> 
> xasecure.audit.destination.solr.urls
> http://fqdn:8983/solr/ranger_audits
> 
> 
> xasecure.audit.destination.solr.user
> rangeraudit
> 
> 
> xasecure.audit.destination.solr.password
> admin
> 
> 
> xasecure.audit.destination.solr.zookeepers
> fqdn:2181/solr.server
> 
> 
> xasecure.audit.destination.solr.batch.filespool.dir
> /srv/audit_solr_spool
> 
> {code}
> The same results with xasecure.audit.destination.solr.urls instead 
> xasecure.audit.destination.solr.zookeepers.
> Ranger Admin on the other hand writes audit just fine with given credentials 
> to the same Solr.
>  Unsurprisingly, following Solr documentation (underlying solrj really) and 
> adding:
> {code:java}
> -Dsolr.httpclient.builder.factory=org.apache.solr.client.solrj.impl.PreemptiveBasicAuthClientBuilderFactory
>  -Dbasicauth=rangeraudit:admin
> {code}
> to the audited daemon (like HiveServer2) solves the problem.
>  I also haven't found setBasicAuthCredentials (the second method of auth 
> solrj provides) in the plugin sources or packages, so I assume it's just not 
> implemented or bugged.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4047) Ranger KMS health metrics

[Bhavik Patel (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705939#comment-17705939
 ] 

Bhavik Patel commented on RANGER-4047:
--

[~vikkumar] are you working on this?

> Ranger KMS health metrics 
> --
>
> Key: RANGER-4047
> URL: https://issues.apache.org/jira/browse/RANGER-4047
> Project: Ranger
>  Issue Type: New Feature
>  Components: kms
>Reporter: Vikas Kumar
>Assignee: Vikas Kumar
>Priority: Major
>
> Ranger KMS should collect the important System as well as application level 
> health metrics.
> System metrics: JVM/CPU/memory related metrics
> Application metrics: KMS API execution metrics. Like, number of time DECRYPT 
> operation invoked and time taken to complete the request etc.
> There should also be API to consume these stats, preferably REST API. Any 
> metric tools should be able to get these metrics through that REST API.
> This will help making KMS highly observable. Alerts system can be configured 
> to consume, process and generate alerts.
> There could be many other use cases.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Review Request 74147: Ranger KMS generates master key on every restart before inserting into DB

[bhavik patel]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/74147/#review225304
---


Ship it!




Ship It!

- bhavik patel


On Oct. 12, 2022, 7:49 a.m., Vikas Kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74147/
> ---
> 
> (Updated Oct. 12, 2022, 7:49 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah and Sailaja Polavarapu.
> 
> 
> Bugs: RANGER-3927
> https://issues.apache.org/jira/browse/RANGER-3927
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Issue: Master Key(MK) was being first generated and then it was checking into 
> DB that if MK actually exists on each restart of the KMS process. If exists, 
> it simply returns. The same check could have been added before regenerating 
> the MK to avoid this unnecessary execution.
> 
> FIX: Added the same check before calling the method 
> RangerMasterKey.saveEncryptedMK(). Also removed the check from 
> saveEncryptedMK().
> 
> New logs: If MK doesn't exist, then 
> 
> logger.info("Master Key doesn't exist in DB, Generating the Master Key");
> 
> if MK already exists, then
> 
> logger.debug("Ranger Master Key already exists in the DB, returning.");
> 
> 
> Diffs
> -
> 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerMasterKey.java 
> c37e98ee5 
> 
> 
> Diff: https://reviews.apache.org/r/74147/diff/3/
> 
> 
> Testing
> ---
> 
> verified through logs on restart of the KMS service. And I got "Ranger Master 
> Key already exists in the DB, returning." It was not going to generate and 
> save the MK into DB.
> 
> 
> Thanks,
> 
> Vikas Kumar
> 
>

[jira] [Updated] (RANGER-4155) Structure of resource(UI) hierarchy in policy form not proper formatted for multiple values.

[Dhaval Rajpara (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dhaval Rajpara updated RANGER-4155:
---
Fix Version/s: 3.0.0
   2.4.0

> Structure of resource(UI) hierarchy in policy form not proper formatted for 
> multiple values. 
> -
>
> Key: RANGER-4155
> URL: https://issues.apache.org/jira/browse/RANGER-4155
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Fix For: 3.0.0, 2.4.0
>
> Attachments: 0001-RANGER-4155.patch, Screenshot from 2023-03-24 
> 18-17-42.png
>
>
> CSS structure of multiple resources are breaking in policy form.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (RANGER-4155) Structure of resource(UI) hierarchy in policy form not proper formatted for multiple values.

[Dhaval Rajpara (Jira)]

[ 
https://issues.apache.org/jira/browse/RANGER-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705905#comment-17705905
 ] 

Dhaval Rajpara commented on RANGER-4155:


Committed to 
[master|https://github.com/apache/ranger/commit/cc67b665fea0bc31c2941ae9940983c8c1fb]
 branch.

> Structure of resource(UI) hierarchy in policy form not proper formatted for 
> multiple values. 
> -
>
> Key: RANGER-4155
> URL: https://issues.apache.org/jira/browse/RANGER-4155
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: 0001-RANGER-4155.patch, Screenshot from 2023-03-24 
> 18-17-42.png
>
>
> CSS structure of multiple resources are breaking in policy form.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [VOTE] Apache Ranger 2.4.0 Release - rc2

[Madhan Neethiraj]

+1 for Apache Ranger 2.4.0-rc2

- verified signature
- verified 2.4.0-rc2 builds successfully
- installed Ranger with Postgres database; verified startup of 
admin/usersync/tagsync services
- added new users and groups; updated user-group association; verified that 
usersync picked up these users and groups
- created services, policies, security zones
- sanity testing of HDFS/Hive/HBase/Kafka/YARN plugins
- verified tag-based policies and {OWNER} macro in Hive
- verified audit logs from plugins, audit-filters
- verified expression condition in Hive policies
- verified that non-admin users with service admin privilege can create 
policies with excludes resource
- verified policies with multiple resource-sets

Thank you, Selva for putting this release together.

Go Rangers!

Madhan


On 3/27/23, 8:41 PM, "Selvamohan Neethiraj" mailto:sneet...@apache.org>> wrote:


Rangers:


Apache Ranger 2.4.0 release candidate #2 is now available for a vote within the 
dev community.
Links to the release artifacts are given below. Please review and vote.


The vote will be open for at least 72 hours or until necessary votes are 
reached.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Thanks,
Selva-
Ranger PMC 


List of issues / improvements addressed in this release: click-here 

 



Git tag for the release: 
https://github.com/apache/ranger/tree/release-2.4.0-rc2 

Sources for the release: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz
 



Source release verification:
PGP Signature: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.asc
 

SHA256 Hash: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha256
 

SHA512 Hash: 
https://dist.apache.org/repos/dist/dev/ranger/2.4.0-rc2/apache-ranger-2.4.0.tar.gz.sha512
 



Keys to verify the signature: 
https://dist.apache.org/repos/dist/release/ranger/KEYS 



Click Here 
(%22New%20Feature%22,%20Improvement)%20ORDER%20BY%20key%20desc>
 to view New Features/Enhancements in this release.

[jira] [Assigned] (RANGER-4081) [Ranger UI] [React JS] If the url to edit a policy, service or permissions for a module, and the url to view user/group/roles contains an invalid id, then page should d

[Brijesh Bhalala (Jira)]

 [ 
https://issues.apache.org/jira/browse/RANGER-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brijesh Bhalala reassigned RANGER-4081:
---

Assignee: (was: Brijesh Bhalala)

> [Ranger UI] [React JS] If the url to edit a policy, service or permissions 
> for a module, and the url to view user/group/roles contains an invalid id, 
> then page should display an error
> ---
>
> Key: RANGER-4081
> URL: https://issues.apache.org/jira/browse/RANGER-4081
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Priority: Major
>  Labels: ranger-react
>
> If the url to edit a policy, a service or permissions for a certain module 
> contains an invalid service id or a policy id, 
> then the page is stuck in loading state. 
> Ideally, if the service or a policy for a given id does not exist, then the 
> page should
> display the appropriate error message.
> If the url to view the user/group/role details also has an invalid id, the 
> page is stuck in loading state instead of displaying an error.
> For example, if the url to edit a security zone contains an invalid zone id, 
> there is a popup that displays the message "Data not found for given id". A 
> similar message should be displayed for other urls with invalid ids.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)