[jira] [Commented] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei commented on RANGER-3637:
--

[~kirbyzhou] I found the root reason of the NullPointerException, when 
plugins's debug opened,policy update failed，beause  auditPolicyEvaluators never 
be newed before  init(options) functions,  Swap the order of the two modules 
will fix the bug.  patch:RANGER-3637.003.patch

!image-2022-02-24-15-11-26-819.png|width=493,height=119!

 

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch, RANGER-3637.002.patch, 
> RANGER-3637.003.patch, image-2022-02-24-15-11-26-819.png
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Updated] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei updated RANGER-3637:
-
Attachment: image-2022-02-24-15-11-26-819.png

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch, RANGER-3637.002.patch, 
> RANGER-3637.003.patch, image-2022-02-24-15-11-26-819.png
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Updated] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei updated RANGER-3637:
-
Attachment: RANGER-3637.003.patch

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch, RANGER-3637.002.patch, 
> RANGER-3637.003.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Updated] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei updated RANGER-3637:
-
Attachment: RANGER-3637.002.patch

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch, RANGER-3637.002.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

Re: Review Request 73863: RANGER-3638: Solr Ranger document level security breaks solr if collection is reloaded

[Abhay Kulkarni]

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




ranger-solr-plugin-shim/src/main/java/org/apache/ranger/authorization/solr/authorizer/RangerSolrAuthorizer.java
Lines 144 (patched)


Is this a misplaced comment, which needs to be before line 134?


- Abhay Kulkarni


On Feb. 24, 2022, 2:12 a.m., Sailaja Polavarapu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73863/
> ---
> 
> (Updated Feb. 24, 2022, 2:12 a.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Mateen Mansoori, Mehul Parikh, and 
> Ramesh Mani.
> 
> 
> Bugs: RANGER-3638
> https://issues.apache.org/jira/browse/RANGER-3638
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RangerSolrAuthorizer is a common implementation call for both SearchComponent 
> (for Document level Authorization) and AuthorizationPlugin (for collection 
> level Authorization). RangerSolrAuthorizer implementation close() shutdowns 
> the plugin and should be avoided when the call is for SearchComponent. Added 
> check to get the authorizer class name to determine if the call is for 
> SearchComponent of for the authorization plugin.
> 
> 
> Diffs
> -
> 
>   
> ranger-solr-plugin-shim/src/main/java/org/apache/ranger/authorization/solr/authorizer/RangerSolrAuthorizer.java
>  dfa219670 
> 
> 
> Diff: https://reviews.apache.org/r/73863/diff/1/
> 
> 
> Testing
> ---
> 
> 1. Patched cluster with the changes and verified the end to end functionality 
> with and without Document level authorization
> 2. Verified basic functional tests and audits for regression testing.
> 
> 
> Thanks,
> 
> Sailaja Polavarapu
> 
>

[jira] [Updated] (RANGER-3638) Solr Ranger document level security breaks solr if collection is reloaded

[Sailaja Polavarapu (Jira)]

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

Sailaja Polavarapu updated RANGER-3638:
---
Attachment: 0001-RANGER-3638-Avoid-calling-rangerSolrAuthorizerImpl-c.patch

> Solr Ranger document level security breaks solr if collection is reloaded
> -
>
> Key: RANGER-3638
> URL: https://issues.apache.org/jira/browse/RANGER-3638
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Sailaja Polavarapu
>Assignee: Sailaja Polavarapu
>Priority: Major
> Attachments: 
> 0001-RANGER-3638-Avoid-calling-rangerSolrAuthorizerImpl-c.patch
>
>
> Solr stops working if using a collection with document level security enabled 
> when:
> adding fields to collection schema
> making changes to collection config
> reloading collection
> This does not happens if the reload is done to the non document level 
> security collection, with other collection with document level security.
> -solr can no longer send ranger audits to solr-infra showing 403 errror from 
> solr-infra
> -solr can no longer save audits to hdfs showing issue with the hdfs sink.
> -solr answer 403 to any query to the collection with document level security 
> and other collections, admin commands too
> -zookeeper znodes warnings are seen on the logs.
> After solr restart all collections with and without document level security 
> are available again and answer queries.



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

Review Request 73863: RANGER-3638: Solr Ranger document level security breaks solr if collection is reloaded

[Sailaja Polavarapu]

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

Review request for ranger, Abhay Kulkarni, Mateen Mansoori, Mehul Parikh, and 
Ramesh Mani.


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


Repository: ranger


Description
---

RangerSolrAuthorizer is a common implementation call for both SearchComponent 
(for Document level Authorization) and AuthorizationPlugin (for collection 
level Authorization). RangerSolrAuthorizer implementation close() shutdowns the 
plugin and should be avoided when the call is for SearchComponent. Added check 
to get the authorizer class name to determine if the call is for 
SearchComponent of for the authorization plugin.


Diffs
-

  
ranger-solr-plugin-shim/src/main/java/org/apache/ranger/authorization/solr/authorizer/RangerSolrAuthorizer.java
 dfa219670 


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


Testing
---

1. Patched cluster with the changes and verified the end to end functionality 
with and without Document level authorization
2. Verified basic functional tests and audits for regression testing.


Thanks,

Sailaja Polavarapu

[jira] [Commented] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei commented on RANGER-3637:
--

[~kirbyzhou] thanks for your suggestion，I will  create a review request and 
give the reason for the NullPointerException

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Created] (RANGER-3638) Solr Ranger document level security breaks solr if collection is reloaded

