[jira] [Commented] (RANGER-4441) Upgrade maven compiler plugin to 3.5

[Bhavik Patel (Jira)]

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

Bhavik Patel commented on RANGER-4441:
--

Can someone review the patch?

> Upgrade maven compiler plugin to 3.5
> 
>
> Key: RANGER-4441
> URL: https://issues.apache.org/jira/browse/RANGER-4441
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Bhavik Patel
>Assignee: Bhavik Patel
>Priority: Major
> Attachments: 
> 0001-RANGER-4441-Upgrade-maven-compiler-plugin-to-3.5.patch
>
>
> Upgrade maven compiler plugin to 3.5 and current version 3.3 tried to 
> download log4j-1.2 jar. 



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

[jira] [Updated] (RANGER-4347) User name with comma split in old Ranger admin UI

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav updated RANGER-4347:
--
Fix Version/s: 3.0.0

> User name with comma split in old Ranger admin UI
> -
>
> Key: RANGER-4347
> URL: https://issues.apache.org/jira/browse/RANGER-4347
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-RANGER-4347-User-name-with-comma-split-in-old-Ranger.patch
>
>
> when using Ranger Audit filter to filter out the audit for a specific user:
> Usually, if we input a username, it would be no issue, but if we input the 
> user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”.
> We found that once we saved the audit filter policy, the user was split into 
> “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com”
> It happens because Ranger UI recognize “,” to be separate items.
> Same scenario is present in :
> 1) Security Zone Form 
> 2) Permission modules
> 3) Role Form



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

[jira] [Commented] (RANGER-4347) User name with comma split in old Ranger admin UI

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav commented on RANGER-4347:
---

Apache Master 
:https://github.com/apache/ranger/commit/39479100fdaafaf6360e4648b8048280669116eb

> User name with comma split in old Ranger admin UI
> -
>
> Key: RANGER-4347
> URL: https://issues.apache.org/jira/browse/RANGER-4347
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-RANGER-4347-User-name-with-comma-split-in-old-Ranger.patch
>
>
> when using Ranger Audit filter to filter out the audit for a specific user:
> Usually, if we input a username, it would be no issue, but if we input the 
> user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”.
> We found that once we saved the audit filter policy, the user was split into 
> “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com”
> It happens because Ranger UI recognize “,” to be separate items.
> Same scenario is present in :
> 1) Security Zone Form 
> 2) Permission modules
> 3) Role Form



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

Re: Review Request 74572: RANGER-4347 : User name with comma split in old Ranger admin UI

[Dineshkumar Yadav]

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


Ship it!




Ship It!

- Dineshkumar Yadav


