[jira] [Updated] (RANGER-4763) Send user friendly message in Test Connection response if validateConfig is not implemented for the serviceDef

2024-04-03 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated RANGER-4763:
-
Fix Version/s: 3.0.0

> Send user friendly message in Test Connection response if validateConfig is 
> not implemented for the serviceDef
> --
>
> Key: RANGER-4763
> URL: https://issues.apache.org/jira/browse/RANGER-4763
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Anand Nadar
>Priority: Major
> Fix For: 3.0.0
>
>
> The "Test Connection" feature allows us to validate the configurations 
> mentioned for that particular service.
> If "Test Connection" is not implemented for a particular service definition, 
> which means that the service definition specific implementation is not 
> created which handles the configuration validation.
> If this is the case, then RangerDefaultService is used and the API GET 
> service/plugins/services/validateConfig sends the below response 
> {code:java}
> {"statusCode":1,"msgDesc":"","messageList":[{"message":""}]} {code}
> We should send an user-friendly message in this case, indicating that 
> "Configuration validation is not implemented" for that particular service.



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


[jira] [Updated] (RANGER-4764) GDS: When a dataset name is being modified, then the policy name of all the policies which is associated with dataset should also be updated.

2024-04-03 Thread Madhan Neethiraj (Jira)


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

Madhan Neethiraj updated RANGER-4764:
-
Fix Version/s: 3.0.0

> GDS: When a dataset name is being modified, then the policy name of all the 
> policies which is associated with dataset should also be updated. 
> --
>
> Key: RANGER-4764
> URL: https://issues.apache.org/jira/browse/RANGER-4764
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Anand Nadar
>Priority: Major
> Fix For: 3.0.0
>
>
> Suppose there exists a Dataset with name "Sales 2021". And it has a policy 
> giving access to some user. Then the policy which is being created will have 
> its name as 
> {code:java}
> "DATASET: " + dataset.getName() + "@" + System.currentTimeMillis() {code}
> So the dataset name will be "DATASET: Sales 2021@1699530693847".
> This policy name will be seen in the access audits when enforcement is done 
> using this policy.
> But now when the Dataset name is modified to "Sales US 2021", the policy name 
> remains "DATASET: Sales 2021@1699530693847" and whenever policy enforcement 
> is done, it will still show the policy name with old dataset name.
> Solution:
> To resolve this, we need to update all the policies associated with the 
> dataset when the dataset name is being modified.
> Similarly this needs to be done for project policy as well. When the project 
> name is modified, all policies associated with that project should be updated 
> with the new project name.



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


[jira] [Created] (RANGER-4767) Deleted policies are still taking effect if all policies in a repo are deleted

2024-04-03 Thread Abhishek (Jira)
Abhishek created RANGER-4767:


 Summary: Deleted policies are still taking effect if all policies 
in a repo are deleted
 Key: RANGER-4767
 URL: https://issues.apache.org/jira/browse/RANGER-4767
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Abhishek
Assignee: Abhay Kulkarni


If all the policies in a repo are deleted, then still the previous policies are 
taking effect.
If there are no policies in the repo, then the following error is seen in the 
logs
while syncing the policies, and the previously existing policies are still 
taking effect and operations are allowed through those policies
{code:java|bgColor=#f4f5f7}
2024-04-02T16:09:42.913ZERROR   
PolicyRefresher(serviceName=cm_trino)-233   
org.apache.ranger.plugin.service.RangerBasePlugin   setPolicies: policy 
engine initialization failed!  Leaving current policy engine as-is. Exception : 
java.lang.NullPointerException: Cannot invoke "java.util.List.iterator()" 
because "this.policies" is null
at 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository.init(RangerPolicyRepository.java:887)
at 
org.apache.ranger.plugin.policyengine.RangerPolicyRepository.(RangerPolicyRepository.java:229)
at 
org.apache.ranger.plugin.policyengine.PolicyEngine.(PolicyEngine.java:264)
at 
org.apache.ranger.plugin.policyengine.RangerPolicyEngineImpl.(RangerPolicyEngineImpl.java:104)
at 
org.apache.ranger.plugin.service.RangerBasePlugin.setPolicies(RangerBasePlugin.java:363)
at 
org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:264)
at 
org.apache.ranger.plugin.util.PolicyRefresher.run(PolicyRefresher.java:210) 
{code}



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