[Sailaja Polavarapu (Jira)]

Sailaja Polavarapu created RANGER-3638:
--

 Summary: Solr Ranger document level security breaks solr if 
collection is reloaded
 Key: RANGER-3638
 URL: https://issues.apache.org/jira/browse/RANGER-3638
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 2.2.0
Reporter: Sailaja Polavarapu


Solr stops working if using a collection with document level security enabled 
when:
adding fields to collection schema
making changes to collection config
reloading collection
This does not happens if the reload is done to the non document level security 
collection, with other collection with document level security.

-solr can no longer send ranger audits to solr-infra showing 403 errror from 
solr-infra
-solr can no longer save audits to hdfs showing issue with the hdfs sink.
-solr answer 403 to any query to the collection with document level security 
and other collections, admin commands too
-zookeeper znodes warnings are seen on the logs.

After solr restart all collections with and without document level security are 
available again and answer queries.



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

[jira] [Assigned] (RANGER-3638) Solr Ranger document level security breaks solr if collection is reloaded

[Sailaja Polavarapu (Jira)]

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

Sailaja Polavarapu reassigned RANGER-3638:
--

Assignee: Sailaja Polavarapu

> Solr Ranger document level security breaks solr if collection is reloaded
> -
>
> Key: RANGER-3638
> URL: https://issues.apache.org/jira/browse/RANGER-3638
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 2.2.0
>Reporter: Sailaja Polavarapu
>Assignee: Sailaja Polavarapu
>Priority: Major
>
> Solr stops working if using a collection with document level security enabled 
> when:
> adding fields to collection schema
> making changes to collection config
> reloading collection
> This does not happens if the reload is done to the non document level 
> security collection, with other collection with document level security.
> -solr can no longer send ranger audits to solr-infra showing 403 errror from 
> solr-infra
> -solr can no longer save audits to hdfs showing issue with the hdfs sink.
> -solr answer 403 to any query to the collection with document level security 
> and other collections, admin commands too
> -zookeeper znodes warnings are seen on the logs.
> After solr restart all collections with and without document level security 
> are available again and answer queries.



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

[jira] [Commented] (RANGER-3637) setpolicies failed because of NullPointerException

[kirby zhou (Jira)]

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

kirby zhou commented on RANGER-3637:


And your patch is buggy, it even cannot be compiled.

Please check line like "order = 0;" without var definition.

 

Another question, Why NullPointerException happens? It should be inited in 
somewhere, you should given the reason why we need to ignore the 
NullPointerException here instead of fix the root reason why something is null.

 

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Commented] (RANGER-3637) setpolicies failed because of NullPointerException

[kirby zhou (Jira)]

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

kirby zhou commented on RANGER-3637:


You should create a review request here: 
[http://reviews.apache.org|http://reviews.apache.org/]

Using git format-patch --full-index

 

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

Re: Review Request 73857: Improve ranger log system, add RENAME_ON_ROTATE to access_log, fix some remains of log4j

[bhavik patel]

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


Ship it!




Ship It!

- bhavik patel


On Feb. 21, 2022, 4:31 a.m., Kirby Zhou wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73857/
> ---
> 
> (Updated Feb. 21, 2022, 4:31 a.m.)
> 
> 
> Review request for ranger and madhan.
> 
> 
> Bugs: RANGER-3632
> https://issues.apache.org/jira/browse/RANGER-3632
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> 1. add options of access_log
> 
> # set it to false will disable log rotation
> ranger.accesslog.rotate.enabled = true on default
> # set it to true will result in the current access log name without 
> dateformat.
> ranger.accesslog.rotate.rename_on_rotate = false on default
> 
> 2. rename max.days to max_days, make the name look more comfortable
> ranger.accesslog.rotate.max.days = 15
> 
> 3. move "-" from default prefix to default dateformat
> # It can helps for using access log name without dateformat
>   valve.setPrefix(EmbeddedServerUtil.getConfig(ACCESS_LOG_PREFIX,"access-" + 
> hostName));
>   
> valve.setFileDateFormat(EmbeddedServerUtil.getConfig(ACCESS_LOG_DATE_FORMAT, 
> "--MM-dd.HH"));
> 
> 4. mv ews/webapp/WEB-INF/logback.xml to ews/webapp/WEB-INF/classes/conf[.dist]
> # It can helps person to adjust log options easier.
> 
> 5. add "%D" to default access-log
> # It can help admins to get timecost from access-log instead of expansive 
> perf log.
> 
> 6. fix a lot of log4j name remains to logback.
> 
> 
> Diffs
> -
> 
>   dev-support/ranger-docker/scripts/ranger-admin-install.properties 
> f4e623c5aa2865e29e756359eb9a2c4f33f58e36 
>   embeddedwebserver/scripts/ranger-admin-services.sh 
> 54ac410561a34f069c2f62e8a5d2467de4e43bed 
>   
> embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/EmbeddedServer.java
>  93ba6c0f936e9306336d42075f8566e009347367 
>   
> embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/EmbeddedServerUtil.java
>  b05db77e6acbf7c11631c3feae1b660d522e1ea5 
>   ranger-tools/scripts/README.txt 81b5b6678174dd9da79aa083fbe4b73ce8e4bc94 
>   security-admin/scripts/changepasswordutil.py 
> d53cde44378306a3b104d4e6d42c56b5dc7ccbcf 
>   security-admin/scripts/changeusernameutil.py 
> 0c20bb6ed4f535365986555ba24d6a1531fc3392 
>   security-admin/scripts/db_setup.py 5e757aca30d01c244b5b0e4efa356b11c65aa7aa 
>   security-admin/scripts/install.properties 
> 03f6cd7f6f98657ed12ed0f6ccc51bacdbd3afd5 
>   security-admin/scripts/rolebasedusersearchutil.py 
> 500aa624fa12d216e3fca1c58404b6100cafcb8c 
>   security-admin/scripts/setup.sh 583b270a3068246a8be9824dac3ab0655992c9c1 
>   security-admin/scripts/updateUserAndGroupNamesInJson.py 
> 02d95d7816df28dc900fed73522e2e53dbfbd665 
>   security-admin/src/bin/ranger_install.py 
> 90ac92a0ea2abf60aadbdcad5054e843a5d90530 
>   security-admin/src/main/resources/conf.dist/ranger-admin-default-site.xml 
> 0a1128613dca50fe67ea3f891261f1ee449c46db 
>   security-admin/src/main/webapp/WEB-INF/db_patch.log4j.xml  
>   security-admin/src/main/webapp/WEB-INF/log4j.dev.xml 
> 45ca9237f77c1130caaa5e08f3058ecc7e636a0b 
>   security-admin/src/main/webapp/WEB-INF/log4j.xml 
> 359ed93600947d21d5f4d1ee3779e6e3b8213ce2 
>   security-admin/src/main/webapp/WEB-INF/logback.xml  
>   security-admin/src/test/resources/log4j.xml 
> 15ae2741c37e02f55bfb3546f21c71c9b0036260 
>   tagsync/conf.dist/log4j.xml d455509326bfe6f598a48ee6e3f2a4b0d5f621e7 
>   tagsync/scripts/setup.py 29ad7fa885697534748b76187070a4ffa177633f 
>   unixauthservice/conf.dist/log4j.xml 
> 0ef266bfd942181d7cf766bd40e5ce02b8a6be7a 
>   unixauthservice/scripts/setup.py 9639eb4254cb465882144b03cec859f6a0ae98b5 
> 
> 
> Diff: https://reviews.apache.org/r/73857/diff/2/
> 
> 
> Testing
> ---
> 
> mvn package
> clean installation and upgrade.
> 
> 
> Thanks,
> 
> Kirby Zhou
> 
>

[jira] [Commented] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei commented on RANGER-3637:
--

can someone help to review this patch?

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

[ https://issues.apache.org/jira/browse/RANGER-3637 ]


wangzhongwei deleted comment on RANGER-3637:
--

was (Author: JIRAUSER285670):
can someone  assign  this issue to me?

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Updated] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei updated RANGER-3637:
-
Attachment: RANGER-3637.001.patch

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
> Attachments: RANGER-3637.001.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Commented] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei commented on RANGER-3637:
--