On Nov. 22, 2023, 5:21 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74572/
> ---
> 
> (Updated Nov. 22, 2023, 5:21 a.m.)
> 
> 
> Review request for ranger, Dhaval Shah, Dineshkumar Yadav, Harshal Chavan, 
> Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, Nitin 
> Galave, Pradeep Agrawal, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4347
> https://issues.apache.org/jira/browse/RANGER-4347
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> when using Ranger Audit filter to filter out the audit for a specific user:
> Usually, if we input a username, it would be no issue, but if we input the 
> user like: “CN=SZH-C-004VX,CN=Machine,CN=PKI,DC=Bosch,DC=com”.
> We found that once we saved the audit filter policy, the user was split into 
> “CN=SZH-C-004VX”, “CN=Machine”, “CN=PKI”, “DC=Bosch”, “DC=com”
> It happens because Ranger UI recognize “,” to be separate items.
> 
> Same scenario is present in :
> 1) Security Zone Form
> 2) Permission modules
> 3) Role Form
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/libs/fsOverrides/BBFOverrides.js 469f4aa9c 
>   security-admin/src/main/webapp/scripts/models/RangerZone.js 08d118132 
>   security-admin/src/main/webapp/scripts/utils/XAUtils.js 3c5907099 
>   
> security-admin/src/main/webapp/scripts/views/permissions/ModulePermissionForm.js
>  7b8c4c809 
>   security-admin/src/main/webapp/scripts/views/policies/RangerPolicyForm.js 
> 118dfe215 
>   security-admin/src/main/webapp/scripts/views/reports/UserAccessLayout.js 
> ebdd2a0b2 
>   security-admin/src/main/webapp/scripts/views/security_zone/ZoneCreate.js 
> a4885e379 
>   
> security-admin/src/main/webapp/scripts/views/security_zone/ZoneCreateForm.js 
> cbfb8da2d 
>   security-admin/src/main/webapp/scripts/views/service/AuditFilterConfig.js 
> 27e2aaecb 
>   security-admin/src/main/webapp/scripts/views/users/AddUsersOrGroupsList.js 
> 26a62e67d 
>   security-admin/src/main/webapp/styles/xa.css f5544cca0 
>   
> security-admin/src/main/webapp/templates/permissions/ModulePermissionForm_tmpl.html
>  68737 
>   
> security-admin/src/main/webapp/templates/security_zone/ZoneCreateForm_tmpl.html
>  2ddfc3927 
>   security-admin/src/main/webapp/templates/users/RoleForm_tmpl.html 7686c3fd1 
> 
> 
> Diff: https://reviews.apache.org/r/74572/diff/2/
> 
> 
> Testing
> ---
> 
> Validated below scenarios with adding comman in name on old UI
> 1. Tested Resource Based/Tag Based/ KMS Service CRUD.
> 2. Tested Zone & Unzone policy CRUD.
> 3. Tested User/Group/ Role CRUD.
> 4. Tested Zone CRUD.
> 5. Tested Resource Based/Tag Based/ KMS Policy CRUD.
> 6. Tested reports/permissions/audits tab.
> 7. Tested Export and import feature.
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

[jira] [Commented] (RANGER-4461) Implement best coding practices for validating user input

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav commented on RANGER-4461:
---

Apache master commit 
https://github.com/apache/ranger/commit/f1e6e2e9a68558d26a0e3d539bf85228ae71ccdc

>  Implement best coding practices for validating user input
> --
>
> Key: RANGER-4461
> URL: https://issues.apache.org/jira/browse/RANGER-4461
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4461.patch
>
>
>  Implement best coding practices for validating user input



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

[jira] [Updated] (RANGER-4461) Implement best coding practices for validating user input

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav updated RANGER-4461:
--
Fix Version/s: 3.0.0

>  Implement best coding practices for validating user input
> --
>
> Key: RANGER-4461
> URL: https://issues.apache.org/jira/browse/RANGER-4461
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4461.patch
>
>
>  Implement best coding practices for validating user input



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

Re: Review Request 74751: RANGER-4010 : [addendum] Update policy UI to support multiple resource-sets for react ranger.

[Mugdha Varadkar]

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


Ship it!




Ship It!

- Mugdha Varadkar


