[jira] [Commented] (RANGER-3709) Fix NullPointerException in getSecureServicePoliciesIfUpdated call of ServiceRest

[Pradeep Agrawal (Jira)]

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

Pradeep Agrawal commented on RANGER-3709:
-

Master branch commit link : 
[https://github.com/apache/ranger/commit/11d998415d196657fb760ae273a8717927b915c4]

2.3 branch commit link : 
https://github.com/apache/ranger/commit/7a8af6cf0b5ffa9f126f68c7d58feb09e8da734e

> Fix NullPointerException in getSecureServicePoliciesIfUpdated call of 
> ServiceRest
> -
>
> Key: RANGER-3709
> URL: https://issues.apache.org/jira/browse/RANGER-3709
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 
> 0001-RANGER-3709-Fix-NullPointerException-in-getSecureSer.patch
>
>
> {code:java}
> java.lang.NullPointerException
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache$ServicePoliciesWrapper.getLatestOrCached(RangerServicePoliciesCache.java:231)
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache.getServicePolicies(RangerServicePoliciesCache.java:125)
>  {code}
> After fix : 
> {code:java}
> 2022-04-14 15:07:29,557 ERROR 
> org.apache.ranger.common.RangerServicePoliciesCache: Could not get lock in 
> [10] seconds, returning cached ServicePolicies and wait Queue Length:[0], 
> servicePolicies version:[-1] {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3669) Connection to DB fails for MySQL version above 8.0

[gomathinayagam (Jira)]

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

gomathinayagam commented on RANGER-3669:


all are saying to upgrade teh jdbc driver, not mentioned about passing 
connectionstring, if so please let me know.

> Connection to DB fails for MySQL version above 8.0
> --
>
> Key: RANGER-3669
> URL: https://issues.apache.org/jira/browse/RANGER-3669
> Project: Ranger
>  Issue Type: Improvement
>  Components: kms
>Affects Versions: 3.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3669.01.patch, RANGER-3669.patch
>
>
> Observed that Ranger KMS DB setup fails when using with MySQL version above 
> 8.0.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3669) Connection to DB fails for MySQL version above 8.0

[gomathinayagam (Jira)]

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

gomathinayagam commented on RANGER-3669:


how the below issue can be solved? more details here 
[https://bugs.mysql.com/bug.php?id=93042] 
ava.sql.SQLException: Unknown system variable 'query_cache_size'
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:964)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3973)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3909)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2527)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2680)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2486)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2444)
at com.mysql.jdbc.StatementImpl.executeQuery(StatementImpl.java:1381)

> Connection to DB fails for MySQL version above 8.0
> --
>
> Key: RANGER-3669
> URL: https://issues.apache.org/jira/browse/RANGER-3669
> Project: Ranger
>  Issue Type: Improvement
>  Components: kms
>Affects Versions: 3.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3669.01.patch, RANGER-3669.patch
>
>
> Observed that Ranger KMS DB setup fails when using with MySQL version above 
> 8.0.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 73869: RANGER-3389 : Swagger UI Support for Ranger REST API.

[Nitin Galave]

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




security-admin/src/main/webapp/scripts/modules/RestCsrf.js
Lines 89 (patched)


Can we clear csrfToken when user logout?


- Nitin Galave