can someone  assign  this issue to me?

> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
> evaluation order: 0 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter 
> policy evaluation order: 0 policies
> 2022-02-22 16:32:06,200 ERROR 
> org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
> initialization failed!  Leaving current policy engine as-is. Exception :
> java.lang.NullPointerException
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
>         at 
> org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
>         at 
> org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
>         at 
> org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
>         at 
> org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
> @                                                                             
>              
>  
>  



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

[jira] [Updated] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei updated RANGER-3637:
-
Description: 
when use ranger hdfs plugins ,update policies and save the policies ,sometimes 
failed because of the NullPointerException,like the same issue as 
RANGER-3108,but we should

make a non-empty judgment on  all 3 
lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators 

issue log:

2022-02-22 16:32:06,200 INFO 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
engine contains 4 policy evaluators
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy evaluation 
order: 4 policies
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy evaluation 
order: #1 - policy id=1; name=all - path; evalOrder=9933
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy evaluation 
order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy evaluation 
order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy evaluation 
order: #4 - policy id=5; name=test2; evalOrder=9952
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: dataMask policy 
evaluation order: 0 policies
2022-02-22 16:32:06,200 DEBUG 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository: rowFilter policy 
evaluation order: 0 policies
2022-02-22 16:32:06,200 ERROR 
org.apache.ranger.plugin.service.RangerBasePlugin: setPolicies: policy engine 
initialization failed!  Leaving current policy engine as-is. Exception :
java.lang.NullPointerException
        at 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:991)
        at 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
        at 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:180)
        at 
org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:212)
        at 
org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
        at 
org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:325)
        at 
org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:263)
        at 
org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:209)
@                                                                               
           

 

 

  was:
when use ranger hdfs plugins ,update policies and save the policies ,sometimes 
failed because of the NullPointerException,like the same issue as 
RANGER-3108,but we should

make a non-empty judgment on  all 3 
lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators 

 

 


> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
> issue log:
> 2022-02-22 16:32:06,200 INFO 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: This policy 
> engine contains 4 policy evaluators
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: 4 policies
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #1 - policy id=1; name=all - path; evalOrder=9933
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #2 - policy id=2; name=kms-audit-path; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #3 - policy id=3; name=hbase-archive; evalOrder=9944
> 2022-02-22 16:32:06,200 DEBUG 
> org.apache.ranger.plugin.policyengine.RangerPolicyRepository: policy 
> evaluation order: #4 - policy id=5; name=test2; evalOrder=9952
> 2022-02-22 16:32:06,200 

[jira] [Updated] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

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

wangzhongwei updated RANGER-3637:
-
Description: 
when use ranger hdfs plugins ,update policies and save the policies ,sometimes 
failed because of the NullPointerException,like the same issue as 
RANGER-3108,but we should

make a non-empty judgment on  all 3 
lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators 

 

 

  was:
when use ranger hdfs plugins ,update policies and save the policies ,sometimes 
failed because of the NullPointerException,like the same issue as 
RANGER-3108,but we should

make a non-empty judgment on  all 3 
lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators 

!image-2022-02-23-18-26-04-456.png|width=486,height=103!

 


> setpolicies failed because of NullPointerException
> --
>
> Key: RANGER-3637
> URL: https://issues.apache.org/jira/browse/RANGER-3637
> Project: Ranger
>  Issue Type: Bug
>  Components: plugins
>Affects Versions: 2.2.0
> Environment: centos7 java1.8
>Reporter: wangzhongwei
>Priority: Major
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> when use ranger hdfs plugins ,update policies and save the policies 
> ,sometimes failed because of the NullPointerException,like the same issue as 
> RANGER-3108,but we should
> make a non-empty judgment on  all 3 
> lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators
>  
>  
>  



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

[jira] [Created] (RANGER-3637) setpolicies failed because of NullPointerException

[wangzhongwei (Jira)]

wangzhongwei created RANGER-3637:


 Summary: setpolicies failed because of NullPointerException
 Key: RANGER-3637
 URL: https://issues.apache.org/jira/browse/RANGER-3637
 Project: Ranger
  Issue Type: Bug
  Components: plugins