Re: Review Request 74949: RANGER-4763: Send user-friendly message if Test connection is not implemented for a service definition

2024-04-03 Thread Madhan Neethiraj

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


Fix it, then Ship it!





agents-common/src/main/java/org/apache/ranger/plugin/service/RangerDefaultService.java
Line 36 (original), 36 (patched)


Consider using a constant for the error message, to avoid multiple 
hardcoded instances across modules.


- Madhan Neethiraj


On April 3, 2024, 4:40 a.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74949/
> ---
> 
> (Updated April 3, 2024, 4:40 a.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4763
> https://issues.apache.org/jira/browse/RANGER-4763
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Send user-friendly message if Test connection is not implemented for a 
> service definition
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerDefaultService.java
>  c89b55757 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceMgr.java 
> 7e071ba0e 
>   security-admin/src/main/java/org/apache/ranger/common/TimedExecutor.java 
> d6fc01176 
> 
> 
> Diff: https://reviews.apache.org/r/74949/diff/2/
> 
> 
> Testing
> ---
> 
> Validated "Test Connection" when the service definition does not have 
> implClass, it gives the below response in this case.
> {
> "statusCode": 1,
> "msgDesc": "Configuration validation is not implemented for hbase",
> "messageList": [
> {
> "message": "Configuration validation is not implemented for hbase"
> }
> ]
> }
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: Review Request 74950: RANGER-4764: Update the policyName of associated policies when dataset/project name is modified

2024-04-03 Thread Madhan Neethiraj

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


Ship it!




Ship It!

- Madhan Neethiraj


On April 3, 2024, 7:54 a.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74950/
> ---
> 
> (Updated April 3, 2024, 7:54 a.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4764
> https://issues.apache.org/jira/browse/RANGER-4764
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When a dataset/project name is modified, then the policyName of all it's 
> associated policies should be modified.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> a1a2f9920 
> 
> 
> Diff: https://reviews.apache.org/r/74950/diff/2/
> 
> 
> Testing
> ---
> 
> Validated policy name change of associated policies when dataset/project name 
> is modified.
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: [PR] RANGER-4762:Prevent duplicate values for resource while validating policy [ranger]

2024-04-03 Thread via GitHub


fateh288 commented on PR #308:
URL: https://github.com/apache/ranger/pull/308#issuecomment-2035122830

   The changes have been merged : 
https://github.com/apache/ranger/commit/ffda775366ac8ac8a6869991dbab5e12d307a423


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] RANGER-4762:Prevent duplicate values for resource while validating policy [ranger]

2024-04-03 Thread via GitHub


fateh288 closed pull request #308: RANGER-4762:Prevent duplicate values for 
resource while validating policy
URL: https://github.com/apache/ranger/pull/308


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@ranger.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Community over Code EU 2024: Start planning your trip!

2024-04-03 Thread Ryan Skraba
[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

Dear community,

We hope you are doing great, are you ready for Community Over Code EU?
Check out the featured sessions, get your tickets with special
discounts and start planning your trip.

Save your spot! Take a look at our lineup of sessions, panelists and
featured speakers and make your final choice:

* EU policies and regulations affecting open source specialists working in OSPOs

The panel will discuss how EU legislation affects the daily work of
open source operations. Panelists will cover some recent policy
updates, the challenges of staying compliant when managing open source
contribution and usage within organizations, and their personal
experiences in adapting to the changing European regulatory
environment.

* Doing for sustainability, what open source did for software

In this keynote Asim Hussain will explain the history of Impact
Framework, a coalition of hundreds of software practitioners with
tangible solutions that directly foster meaningful change by measuring
the environmental impacts of a piece of software.

Don’t forget that we have special discounts for groups, students and
Apache committers. Visit the website to discover more about these
rates.[1]

It's time for you to start planning your trip. Remember that we have
prepared a “How to get there” guide that will be helpful to find out
the best transportation, either train, bus, flight or boat to
Bratislava from wherever you are coming from. Take a look at the
different options and please reach out to us if you have any
questions.

We have available rooms -with a special rate- at the Radisson Blu
Carlton Hotel, where the event will take place and at the Park Inn
Hotel which is only 5 minutes walking from the venue. [2] However, you
are free to choose any other accommodation options around the city.

See you in Bratislava,
Community Over Code EU Team

[1]: https://eu.communityovercode.org/tickets/ "Register"
[2]: https://eu.communityovercode.org/venue/ "Where to stay"


Re: Tagsync not working, documentation didn't help

2024-04-03 Thread Eckman, Barbara
In your case,  TAGSYNC_ATLAS_TO_RANGER_SERVICE_MAPPING should be “hive” –it’s 
the service name whose resources you want to map Atlas resources to


Thanks!

Barbara
--
Barbara Eckman, Ph.D.
she/her/hers
Distinguished Architect
Enterprise Metadata, Lineage and Access Control
Comcast
[signature_838192775]



From: Vijay Kumar Jangir 
Date: Wednesday, April 3, 2024 at 12:31 AM
To: u...@ranger.apache.org , dev@ranger.apache.org 

Subject: [EXTERNAL] Tagsync not working, documentation didn't help
Hi All,

I’m trying to setup apache ranger tagsync with atlas.

I see in multiple demos on youtube that atlas tags are automatically synced 
with ranger, however for me that’s not happening.

For my setup I have created a hive instance, added atlas hook and ranger plugin 
to it.

For tagsync install.properties, I’m not able to understand what should be the 
value of TAGSYNC_ATLAS_TO_RANGER_SERVICE_MAPPING

My setup is below:
Ranger:

  *   Hive service name: hive
  *   Atlas service name: atlas dev


I want to implement tag bsed service for Trino , and further I want to use 
datahub as a source for tags instead of atlas.

Any help here would be highly appreciated.

Thanks
***
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. If you are not the intended recipient you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited . The 
information contained in this mail is propriety and strictly confidential.
***


[jira] [Comment Edited] (RANGER-4764) GDS: When a dataset name is being modified, then the policy name of all the policies which is associated with dataset should also be updated.

2024-04-03 Thread Anand Nadar (Jira)


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

Anand Nadar edited comment on RANGER-4764 at 4/3/24 2:14 PM:
-

patch available for review :  [https://reviews.apache.org/r/74950/]


was (Author: JIRAUSER295963):
https://reviews.apache.org/r/74950/

> GDS: When a dataset name is being modified, then the policy name of all the 
> policies which is associated with dataset should also be updated. 
> --
>
> Key: RANGER-4764
> URL: https://issues.apache.org/jira/browse/RANGER-4764
> Project: Ranger
>  Issue Type: Task
>  Components: admin
>Reporter: Anand Nadar
>Assignee: Anand Nadar
>Priority: Major
>
> Suppose there exists a Dataset with name "Sales 2021". And it has a policy 
> giving access to some user. Then the policy which is being created will have 
> its name as 
> {code:java}
> "DATASET: " + dataset.getName() + "@" + System.currentTimeMillis() {code}
> So the dataset name will be "DATASET: Sales 2021@1699530693847".
> This policy name will be seen in the access audits when enforcement is done 
> using this policy.
> But now when the Dataset name is modified to "Sales US 2021", the policy name 
> remains "DATASET: Sales 2021@1699530693847" and whenever policy enforcement 
> is done, it will still show the policy name with old dataset name.
> Solution:
> To resolve this, we need to update all the policies associated with the 
> dataset when the dataset name is being modified.
> Similarly this needs to be done for project policy as well. When the project 
> name is modified, all policies associated with that project should be updated 
> with the new project name.



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


Participate in the ASF 25th Anniversary Campaign

2024-04-03 Thread Brian Proffitt
Hi everyone,

As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.

We invite all projects and contributors to participate in the following
ways:

* Individuals - submit your first contribution:
https://news.apache.org/foundation/entry/the-asf-launches-firstasfcontribution-campaign
* Projects - share your public good story:
https://docs.google.com/forms/d/1vuN-tUnBwpTgOE5xj3Z5AG1hsOoDNLBmGIqQHwQT6k8/viewform?edit_requested=true
* Projects - submit a project spotlight for the blog:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278466116
* Projects - contact the Voice of Apache podcast (formerly Feathercast) to
be featured: https://feathercast.apache.org/help/
*  Projects - use the 25th anniversary template and the #ASF25Years hashtag
on social media:
https://docs.google.com/presentation/d/1oDbMol3F_XQuCmttPYxBIOIjRuRBksUjDApjd8Ve3L8/edit#slide=id.g26b0919956e_0_13

If you have questions, email the Marketing & Publicity team at
mark...@apache.org.

Peace,
BKP

[1] https://apache.org/asf25years/

[NOTE: You are receiving this message because you are a contributor to an
Apache Software Foundation project. The ASF will very occasionally send out
messages relating to the Foundation to contributors and members, such as
this one.]

Brian Proffitt
VP, Marketing & Publicity
VP, Conferences


Re: Review Request 74950: RANGER-4764: Update the policyName of associated policies when dataset/project name is modified

2024-04-03 Thread Subhrat Chaudhary via Review Board

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


Ship it!




Ship It!

- Subhrat Chaudhary


On April 3, 2024, 1:24 p.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74950/
> ---
> 
> (Updated April 3, 2024, 1:24 p.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4764
> https://issues.apache.org/jira/browse/RANGER-4764
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When a dataset/project name is modified, then the policyName of all it's 
> associated policies should be modified.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> a1a2f9920 
> 
> 
> Diff: https://reviews.apache.org/r/74950/diff/2/
> 
> 
> Testing
> ---
> 
> Validated policy name change of associated policies when dataset/project name 
> is modified.
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: Review Request 74950: RANGER-4764: Update the policyName of associated policies when dataset/project name is modified

2024-04-03 Thread Anand Nadar

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

(Updated April 3, 2024, 7:54 a.m.)


Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika Kachhadiya, 
Siddhesh Phatak, and Subhrat Chaudhary.


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


Repository: ranger


Description
---

When a dataset/project name is modified, then the policyName of all it's 
associated policies should be modified.


Diffs (updated)
-

  security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java a1a2f9920 


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

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


Testing
---

Validated policy name change of associated policies when dataset/project name 
is modified.


Thanks,

Anand Nadar



Re: Review Request 74950: RANGER-4764: Update the policyName of associated policies when dataset/project name is modified

2024-04-03 Thread Anand Nadar


> On April 3, 2024, 7:41 a.m., Subhrat Chaudhary wrote:
> > security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java
> > Lines 183 (patched)
> > 
> >
> > We should update policy when dataset name has changed. Please review.
> 
> Anand Nadar wrote:
> I think only dataset name change has impact on a policy, as the policy 
> name contains the dataset name. Is there any other case where policy update 
> is needed?

okay understood, I need to add not


- Anand


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


On April 2, 2024, 12:51 p.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74950/
> ---
> 
> (Updated April 2, 2024, 12:51 p.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4764
> https://issues.apache.org/jira/browse/RANGER-4764
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When a dataset/project name is modified, then the policyName of all it's 
> associated policies should be modified.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> a1a2f9920 
> 
> 
> Diff: https://reviews.apache.org/r/74950/diff/1/
> 
> 
> Testing
> ---
> 
> Validated policy name change of associated policies when dataset/project name 
> is modified.
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: Review Request 74950: RANGER-4764: Update the policyName of associated policies when dataset/project name is modified

2024-04-03 Thread Anand Nadar


> On April 3, 2024, 7:41 a.m., Subhrat Chaudhary wrote:
> > security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java
> > Lines 183 (patched)
> > 
> >
> > We should update policy when dataset name has changed. Please review.

I think only dataset name change has impact on a policy, as the policy name 
contains the dataset name. Is there any other case where policy update is 
needed?


- Anand


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


On April 2, 2024, 12:51 p.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74950/
> ---
> 
> (Updated April 2, 2024, 12:51 p.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4764
> https://issues.apache.org/jira/browse/RANGER-4764
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When a dataset/project name is modified, then the policyName of all it's 
> associated policies should be modified.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> a1a2f9920 
> 
> 
> Diff: https://reviews.apache.org/r/74950/diff/1/
> 
> 
> Testing
> ---
> 
> Validated policy name change of associated policies when dataset/project name 
> is modified.
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: Review Request 74949: RANGER-4763: Send user-friendly message if Test connection is not implemented for a service definition

2024-04-03 Thread Subhrat Chaudhary via Review Board

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


Ship it!




Ship It!

- Subhrat Chaudhary


On April 3, 2024, 10:10 a.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74949/
> ---
> 
> (Updated April 3, 2024, 10:10 a.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4763
> https://issues.apache.org/jira/browse/RANGER-4763
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Send user-friendly message if Test connection is not implemented for a 
> service definition
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/service/RangerDefaultService.java
>  c89b55757 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceMgr.java 
> 7e071ba0e 
>   security-admin/src/main/java/org/apache/ranger/common/TimedExecutor.java 
> d6fc01176 
> 
> 
> Diff: https://reviews.apache.org/r/74949/diff/2/
> 
> 
> Testing
> ---
> 
> Validated "Test Connection" when the service definition does not have 
> implClass, it gives the below response in this case.
> {
> "statusCode": 1,
> "msgDesc": "Configuration validation is not implemented for hbase",
> "messageList": [
> {
> "message": "Configuration validation is not implemented for hbase"
> }
> ]
> }
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: Review Request 74950: RANGER-4764: Update the policyName of associated policies when dataset/project name is modified

2024-04-03 Thread Subhrat Chaudhary via Review Board

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




security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java
Lines 183 (patched)


We should update policy when dataset name has changed. Please review.


- Subhrat Chaudhary


On April 2, 2024, 6:21 p.m., Anand Nadar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74950/
> ---
> 
> (Updated April 2, 2024, 6:21 p.m.)
> 
> 
> Review request for ranger, Asit Vadhavkar, Madhan Neethiraj, Monika 
> Kachhadiya, Siddhesh Phatak, and Subhrat Chaudhary.
> 
> 
> Bugs: RANGER-4764
> https://issues.apache.org/jira/browse/RANGER-4764
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When a dataset/project name is modified, then the policyName of all it's 
> associated policies should be modified.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/biz/GdsDBStore.java 
> a1a2f9920 
> 
> 
> Diff: https://reviews.apache.org/r/74950/diff/1/
> 
> 
> Testing
> ---
> 
> Validated policy name change of associated policies when dataset/project name 
> is modified.
> 
> 
> Thanks,
> 
> Anand Nadar
> 
>



Re: Review Request 74259: RANGER-3998: Support Ranger KMS integration with AWS KMS

2024-04-03 Thread Dhaval Shah

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



Hi Kirby,

As mentioned in Apache Jira,
Can you please share the documentation link for this feature.

Thanks

- Dhaval Shah


On March 23, 2024, 2:20 a.m., Kirby Zhou wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74259/
> ---
> 
> (Updated March 23, 2024, 2:20 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Gautam Borad, 
> Jayendra Parab, Kishor Gollapalliwar, Abhay Kulkarni, Mateen Mansoori, Mehul 
> Parikh, Pradeep Agrawal, VaradreawiZTV VaradreawiZTV, Vishal Suvagia, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: ranger-3998
> https://issues.apache.org/jira/browse/ranger-3998
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> AWS KMS is widely used by many customers.
> Therefore, RangerKMS should support hosting MasterKey to AWS KMS.
> 
> 
> Diffs
> -
> 
>   distro/src/main/assembly/kms.xml 77f61b917 
>   kms/config/kms-webapp/dbks-site.xml 258d331d8 
>   kms/pom.xml 0b37ce52d 
>   kms/scripts/install.properties 5f5df9b1f 
>   kms/scripts/setup.sh 0cce478fd 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerAWSKMSProvider.java 
> PRE-CREATION 
>   kms/src/main/java/org/apache/hadoop/crypto/key/RangerKeyStoreProvider.java 
> 429d1ce45 
>   
> kms/src/main/java/org/apache/hadoop/crypto/key/RangerTencentKMSProvider.java 
> 1f0125967 
> 
> 
> Diff: https://reviews.apache.org/r/74259/diff/8/
> 
> 
> Testing
> ---
> 
> Tested under macos-13 and centos-8
> 
> 
> File Attachments
> 
> 
> 0001-RANGER-3998-KMS-integration-with-AWS-KMS.patch
>   
> https://reviews.apache.org/media/uploaded/files/2023/04/07/6499bf0e-af49-4eae-8636-f183f0fab3d7__0001-RANGER-3998-KMS-integration-with-AWS-KMS.patch
> 
> 
> Thanks,
> 
> Kirby Zhou
> 
>