Review Request 74775: RANGER-4502 : Getting Error to load backbone.js latest UI.

2023-12-04 Thread Dhaval Rajpara

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

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-4502
https://issues.apache.org/jira/browse/RANGER-4502


Repository: ranger


Description
---

Step to reproduce:

1) Login to ranger admin UI
2) go to the profile drop-down
3) Click on Switch to latest UI

Result in "NO services found" page displayed. But we have services present in 
Backbone Classic UI.


Diffs
-

  
security-admin/src/main/webapp/scripts/views/policymanager/ServiceLayoutSidebar.js
 965c52c37 


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


Testing
---

Testing is in progress


Thanks,

Dhaval Rajpara



[jira] [Updated] (RANGER-4502) Getting Error to load backbone.js latest UI.

2023-12-04 Thread Dhaval Rajpara (Jira)


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

Dhaval Rajpara updated RANGER-4502:
---
Attachment: 0001-RANGER-4502.patch

> Getting Error to load  backbone.js latest UI.
> -
>
> Key: RANGER-4502
> URL: https://issues.apache.org/jira/browse/RANGER-4502
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
> Attachments: 0001-RANGER-4502.patch
>
>
> Step to reproduce:
> 1) Login to ranger admin UI
> 2) go to the profile drop-down
> 3) Click on Switch to latest UI
> Result in "NO services found" page displayed. But we have services present in 
> Backbone Classic UI. 



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


Re: Review Request 74767: RANGER-4542 : Need to add support of search by zoneNamePartial and sort by zoneName, createTime query params in zone-summary api

2023-12-04 Thread Madhan Neethiraj

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


Ship it!




Ship It!

- Madhan Neethiraj


On Nov. 29, 2023, 9:39 a.m., Prashant Satam wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74767/
> ---
> 
> (Updated Nov. 29, 2023, 9:39 a.m.)
> 
> 
> Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, 
> Monika Kachhadiya, Subhrat Chaudhary, and Vanita Ubale.
> 
> 
> Bugs: RANGER-4542
> https://issues.apache.org/jira/browse/RANGER-4542
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> For GET API service/zones/summary we need to add support for query param 
> search by  zoneNamePartial , and sort by  zoneName, createTime (Both ASC and 
> DESC order)
> When we pass just sortTpye/sortBy params single or together we dont get 
> response accordingly
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/AbstractPredicateUtil.java
>  07c561506 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/SecurityZonePredicateUtil.java
>  9164091ae 
>   security-admin/src/main/java/org/apache/ranger/biz/SecurityZoneDBStore.java 
> 6c6ddc49f 
> 
> 
> Diff: https://reviews.apache.org/r/74767/diff/1/
> 
> 
> Testing
> ---
> 
> Steps to Test
> 1)Create multiple security-zones 
> 2)Use /service/zones/summary?sortBy=zoneName=DESC only using 
> (sortTpye/sortBy) we get response according to this params
> 3)Use just /service/zones/summary?sortType=DESC we get response according to 
> this param 
> 4)Create 2 security-zones with similar names i.e Test-zone-1 and Test-zone-11
> 5)Use /service/zones/summary?zoneNamePartial=Test-zone-1 we get 2 
> security-zones in response
> 
> 
> Thanks,
> 
> Prashant Satam
> 
>



[jira] [Created] (RANGER-4572) Upgrade Apache Derby to 10.17.1.0

2023-12-04 Thread Pradeep Agrawal (Jira)
Pradeep Agrawal created RANGER-4572:
---

 Summary: Upgrade Apache Derby to 10.17.1.0
 Key: RANGER-4572
 URL: https://issues.apache.org/jira/browse/RANGER-4572
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal






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


[jira] [Updated] (RANGER-4213) Getting 302 status code instead of 419 in case of session timeout

2023-12-04 Thread Rakesh Gupta (Jira)


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

Rakesh Gupta updated RANGER-4213:
-
Attachment: 0001-RANGER-4213.patch

> Getting 302 status code instead of 419 in case of session timeout
> -
>
> Key: RANGER-4213
> URL: https://issues.apache.org/jira/browse/RANGER-4213
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Mugdha Varadkar
>Assignee: Rakesh Gupta
>Priority: Major
> Attachments: 0001-RANGER-4213.patch
>
>
> Steps to reproduce :
> # Setup a cluster with Ranger Admin code bits
> # Set session timeout to lower value in {{ews/webapp/WEB-INF/web.xml}}
> # Start Ranger Admin
> # When session is timeout the "service/plugins/" api gives status code 302 
> instead of 419
> # Earlier we used to get 419 status code from api during session time-out
> cc [~Dhaval.Rajpara] / [~mehul]



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


[jira] [Updated] (RANGER-4213) Getting 302 status code instead of 419 in case of session timeout

2023-12-04 Thread Rakesh Gupta (Jira)


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

Rakesh Gupta updated RANGER-4213:
-
Attachment: (was: 
0001-RANGER-4213-Getting-302-status-code-instead-of-419-i.patch)

> Getting 302 status code instead of 419 in case of session timeout
> -
>
> Key: RANGER-4213
> URL: https://issues.apache.org/jira/browse/RANGER-4213
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Mugdha Varadkar
>Assignee: Rakesh Gupta
>Priority: Major
>
> Steps to reproduce :
> # Setup a cluster with Ranger Admin code bits
> # Set session timeout to lower value in {{ews/webapp/WEB-INF/web.xml}}
> # Start Ranger Admin
> # When session is timeout the "service/plugins/" api gives status code 302 
> instead of 419
> # Earlier we used to get 419 status code from api during session time-out
> cc [~Dhaval.Rajpara] / [~mehul]



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


[jira] [Commented] (RANGER-4010) Update policy UI to support multiple resource-sets for react ranger.

2023-12-04 Thread Dineshkumar Yadav (Jira)


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

Dineshkumar Yadav commented on RANGER-4010:
---

Apache master : 
https://github.com/apache/ranger/commit/2e4a8c17baec963c190966be11a934f72373644b

> Update policy UI to support multiple resource-sets for react ranger.
> 
>
> Key: RANGER-4010
> URL: https://issues.apache.org/jira/browse/RANGER-4010
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Major
>  Labels: ranger-react
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4010.patch
>
>
> 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.



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


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

2023-12-04 Thread Dineshkumar Yadav (Jira)


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

Dineshkumar Yadav commented on RANGER-4556:
---

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

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