Affects Versions: 2.2.0
 Environment: centos7 java1.8
Reporter: wangzhongwei


when use ranger hdfs plugins ,update policies and save the policies ,sometimes 
failed because of the NullPointerException,like the same issue as 
RANGER-3108,but we should

make a non-empty judgment on  all 3 
lists:dataMaskPolicyEvaluators,rowFilterPolicyEvaluators,auditPolicyEvaluators 

!image-2022-02-23-18-26-04-456.png|width=486,height=103!

 



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

[jira] [Updated] (RANGER-3615) Issue with exported audit json builder while writing events to log4j

[Dhaval Shah (Jira)]

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

Dhaval Shah updated RANGER-3615:

Fix Version/s: 3.0.0

> Issue with exported audit json builder while writing events to log4j
> 
>
> Key: RANGER-3615
> URL: https://issues.apache.org/jira/browse/RANGER-3615
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Dhaval Shah
>Assignee: Dhaval Shah
>Priority: Major
> Fix For: 3.0.0
>
>
> Ref Doc: 
> https://blog.cloudera.com/auditing-to-external-systems-in-cdp-private-cloud-base/
> Here's the example:
> {code:java}
> {"repoType":3,"repo":"hive","reqUser":"systest","evtTime":"2022-01-20 
> 12:56:31.909","access":"USE","resource":"default","resType":"@database","action":"_any","result":1,"agent":"hiveServer2","policy":14,"enforcer":"ranger-acl","sess":"e162e0ad-717b-4934-9a50-6915de2268c3","cliType":"HIVESERVER2","cliIP":"172.27.27.131","reqData":"show
>  
> tables","agentHost":"pravinknox-2.pravinknox.root.site","logType":"RangerAudit","id":"d8c7d941-26b7-4390-85dd-4a51e716ae40-0","seq_num":1,"event_count":1,"event_dur_ms":1,"additional_info":"{\"remote-ip-address\":172.27.27.131,
>  \"forwarded-ip-addresses\":[]","cluster_name":"Cluster 
> 1","policy_version":1} 
> {code}
> Found some issue parsing the log due to a json format error there are 
> basically missing a '}' at the end of addition_info.
> Code Ref: 
> https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/audit/RangerDefaultAuditHandler.java#L270



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

[jira] [Commented] (RANGER-3615) Issue with exported audit json builder while writing events to log4j

[Dhaval Shah (Jira)]

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

Dhaval Shah commented on RANGER-3615:
-

Commits:

master : 
https://github.com/apache/ranger/commit/227c45b5ccea6d9d0d546c1882a805b0f0b7b617

ranger-2.3 :
https://github.com/apache/ranger/commit/fb764e6910830f138ab1513b65f7689599ff0307

Thanks

> Issue with exported audit json builder while writing events to log4j
> 
>
> Key: RANGER-3615
> URL: https://issues.apache.org/jira/browse/RANGER-3615
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Dhaval Shah
>Assignee: Dhaval Shah
>Priority: Major
>
> Ref Doc: 
> https://blog.cloudera.com/auditing-to-external-systems-in-cdp-private-cloud-base/
> Here's the example:
> {code:java}
> {"repoType":3,"repo":"hive","reqUser":"systest","evtTime":"2022-01-20 
> 12:56:31.909","access":"USE","resource":"default","resType":"@database","action":"_any","result":1,"agent":"hiveServer2","policy":14,"enforcer":"ranger-acl","sess":"e162e0ad-717b-4934-9a50-6915de2268c3","cliType":"HIVESERVER2","cliIP":"172.27.27.131","reqData":"show
>  
> tables","agentHost":"pravinknox-2.pravinknox.root.site","logType":"RangerAudit","id":"d8c7d941-26b7-4390-85dd-4a51e716ae40-0","seq_num":1,"event_count":1,"event_dur_ms":1,"additional_info":"{\"remote-ip-address\":172.27.27.131,
>  \"forwarded-ip-addresses\":[]","cluster_name":"Cluster 
> 1","policy_version":1} 
> {code}
> Found some issue parsing the log due to a json format error there are 
> basically missing a '}' at the end of addition_info.
> Code Ref: 
> https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/audit/RangerDefaultAuditHandler.java#L270



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

Re: Review Request 73860: RANGER-3615 : Issue with exported audit json builder while writing events to log4j

[Mehul Parikh]

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


Ship it!




Ship It!

- Mehul Parikh


On Feb. 23, 2022, 5:47 a.m., Dhaval Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73860/
> ---
> 
> (Updated Feb. 23, 2022, 5:47 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, bhavik patel, Dineshkumar Yadav, 
> Jayendra Parab, Kishore Gopalakrishna, Abhay Kulkarni, madhan, Mahesh Bandal, 
> Mehul Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-3615
> https://issues.apache.org/jira/browse/RANGER-3615
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Ref Doc:
> 
> https://blog.cloudera.com/auditing-to-external-systems-in-cdp-private-cloud-base/
> 
> Here's the example:
> 
> {"repoType":3,"repo":"hive","reqUser":"systest","evtTime":"2022-01-20 
> 12:56:31.909","access":"USE","resource":"default","resType":"@database","action":"_any","result":1,"agent":"hiveServer2","policy":14,"enforcer":"ranger-acl","sess":"e162e0ad-717b-4934-9a50-6915de2268c3","cliType":"HIVESERVER2","cliIP":"172.27.27.131","reqData":"show
>  
> tables","agentHost":"pravinknox-2.pravinknox.root.site","logType":"RangerAudit","id":"d8c7d941-26b7-4390-85dd-4a51e716ae40-0","seq_num":1,"event_count":1,"event_dur_ms":1,"additional_info":"{\"remote-ip-address\":172.27.27.131,
>  \"forwarded-ip-addresses\":[]","cluster_name":"Cluster 
> 1","policy_version":1} 
> 
> Found some issue parsing the log due to a json format error there are 
> basically missing a '}' at the end of addition_info.
> 
> Code Ref:
> 
> https://github.com/apache/ranger/blob/master/agents-common/src/main/java/org/apache/ranger/plugin/audit/RangerDefaultAuditHandler.java#L270
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/audit/RangerDefaultAuditHandler.java
>  838cfada3 
>   
> hdfs-agent/src/main/java/org/apache/ranger/authorization/hadoop/RangerHdfsAuthorizer.java
>  8940f36c0 
> 
> 
> Diff: https://reviews.apache.org/r/73860/diff/1/
> 
> 
> Testing
> ---
> 
> 1.) Build Succeeded with test cases.
> 2.) Validataed audit JSON for hdfs , hive services.
> 
> 
> Thanks,
> 
> Dhaval Shah
> 
>

Re: Review Request 73859: RANGER-3634: Remove duplicate entries from usersync distribution file

[Dhaval Shah]

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


Ship it!




Ship It!

- Dhaval Shah


On Feb. 21, 2022, 10:25 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73859/
> ---
> 
> (Updated Feb. 21, 2022, 10:25 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kishor 
> Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mateen Mansoori, Mehul 
> Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-3634
> https://issues.apache.org/jira/browse/RANGER-3634
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Remove duplicate entries from usersync distribution file
> 
> 
> Diffs
> -
> 
>   distro/src/main/assembly/usersync.xml e1c4b1b16 
> 
> 
> Diff: https://reviews.apache.org/r/73859/diff/1/
> 
> 
> Testing
> ---
> 
> Required jar files are present in respective dir "{home}/lib"
> 
> 
> Thanks,
> 
> bhavik patel
> 
>

Re: Review Request 73847: RANGER-3624: Update-Ranger-services-Password-Policy

[Dhaval Shah]

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


Ship it!




Ship It!

- Dhaval Shah


On Feb. 21, 2022, 6:58 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/73847/
> ---
> 
> (Updated Feb. 21, 2022, 6:58 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Kishor 
> Gollapalliwar, Abhay Kulkarni, Madhan Neethiraj, Mateen Mansoori, Mehul 
> Parikh, Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-3624
> https://issues.apache.org/jira/browse/RANGER-3624
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Current Password policies(validation) is not strong enough as it expect the 
> "minimum 8 characters with minimum one alphabet and one numeric".
> 
> In this improvement Jira will enhance the password policies to "minimum 8 
> characters, at least one uppercase letter, one lowercase letter and one 
> numeric"
> 
> 
> Diffs
> -
> 
>   security-admin/scripts/setup.sh 583b270a3 
> 
> 
> Diff: https://reviews.apache.org/r/73847/diff/1/
> 
> 
> Testing
> ---
> 
> Verified many password combination for Valid/Non-valid case.
> 
> 1.Valid paswords 
> - Admin@123
> - aDmin@123
> 
> 2.Invalid paswords
> - admin@123
> - ADMIN@123
> 
> 
> Thanks,
> 
> bhavik patel
> 
>