On April 4, 2022, 9 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73869/
> ---
> 
> (Updated April 4, 2022, 9 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kishor 
> Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, 
> Pradeep Agrawal, Sailaja Polavarapu, Steven Ramirez, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3389
> https://issues.apache.org/jira/browse/RANGER-3389
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Create documentation for ranger REST API then display that documentation 
> through swagger ui as part of ranger admin ui.
> 
> 
> Diffs
> -
> 
>   distro/src/main/assembly/admin-web.xml e19d50572 
>   docs/src/site/resources/index.html PRE-CREATION 
>   docs/src/site/resources/index.js PRE-CREATION 
>   docs/src/site/resources/swagger-ui-bundle.js PRE-CREATION 
>   docs/src/site/resources/swagger-ui-es-bundle-core.js PRE-CREATION 
>   docs/src/site/resources/swagger-ui-es-bundle.js PRE-CREATION 
>   docs/src/site/resources/swagger-ui-standalone-preset.js PRE-CREATION 
>   docs/src/site/resources/swagger-ui.css PRE-CREATION 
>   docs/src/site/resources/swagger-ui.js PRE-CREATION 
>   enunciate.xml 13b465b55 
>   pom.xml 252463227 
>   security-admin/src/main/webapp/scripts/modules/RestCsrf.js 63561e3d1 
>   security-admin/src/main/webapp/templates/common/ProfileBar_tmpl.html 
> 285d10617 
> 
> 
> Diff: https://reviews.apache.org/r/73869/diff/2/
> 
> 
> Testing
> ---
> 
> Updated Review request form https://reviews.apache.org/r/73566/
> Fixed issue where swagger UI is not loading.
> Fixed all review comment on patch.
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 73945: RANGER-3709: Fix NullPointerException in getSecureServicePoliciesIfUpdated call of ServiceRest

[Ramesh Mani]

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


Ship it!




Ship It!

- Ramesh Mani


On April 14, 2022, 4:25 p.m., Pradeep Agrawal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73945/
> ---
> 
> (Updated April 14, 2022, 4:25 p.m.)
> 
> 
> Review request for ranger, bhavik patel, Abhay Kulkarni, Madhan Neethiraj, 
> Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3709
> https://issues.apache.org/jira/browse/RANGER-3709
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> **Problem Statement:** if servicePolicies object is null then following error 
> message may appear in the log file with long stacktrace.
> java.lang.NullPointerException
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache$ServicePoliciesWrapper.getLatestOrCached(RangerServicePoliciesCache.java:231)
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache.getServicePolicies(RangerServicePoliciesCache.java:125)
>   at 
> org.apache.ranger.biz.ServiceDBStore.getServicePoliciesIfUpdated(ServiceDBStore.java:2797)
>   at 
> org.apache.ranger.rest.ServiceREST.getSecureServicePoliciesIfUpdated(ServiceREST.java:3140)
> 
> **Proposed Statement:** 
> Add a null check and accordingly print the Policy Version.
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/java/org/apache/ranger/common/RangerServicePoliciesCache.java
>  061b14cbd 
> 
> 
> Diff: https://reviews.apache.org/r/73945/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with patch and can see following message.
> 
> 2022-04-14 15:07:29,557 ERROR 
> org.apache.ranger.common.RangerServicePoliciesCache: Could not get lock in 
> [10] seconds, returning cached ServicePolicies and wait Queue Length:[0], 
> servicePolicies version:[-1]
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

[jira] [Updated] (RANGER-3709) Fix NullPointerException in getSecureServicePoliciesIfUpdated call of ServiceRest

[Pradeep Agrawal (Jira)]

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

Pradeep Agrawal updated RANGER-3709:

Attachment: 0001-RANGER-3709-Fix-NullPointerException-in-getSecureSer.patch

> Fix NullPointerException in getSecureServicePoliciesIfUpdated call of 
> ServiceRest
> -
>
> Key: RANGER-3709
> URL: https://issues.apache.org/jira/browse/RANGER-3709
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: 
> 0001-RANGER-3709-Fix-NullPointerException-in-getSecureSer.patch
>
>
> {code:java}
> java.lang.NullPointerException
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache$ServicePoliciesWrapper.getLatestOrCached(RangerServicePoliciesCache.java:231)
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache.getServicePolicies(RangerServicePoliciesCache.java:125)
>  {code}
> After fix : 
> {code:java}
> 2022-04-14 15:07:29,557 ERROR 
> org.apache.ranger.common.RangerServicePoliciesCache: Could not get lock in 
> [10] seconds, returning cached ServicePolicies and wait Queue Length:[0], 
> servicePolicies version:[-1] {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3709) Fix NullPointerException in getSecureServicePoliciesIfUpdated call of ServiceRest

[kirby zhou (Jira)]

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

kirby zhou commented on RANGER-3709:


How to reproduce?

> Fix NullPointerException in getSecureServicePoliciesIfUpdated call of 
> ServiceRest
> -
>
> Key: RANGER-3709
> URL: https://issues.apache.org/jira/browse/RANGER-3709
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> {code:java}
> java.lang.NullPointerException
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache$ServicePoliciesWrapper.getLatestOrCached(RangerServicePoliciesCache.java:231)
>   at 
> org.apache.ranger.common.RangerServicePoliciesCache.getServicePolicies(RangerServicePoliciesCache.java:125)
>  {code}
> After fix : 
> {code:java}
> 2022-04-14 15:07:29,557 ERROR 
> org.apache.ranger.common.RangerServicePoliciesCache: Could not get lock in 
> [10] seconds, returning cached ServicePolicies and wait Queue Length:[0], 
> servicePolicies version:[-1] {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Review Request 73945: RANGER-3709: Fix NullPointerException in getSecureServicePoliciesIfUpdated call of ServiceRest

[Pradeep Agrawal]

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

Review request for ranger, bhavik patel, Abhay Kulkarni, Madhan Neethiraj, 
Ramesh Mani, Sailaja Polavarapu, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

**Problem Statement:** if servicePolicies object is null then following error 
message may appear in the log file with long stacktrace.
java.lang.NullPointerException
at 
org.apache.ranger.common.RangerServicePoliciesCache$ServicePoliciesWrapper.getLatestOrCached(RangerServicePoliciesCache.java:231)
at 
org.apache.ranger.common.RangerServicePoliciesCache.getServicePolicies(RangerServicePoliciesCache.java:125)
at 
org.apache.ranger.biz.ServiceDBStore.getServicePoliciesIfUpdated(ServiceDBStore.java:2797)
at 
org.apache.ranger.rest.ServiceREST.getSecureServicePoliciesIfUpdated(ServiceREST.java:3140)

**Proposed Statement:** 
Add a null check and accordingly print the Policy Version.


Diffs
-

  
security-admin/src/main/java/org/apache/ranger/common/RangerServicePoliciesCache.java
 061b14cbd 


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


Testing
---

Tested with patch and can see following message.

2022-04-14 15:07:29,557 ERROR 
org.apache.ranger.common.RangerServicePoliciesCache: Could not get lock in [10] 
seconds, returning cached ServicePolicies and wait Queue Length:[0], 
servicePolicies version:[-1]


Thanks,

Pradeep Agrawal

[jira] [Created] (RANGER-3709) Fix NullPointerException in getSecureServicePoliciesIfUpdated call of ServiceRest

[Pradeep Agrawal (Jira)]

Pradeep Agrawal created RANGER-3709:
---

 Summary: Fix NullPointerException in 
getSecureServicePoliciesIfUpdated call of ServiceRest
 Key: RANGER-3709
 URL: https://issues.apache.org/jira/browse/RANGER-3709
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 3.0.0, 2.3.0
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal
 Fix For: 3.0.0, 2.3.0


{code:java}
java.lang.NullPointerException
at 
org.apache.ranger.common.RangerServicePoliciesCache$ServicePoliciesWrapper.getLatestOrCached(RangerServicePoliciesCache.java:231)
at 
org.apache.ranger.common.RangerServicePoliciesCache.getServicePolicies(RangerServicePoliciesCache.java:125)
 {code}
After fix : 
{code:java}
2022-04-14 15:07:29,557 ERROR 
org.apache.ranger.common.RangerServicePoliciesCache: Could not get lock in [10] 
seconds, returning cached ServicePolicies and wait Queue Length:[0], 
servicePolicies version:[-1] {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2

[Ramesh Mani (Jira)]

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

Ramesh Mani commented on RANGER-3165:
-

[~chengyang14]   ElasticSearch version 7.17.2 is not Apache licensed and hence 
we need to see which has to be used. Already master branch version is in 
7.10.0. We need to see what is best to do here, please review 
https://www.elastic.co/pricing/faq/licensing

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Major
> Attachments: 
> 0001-RANGER-3165-Upgrade-Elasticsearch-version-in-Ranger-.patch
>
>
> Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
> update the version to 7.17.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3687) Password Policy Best Practices for Strong Security

[kirby zhou (Jira)]

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

kirby zhou commented on RANGER-3687:


Since ranger-2.3 changes database schema.

Is there a guide of how to upgrade ranger?

Especially how to upgrade dockerized ranger, it is difficult to run setup.sh 
again inside a docker image.

 

> Password Policy Best Practices for Strong Security
> --
>
> Key: RANGER-3687
> URL: https://issues.apache.org/jira/browse/RANGER-3687
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0, 2.3.0
>Reporter: Bhavik Patel
>Assignee: Bhavik Patel
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> # Password history should be configured to restrict users from reusing their 
> last 4 or 5 passwords.
>  # Forcing users to change passwords every 90-180 days 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3165:
-
Affects Version/s: 3.0.0

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Major
> Attachments: 
> 0001-RANGER-3165-Upgrade-Elasticsearch-version-in-Ranger-.patch
>
>
> Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
> update the version to 7.17.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3165:
-
Priority: Major  (was: Critical)

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Major
> Attachments: 
> 0001-RANGER-3165-Upgrade-Elasticsearch-version-in-Ranger-.patch
>
>
> Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
> update the version to 7.17.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Review Request 73944: RANGER-3165: Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2

[bhavik patel]

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

Review request for ranger.


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


Repository: ranger


Description
---

Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
update the version to 7.17.2


Diffs
-

  
embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/ElasticSearchIndexBootStrapper.java
 15a16e41f 
  pom.xml 5afaa39ff 
  
ranger-elasticsearch-plugin-shim/src/main/java/org/apache/ranger/authorization/elasticsearch/plugin/RangerElasticsearchPlugin.java
 b196b0fa4 


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


Testing
---

Build is successfull and all the test-cases passed.

Not able to verify the funcionality as I dont have ES environment.


Thanks,

bhavik patel

[jira] [Updated] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3165:
-
Attachment: 0001-RANGER-3165-Upgrade-Elasticsearch-version-in-Ranger-.patch

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Critical
> Attachments: 
> 0001-RANGER-3165-Upgrade-Elasticsearch-version-in-Ranger-.patch
>
>
> Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
> update the version to 7.17.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3669) Connection to DB fails for MySQL version above 8.0

[Vishal Suvagia (Jira)]

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

Vishal Suvagia commented on RANGER-3669:


[~gomesnayagam] , lets say we have jdbc with some additional flags which we 
need to configure, in cases where need to add unicode and character-encoding 
support for the jdbc url.

in that case we can set the below in install.properties.
{noformat}
is_override_db_connection_string=true
db_override_connection_string=jdbc:mysql://localhost:3306/test?autoReconnect=trueuseUnicode=truecharacterEncoding=UTF-8
{noformat}
This jdbc url should now be used during setup for communication with DB

> Connection to DB fails for MySQL version above 8.0
> --
>
> Key: RANGER-3669
> URL: https://issues.apache.org/jira/browse/RANGER-3669
> Project: Ranger
>  Issue Type: Improvement
>  Components: kms
>Affects Versions: 3.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3669.01.patch, RANGER-3669.patch
>
>
> Observed that Ranger KMS DB setup fails when using with MySQL version above 
> 8.0.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3165:
-
Summary: Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2  
(was: Upgrade Elasticsearch version in Ranger to Elasticsearch 7.14.2)

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.17.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Critical
>
> Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
> update the version to 7.17.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.14.2

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3165:
-
Description: 
Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
update the version to 7.17.2

 

 

 

 

  was:Upgrade Elasticsearch version in Ranger to Elasticsearch 7.10.2


> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.14.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Critical
>
> Current ES version 7.6.0 affected with many CVE's issue, so it's better to 
> update the version to 7.17.2
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Assigned] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.10.2