On Nov. 22, 2023, 6:41 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74751/
> ---
> 
> (Updated Nov. 22, 2023, 6:41 a.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Shah, Dineshkumar Yadav, 
> Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, 
> Pradeep Agrawal, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4010
> https://issues.apache.org/jira/browse/RANGER-4010
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Policy model enhancements in RANGER_3796 enable a Ranger policy to be created 
> with multiple resource sets – like:
>  * database: [ db1 ], table: [ tbl1 ], column: [ * ]
>  * database: [ db1 ], udf: [ * ]
>  * database: [ db2 ], table: [ tbl2 ], column: [ * ]
> 
> 
> Policy UI needs to be updated to support multiple resource sets, some what 
> similar to security-zone UI that allows multiple resource sets to be added in 
> a zone. For policy UI, I suggest retaining the existing UI for 
> RangerPolicy.resources and having a separate optional UI (triggered via More 
> Resources button?) to capture additional resources.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx 
> 98495f6cc 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyPermissionItem.jsx
>  ab9b3ce88 
> 
> 
> Diff: https://reviews.apache.org/r/74751/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Review Request 74653: RANGER-4370: "Select All permissions for all components." checkbox missing in tag based policy permission popup

[Mugdha Varadkar]

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


Ship it!




Ship It!

- Mugdha Varadkar


On Nov. 23, 2023, 12:04 p.m., Brijesh Bhalala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74653/
> ---
> 
> (Updated Nov. 23, 2023, 12:04 p.m.)
> 
> 
> Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan 
> Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4370
> https://issues.apache.org/jira/browse/RANGER-4370
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> In the permissions selector popup for tag based policies in Backbone UI,
> there is a checkbox which allows users to select all permissions for all 
> components selected.
> But in React UI, this checkbox is missing.
> This is a minor bug.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/react-webapp/src/styles/style.css 46e8eeda1 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
>  cda20700c 
> 
> 
> Diff: https://reviews.apache.org/r/74653/diff/3/
> 
> 
> Testing
> ---
> 
> Tested changes on a cluster setup with Ranger Admin build with React JS code 
> base.
> 
> verified the Service & Policy Module permission component.
> 
> 
> Thanks,
> 
> Brijesh Bhalala
> 
>

Re: Review Request 74653: RANGER-4370: "Select All permissions for all components." checkbox missing in tag based policy permission popup

[Brijesh Bhalala]

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

(Updated Nov. 23, 2023, 12:04 p.m.)


Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan Neethiraj, 
Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.


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


Repository: ranger


Description
---

In the permissions selector popup for tag based policies in Backbone UI,
there is a checkbox which allows users to select all permissions for all 
components selected.
But in React UI, this checkbox is missing.
This is a minor bug.


Diffs (updated)
-

  security-admin/src/main/webapp/react-webapp/src/styles/style.css 46e8eeda1 
  
security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/TagBasePermissionItem.jsx
 cda20700c 


Diff: https://reviews.apache.org/r/74653/diff/3/

Changes: https://reviews.apache.org/r/74653/diff/2-3/


Testing
---

Tested changes on a cluster setup with Ranger Admin build with React JS code 
base.

verified the Service & Policy Module permission component.


Thanks,

Brijesh Bhalala

[jira] [Updated] (RANGER-4370) [Ranger UI] [React JS]"Select All permissions for all components." checkbox missing in tag based policy permission popup

[Brijesh Bhalala (Jira)]

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

Brijesh Bhalala updated RANGER-4370:

Attachment: 0003-RANGER-4370.patch

> [Ranger UI] [React JS]"Select All permissions for all components." checkbox 
> missing in tag based policy permission popup
> 
>
> Key: RANGER-4370
> URL: https://issues.apache.org/jira/browse/RANGER-4370
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Abhishek
>Assignee: Brijesh Bhalala
>Priority: Minor
>  Labels: ranger-react
> Attachments: 0001-RANGER-4370.patch, 0002-RANGER-4370.patch, 
> 0003-RANGER-4370.patch
>
>
> {color:#172b4d}In the permissions selector popup for tag based policies in 
> Backbone UI,{color}
> {color:#172b4d}there is a checkbox which allows users to select all 
> permissions for all components selected.{color}
> {color:#172b4d}But in React UI, this checkbox is missing.{color}
> {color:#172b4d}This is a minor bug.{color}



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

Review Request 74754: RANGER-4541: fixed validation of DataShareInDataset and DatasetInProject status update and delete

[Madhan Neethiraj]

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

Review request for ranger, Anand Nadar, Ankita Sinha, Brijesh Bhalala, Dhaval 
Rajpara, Abhay Kulkarni, Mehul Parikh, Prashant Satam, Ramesh Mani, and Subhrat 
Chaudhary.


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


Repository: ranger


Description
---

- updated validation of DataShareInDataset status change
 -- NONE  => REQUESTED: dataset admin
 -- NONE  => GRANTED/DENIED: dataShare admin
 -- NONE  => ACTIVE: dataset admin and dataShare admin
 -- REQUESTED => NONE: dataset admin
 -- REQUESTED => GRANTED/DENIED: dataShare admin
 -- REQUESTED => ACTIVE: dataset admin and dataShare admin
 -- GRANTED   => ACTIVE: dataset admin
 -- GRANTED   => DENIED: dataShare admin
 -- GRANTED   => NONE, REQUESTED: dataset admin or dataShare admin
 -- DENIED=> ACTIVE: dataset admin and dataShare admin
 -- DENIED=> GRANTED: dataShare admin
 -- DENIED=> NONE, REQUESTED: dataset admin or dataShare admin
- updated validation of DataShareInDataset delete to allow users with dataShare 
admin and dataset admin to delete 
- updated validation of DatasetInProject status change
 -- NONE  => REQUESTED: project admin
 -- NONE  => GRANTED/DENIED: dataset admin
 -- NONE  => ACTIVE: project admin and dataset admin
 -- REQUESTED => NONE: project admin
 -- REQUESTED => GRANTED/DENIED: dataset admin
 -- REQUESTED => ACTIVE: project admin and dataset admin
 -- GRANTED   => ACTIVE: project admin
 -- GRANTED   => DENIED: dataset admin
 -- GRANTED   => NONE, REQUESTED: project admin or dataset admin
 -- DENIED=> ACTIVE: project admin and dataset admin
 -- DENIED=> GRANTED: dataset admin
 -- DENIED=> NONE, REQUESTED: project admin or dataset admin
- updated validation of DatasetInProject delete to allow users with dataset 
admin and project admin to delete


Diffs
-

  
security-admin/src/main/java/org/apache/ranger/validation/RangerGdsValidator.java
 d0a1142f6 


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


Testing
---

- verified status change and delete of DataShareInDataset and DatasetInProject
- verified that all existing tests pass successfully


Thanks,

Madhan Neethiraj

[jira] [Updated] (RANGER-4556) policy creation without resource is being allowed through rest api

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav updated RANGER-4556:
--
Attachment: 0001-RANGER-4556-policy-creation-without-resource-is-bein.patch

> policy creation without resource is being allowed through rest api
> --
>
> Key: RANGER-4556
> URL: https://issues.apache.org/jira/browse/RANGER-4556
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Dineshkumar Yadav
>Assignee: Dineshkumar Yadav
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: 
> 0001-RANGER-4556-policy-creation-without-resource-is-bein.patch
>
>
> At the time of policy creation at least one resource should present.
> Currently Hive global policy can be created without any resource. 



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

Review Request 74753: RANGER-4521: All records not displayed on Admin Audits UI when filtered using session ID

[Rakesh Gupta]

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

Review request for ranger, Dineshkumar Yadav, Kishor Gollapalliwar, Abhay 
Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, sanket 
shelar, Sailaja Polavarapu, and Velmurugan Periasamy.


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


Repository: ranger


Description
---

Some audit entries for keyadmin user are missing when filtered using sessionID 
or Audit Type = Ranger Policy. Also when moved to next page most audit entries 
are missing

(Audits for import and export are shown, audit corresponding to policy crud 
operation is missing for keyadmin user)


Diffs
-

  security-admin/src/main/java/org/apache/ranger/service/XTrxLogService.java 
9d9e0bbc0 


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


Testing
---

Tested All audits are displayed properly with filter and without filter for 
admin and keyadmin user.


Thanks,

Rakesh Gupta

[jira] [Updated] (RANGER-4556) policy creation without resource is being allowed through rest api

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav updated RANGER-4556:
--
Description: 
At the time of policy creation at least one resource should present.

Currently Hive global policy can be created without any resource. 

  was:At the time of policy creation at least one resource should present.


> policy creation without resource is being allowed through rest api
> --
>
> Key: RANGER-4556
> URL: https://issues.apache.org/jira/browse/RANGER-4556
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Dineshkumar Yadav
>Assignee: Dineshkumar Yadav
>Priority: Major
> Fix For: 3.0.0
>
>
> At the time of policy creation at least one resource should present.
> Currently Hive global policy can be created without any resource. 



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

[jira] [Assigned] (RANGER-4556) policy creation without resource is being allowed through rest api

[Dineshkumar Yadav (Jira)]

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

Dineshkumar Yadav reassigned RANGER-4556:
-

Assignee: Dineshkumar Yadav

> policy creation without resource is being allowed through rest api
> --
>
> Key: RANGER-4556
> URL: https://issues.apache.org/jira/browse/RANGER-4556
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Dineshkumar Yadav
>Assignee: Dineshkumar Yadav
>Priority: Major
> Fix For: 3.0.0
>
>
> At the time of policy creation at least one resource should present.



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

[jira] [Created] (RANGER-4556) policy creation without resource is being allowed through rest api

[Dineshkumar Yadav (Jira)]

Dineshkumar Yadav created RANGER-4556:
-

 Summary: policy creation without resource is being allowed through 
rest api
 Key: RANGER-4556
 URL: https://issues.apache.org/jira/browse/RANGER-4556
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 3.0.0
Reporter: Dineshkumar Yadav
 Fix For: 3.0.0


At the time of policy creation at least one resource should present.



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

Re: Review Request 74751: RANGER-4010 : [addendum] Update policy UI to support multiple resource-sets for react ranger.

[Mugdha Varadkar]

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


Ship it!




Ship It!

- Mugdha Varadkar


On Nov. 22, 2023, 6:41 a.m., Dhaval Rajpara wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74751/
> ---
> 
> (Updated Nov. 22, 2023, 6:41 a.m.)
> 
> 
> Review request for ranger, Brijesh Bhalala, Dhaval Shah, Dineshkumar Yadav, 
> Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Mugdha Varadkar, 
> Pradeep Agrawal, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-4010
> https://issues.apache.org/jira/browse/RANGER-4010
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Policy model enhancements in RANGER_3796 enable a Ranger policy to be created 
> with multiple resource sets – like:
>  * database: [ db1 ], table: [ tbl1 ], column: [ * ]
>  * database: [ db1 ], udf: [ * ]
>  * database: [ db2 ], table: [ tbl2 ], column: [ * ]
> 
> 
> Policy UI needs to be updated to support multiple resource sets, some what 
> similar to security-zone UI that allows multiple resource sets to be added in 
> a zone. For policy UI, I suggest retaining the existing UI for 
> RangerPolicy.resources and having a separate optional UI (triggered via More 
> Resources button?) to capture additional resources.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/react-webapp/src/components/Editable.jsx 
> 98495f6cc 
>   
> security-admin/src/main/webapp/react-webapp/src/views/PolicyListing/PolicyPermissionItem.jsx
>  ab9b3ce88 
> 
> 
> Diff: https://reviews.apache.org/r/74751/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Dhaval Rajpara
> 
>

Re: Request to be a contributor in Apache Ranger

[Madhan Neethiraj]

Akshay,

 

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

 

Welcome to Apache Ranger.

 

Thanks,

Madhan

Apache Ranger PMC

 

 

From: akshay tupe 
Date: Thursday, November 23, 2023 at 12:14 AM
To: Madhan Neethiraj 
Subject: Re: Request to be a contributor in Apache Ranger

 

Hi Madhan,

 

Thanks for the url.

JIRA ID: akshaytupe15

 

Thanks & Regards, 
Akshay Tupe

 

 

On Wed, Nov 22, 2023 at 9:31 PM Madhan Neethiraj  wrote:

Akshay,

Thank you for your interest in contributing to Apache Ranger.

Can you please verify the JIRA ID, as akshaytupe doesn't exist? If you haven't 
signed up for an account yet, please sign up at 
https://selfserve.apache.org/jira-account.html, and respond to this thread.

Thanks,
Madhan
Apache Ranger PMC

On 11/22/23, 7:55 AM, "akshay tupe" mailto:akshay.t...@gmail.com>> wrote:


Hi Team,


I would like to contribute to the Apache Ranger project. Can you please add
me as a contributor to the project?
Email ID: akshay.t...@gmail.com 
JIRA ID: akshaytupe


Thanks & Regards,
Akshay Tupe