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


Ship it!




Ship It!

- Mugdha Varadkar


On May 13, 2024, 9:48 a.m., Brijesh Bhalala wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/74982/
> -----------------------------------------------------------
> 
> (Updated May 13, 2024, 9:48 a.m.)
> 
> 
> Review request for ranger, Dhaval Rajpara, Dineshkumar Yadav, Madhan 
> Neethiraj, Mehul Parikh, Mugdha Varadkar, Nikunj Pansuriya, and Nitin Galave.
> 
> 
> Bugs: RANGER-4681
>     https://issues.apache.org/jira/browse/RANGER-4681
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> Audit logs for Mask & Row policy does not show policy condition under policy 
> item.
> 
>  
> 
> Steps to repro:
> 
> 1) Inside Hive service, navigate hive masking policy listing page.
> 
> 2) Click on "Add New Policy", add all the details. Under policy item section 
> add policy condition. Now save the policy
> 
> 3) Go to Audits, Admin page, click on the audit record of above newly policy. 
> One modal would be opened which show all the details for the policy
> 
> 4) Under "Row Level Filter Policy Items" section we would not see policy 
> condition details.
> 
> 
> Diffs
> -----
> 
>   security-admin/src/main/webapp/react-webapp/src/styles/style.css e6b767f5e 
>   
> security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyLogs.jsx
>  acd4f5825 
>   
> security-admin/src/main/webapp/react-webapp/src/views/AuditEvent/AdminLogs/PolicyViewDetails.jsx
>  7dd2de84f 
> 
> 
> Diff: https://reviews.apache.org/r/74982/diff/2/
> 
> 
> Testing
> -------
> 
> Applied the patch on a cluster and tested the following UI scenarios :-
> 1)Policy CRUD operations.
> 2)Resource based & tag based policy modules.
> 3)Audit admin table.
> 
> 
> Thanks,
> 
> Brijesh Bhalala
> 
>

Reply via email to