[Bhavik Patel (Jira)]

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

Bhavik Patel reassigned RANGER-3165:


Assignee: Bhavik Patel

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.10.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Critical
>
> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.10.2



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (RANGER-3165) Upgrade Elasticsearch version in Ranger to Elasticsearch 7.14.2

[Bhavik Patel (Jira)]

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

Bhavik Patel updated RANGER-3165:
-
Summary: Upgrade Elasticsearch version in Ranger to Elasticsearch 7.14.2  
(was: Upgrade Elasticsearch version in Ranger to Elasticsearch 7.10.2)

> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.14.2
> ---
>
> Key: RANGER-3165
> URL: https://issues.apache.org/jira/browse/RANGER-3165
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: YangCheng
>Assignee: Bhavik Patel
>Priority: Critical
>
> Upgrade Elasticsearch version in Ranger to Elasticsearch 7.10.2



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (RANGER-3182) Prestosql is renamed to Trino

[rujia (Jira)]

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

rujia commented on RANGER-3182:
---

[~aakashnand] i can't find any define for commons.lang3.version in root pom, 
did u miss it?

> Prestosql is renamed to Trino
> -
>
> Key: RANGER-3182
> URL: https://issues.apache.org/jira/browse/RANGER-3182
> Project: Ranger
>  Issue Type: Improvement
>  Components: plugins
>Affects Versions: 2.1.0
>Reporter: Viacheslav Kriuchkov
>Priority: Blocker
> Attachments: 0001-RANGER-3182-Rename-Prestosql-to-Trino.patch, 
> ranger-commons-lang3-master.patch
>
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> All "prestosql" classes are "trino" now and Presto plugin can't integrate 
> with Trino because of that. It means all Presto deployments that use Ranger 
> are stuck on version 350 and can't upgrade further.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: Review Request 73935: RANGER-3669 : Connection to DB fails for MySQL version above 8.0

[Pradeep Agrawal]

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


Ship it!




Ship It!

- Pradeep Agrawal


On April 8, 2022, 10:57 a.m., Vishal Suvagia wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73935/
> ---
> 
> (Updated April 8, 2022, 10:57 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Dhaval Shah, Dineshkumar Yadav, 
> Gautam Borad, Jayendra Parab, Kishor Gollapalliwar, Abhay Kulkarni, Madhan 
> Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, 
> and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3669
> https://issues.apache.org/jira/browse/RANGER-3669
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ranger KMS db setup script needs to be updated to support MySql versions 
> greater than 8.0
> Made changes to allow non-ssl connection with DB for Mysql version greater 
> than 8.0
> made a fix to allow user to define the custom jdbc url which can be used in 
> db-setup.
> Added missing change for Ranger Admin db-setup in RANGER-3647
> 
> 
> Diffs
> -
> 
>   kms/scripts/db_setup.py 165e30d89443b7e8244ed965c34a5d7219e7d1f3 
>   kms/scripts/install.properties 780509dcdd06c13e84f1a860213eb28f3556fa26 
>   security-admin/scripts/db_setup.py eaae5c8990724d7ead703d747140a0c3c49289d7 
> 
> 
> Diff: https://reviews.apache.org/r/73935/diff/1/
> 
> 
> Testing
> ---
> 
> Validated changes locally with available Mysql-8.0 release.
> 
> 
> File Attachments
> 
> 
> RANGER-3669.01.patch
>   
> https://reviews.apache.org/media/uploaded/files/2022/04/08/48106a24-5c65-47d3-b971-7b69f5d7bb79__RANGER-3669.01.patch
> 
> 
> Thanks,
> 
> Vishal Suvagia
> 
>