Re: Review Request 66878: RANGER-2090: Empty start and end time Strings should be interpreted same as NULL in Ranger

2018-04-30 Thread Ramesh Mani

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


Ship it!




Ship It!

- Ramesh Mani


On April 30, 2018, 11:37 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66878/
> ---
> 
> (Updated April 30, 2018, 11:37 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Ramesh Mani.
> 
> 
> Bugs: RANGER-2090
> https://issues.apache.org/jira/browse/RANGER-2090
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Treat empty-string or null value for startTime/endTime in time-based 
> policies/tags identically.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidityScheduleValidator.java
>  30c4d416d 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerValidityScheduleEvaluator.java
>  f097f2274 
>   
> agents-common/src/test/resources/policyengine/validityscheduler/test-validity-schedules-valid-and-applicable.json
>  7df6fcfe2 
> 
> 
> Diff: https://reviews.apache.org/r/66878/diff/1/
> 
> 
> Testing
> ---
> 
> Developed unit tests and ran them successfully
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>



Review Request 66878: RANGER-2090: Empty start and end time Strings should be interpreted same as NULL in Ranger

2018-04-30 Thread Abhay Kulkarni

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

Review request for ranger, Madhan Neethiraj and Ramesh Mani.


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


Repository: ranger


Description
---

Treat empty-string or null value for startTime/endTime in time-based 
policies/tags identically.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidityScheduleValidator.java
 30c4d416d 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerValidityScheduleEvaluator.java
 f097f2274 
  
agents-common/src/test/resources/policyengine/validityscheduler/test-validity-schedules-valid-and-applicable.json
 7df6fcfe2 


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


Testing (updated)
---

Developed unit tests and ran them successfully


Thanks,

Abhay Kulkarni



[jira] [Assigned] (RANGER-2090) Empty start and end time Strings should be interpreted same as NULL in Ranger

2018-04-30 Thread Abhay Kulkarni (JIRA)

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

Abhay Kulkarni reassigned RANGER-2090:
--

Assignee: Abhay Kulkarni

> Empty start and end time Strings should be interpreted same as NULL in Ranger
> -
>
> Key: RANGER-2090
> URL: https://issues.apache.org/jira/browse/RANGER-2090
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Anuja Leekha
>Assignee: Abhay Kulkarni
>Priority: Major
>  Labels: ranger
> Fix For: master, 0.7.2, 1.1.0, 1.0.1
>
>
> Empty start and end time Strings should be interpreted same as NULL in Ranger



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 66877: RANGER-2089: Update scala library version for tagsync to be the same as in Atlas

2018-04-30 Thread Ramesh Mani

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


Ship it!




Ship It!

- Ramesh Mani


On April 30, 2018, 10:47 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66877/
> ---
> 
> (Updated April 30, 2018, 10:47 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Bugs: RANGER-2089
> https://issues.apache.org/jira/browse/RANGER-2089
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Update scala-libary.jar version from 2.11.8 to 2.11.12 to be compatible with 
> Atlas
> 
> 
> Diffs
> -
> 
>   pom.xml f81a39b84 
> 
> 
> Diff: https://reviews.apache.org/r/66877/diff/1/
> 
> 
> Testing
> ---
> 
> Ran all unit tests successfully
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>



[jira] [Created] (RANGER-2090) Empty start and end time Strings should be interpreted same as NULL in Ranger

2018-04-30 Thread Anuja Leekha (JIRA)
Anuja Leekha created RANGER-2090:


 Summary: Empty start and end time Strings should be interpreted 
same as NULL in Ranger
 Key: RANGER-2090
 URL: https://issues.apache.org/jira/browse/RANGER-2090
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Reporter: Anuja Leekha
 Fix For: master, 0.7.2, 1.1.0, 1.0.1


Empty start and end time Strings should be interpreted same as NULL in Ranger



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 66877: RANGER-2089: Update scala library version for tagsync to be the same as in Atlas

2018-04-30 Thread Sarath Subramanian

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


Ship it!




Ship It!

- Sarath Subramanian


On April 30, 2018, 3:47 p.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66877/
> ---
> 
> (Updated April 30, 2018, 3:47 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Bugs: RANGER-2089
> https://issues.apache.org/jira/browse/RANGER-2089
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Update scala-libary.jar version from 2.11.8 to 2.11.12 to be compatible with 
> Atlas
> 
> 
> Diffs
> -
> 
>   pom.xml f81a39b84 
> 
> 
> Diff: https://reviews.apache.org/r/66877/diff/1/
> 
> 
> Testing
> ---
> 
> Ran all unit tests successfully
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>



Review Request 66877: RANGER-2089: Update scala library version for tagsync to be the same as in Atlas

2018-04-30 Thread Abhay Kulkarni

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

Review request for ranger, Madhan Neethiraj and Sarath Subramanian.


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


Repository: ranger


Description
---

Update scala-libary.jar version from 2.11.8 to 2.11.12 to be compatible with 
Atlas


Diffs
-

  pom.xml f81a39b84 


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


Testing
---

Ran all unit tests successfully


Thanks,

Abhay Kulkarni



[jira] [Created] (RANGER-2089) Update scala library version for tagsync to be the same as in Atlas

2018-04-30 Thread Abhay Kulkarni (JIRA)
Abhay Kulkarni created RANGER-2089:
--

 Summary: Update scala library version for tagsync to be the same 
as in Atlas
 Key: RANGER-2089
 URL: https://issues.apache.org/jira/browse/RANGER-2089
 Project: Ranger
  Issue Type: Bug
  Components: tagsync
Affects Versions: master
Reporter: Abhay Kulkarni
Assignee: Abhay Kulkarni
 Fix For: master


Update scala-libary.jar version from 2.11.8 to 2.11.12 to be compatible with 
Atlas.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (RANGER-1889) List Users belonging to Group in Group tab

2018-04-30 Thread Nitin Galave (JIRA)

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

Nitin Galave commented on RANGER-1889:
--

UI Improvements committed to apache 
[master|https://github.com/apache/ranger/commit/6c6ec75db0c3871ff76fc072e64fbc778d58625c]
 branch.

1. Show users in an appropriate format and also add link to username label to 
see user detail.

2. Add copy to clipboard functionality to copy list of users from pop-up.

> List Users belonging to Group in Group tab
> --
>
> Key: RANGER-1889
> URL: https://issues.apache.org/jira/browse/RANGER-1889
> Project: Ranger
>  Issue Type: Improvement
>  Components: admin
>Affects Versions: 0.7.0
> Environment: HDP 2.6.1 + Kerberos
>Reporter: Hari Sekhon
>Assignee: Nitin Galave
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: RANGER-1889-Improvement.2.patch, RANGER-1889.1.patch, 
> RANGER-1889.matser.patch
>
>
> Request to add the list of users inside each group page on the Settings -> 
> Groups -> "" Group Detail page.
> Currently one can see the list of groups a specific user belongs to in the 
> groups column on the User List page, but cannot see all users belonging to a 
> specific group as there is no users column on the Group List page (probably 
> just as well as it could be large), but once clicking on a specific group the 
> Group Detail page lists only Group Name and Description fields, it should 
> have a long listing of users that are members of that specific group.
> This is important for auditing purposes as most policies are set on a group 
> basis yet there is no current way in the Ranger UI to see all the users in 
> that group.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 66810: RANGER-2085 :- Add resource lookup for entity-id in Atlas service

2018-04-30 Thread Madhan Neethiraj

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


Fix it, then Ship it!





plugin-atlas/src/main/java/org/apache/ranger/services/atlas/RangerServiceAtlas.java
Lines 404 (patched)


Consider replacing method parameter "List types" with "String 
typeName", and call this method only when one typeName is present for 
'entity-types' resource.


- Madhan Neethiraj


On April 26, 2018, 12:36 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66810/
> ---
> 
> (Updated April 26, 2018, 12:36 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj, Mehul Parikh, and Ramesh Mani.
> 
> 
> Bugs: RANGER-2085
> https://issues.apache.org/jira/browse/RANGER-2085
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> This patch includes changes to add resource lookup for entity-id in Atlas 
> service.
> 
> 
> Diffs
> -
> 
>   
> plugin-atlas/src/main/java/org/apache/ranger/services/atlas/RangerServiceAtlas.java
>  671d2d14f4dda0274fac3d9b039597360348ca18 
>   src/main/assembly/admin-web.xml 73bf8c05b7b8f0e5d2fea4b2e446c1f087b9788b 
> 
> 
> Diff: https://reviews.apache.org/r/66810/diff/1/
> 
> 
> Testing
> ---
> 
> Searched with names of entity with starting characters in text-box then 
> entities with qualified names are loading in dropdown of selected type.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>



Re: Review Request 66852: RANGER-1852: some groups missed to be sync if they are syncd from openldap If deltasync is enabled

2018-04-30 Thread Velmurugan Periasamy

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


Fix it, then Ship it!





ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapDeltaUserGroupBuilder.java
Line 854 (original), 854 (patched)


Use a configurable param for this?


- Velmurugan Periasamy


On April 27, 2018, 5:48 p.m., Sailaja Polavarapu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66852/
> ---
> 
> (Updated April 27, 2018, 5:48 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-1852
> https://issues.apache.org/jira/browse/RANGER-1852
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Incrementing timestamp value for groups to 1sec instead of 1min. This is 
> in-sync with timestamp value for users.
> 
> 
> Diffs
> -
> 
>   
> ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapDeltaUserGroupBuilder.java
>  2288ab8e 
> 
> 
> Diff: https://reviews.apache.org/r/66852/diff/1/
> 
> 
> Testing
> ---
> 
> 1. Verified the existing unit tests are ran successfully.
> 2. Verified basic usersync functionality with openldap server.
> 
> 
> Thanks,
> 
> Sailaja Polavarapu
> 
>



Re: Review Request 66796: RANGER-2041 : Handle validations for passwords of admin accounts during ranger install

2018-04-30 Thread Mehul Parikh

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


Ship it!




Ship It!

- Mehul Parikh


On April 27, 2018, 11:15 a.m., Fatima Khan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66796/
> ---
> 
> (Updated April 27, 2018, 11:15 a.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
> Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and 
> Sailaja Polavarapu.
> 
> 
> Bugs: RANGER-2041
> https://issues.apache.org/jira/browse/RANGER-2041
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> We are making default password mandatory during fresh ranger install.
> 
> 
> Diffs
> -
> 
>   security-admin/scripts/db_setup.py 2cbe665 
>   security-admin/scripts/dba_script.py 4a57bba 
>   security-admin/scripts/setup.sh 45bc918 
> 
> 
> Diff: https://reviews.apache.org/r/66796/diff/1/
> 
> 
> Testing
> ---
> 
> Tested the validation for all password combinations in manual install.
> 
> 
> Thanks,
> 
> Fatima Khan
> 
>



Re: Review Request 66810: RANGER-2085 :- Add resource lookup for entity-id in Atlas service

2018-04-30 Thread Velmurugan Periasamy

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


Ship it!




Ship It!

- Velmurugan Periasamy


On April 26, 2018, 12:36 p.m., Nixon Rodrigues wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66810/
> ---
> 
> (Updated April 26, 2018, 12:36 p.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj, Mehul Parikh, and Ramesh Mani.
> 
> 
> Bugs: RANGER-2085
> https://issues.apache.org/jira/browse/RANGER-2085
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> This patch includes changes to add resource lookup for entity-id in Atlas 
> service.
> 
> 
> Diffs
> -
> 
>   
> plugin-atlas/src/main/java/org/apache/ranger/services/atlas/RangerServiceAtlas.java
>  671d2d14f4dda0274fac3d9b039597360348ca18 
>   src/main/assembly/admin-web.xml 73bf8c05b7b8f0e5d2fea4b2e446c1f087b9788b 
> 
> 
> Diff: https://reviews.apache.org/r/66810/diff/1/
> 
> 
> Testing
> ---
> 
> Searched with names of entity with starting characters in text-box then 
> entities with qualified names are loading in dropdown of selected type.
> 
> 
> Thanks,
> 
> Nixon Rodrigues
> 
>



[jira] [Updated] (RANGER-2083) Resctict KMS audit events to KMS related users only

2018-04-30 Thread Velmurugan Periasamy (JIRA)

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

Velmurugan Periasamy updated RANGER-2083:
-
Reporter: Deepak Sharma  (was: Fatima Amjad Khan)

> Resctict KMS audit events to KMS related users only 
> 
>
> Key: RANGER-2083
> URL: https://issues.apache.org/jira/browse/RANGER-2083
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Deepak Sharma
>Assignee: Fatima Amjad Khan
>Priority: Major
> Fix For: master
>
> Attachments: RANGER-2083.patch
>
>
> Only Keyadmin and KMS Auditor role users should be able to see KMS related 
> audit logs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: Review Request 66796: RANGER-2041 : Handle validations for passwords of admin accounts during ranger install

2018-04-30 Thread Velmurugan Periasamy

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


Ship it!




Ship It!

- Velmurugan Periasamy


On April 27, 2018, 11:15 a.m., Fatima Khan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66796/
> ---
> 
> (Updated April 27, 2018, 11:15 a.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
> Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and 
> Sailaja Polavarapu.
> 
> 
> Bugs: RANGER-2041
> https://issues.apache.org/jira/browse/RANGER-2041
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> We are making default password mandatory during fresh ranger install.
> 
> 
> Diffs
> -
> 
>   security-admin/scripts/db_setup.py 2cbe665 
>   security-admin/scripts/dba_script.py 4a57bba 
>   security-admin/scripts/setup.sh 45bc918 
> 
> 
> Diff: https://reviews.apache.org/r/66796/diff/1/
> 
> 
> Testing
> ---
> 
> Tested the validation for all password combinations in manual install.
> 
> 
> Thanks,
> 
> Fatima Khan
> 
>



Re: Review Request 66690: RANGER-2072 - Update HBase to 1.3.2

2018-04-30 Thread Velmurugan Periasamy

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


Ship it!




Ship It!

- Velmurugan Periasamy


On April 18, 2018, 4:38 p.m., Colm O hEigeartaigh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66690/
> ---
> 
> (Updated April 18, 2018, 4:38 p.m.)
> 
> 
> Review request for ranger.
> 
> 
> Bugs: RANGER-2072
> https://issues.apache.org/jira/browse/RANGER-2072
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> This task is to upgrade the HBase dependency to 1.3.2.
> 
> 
> Diffs
> -
> 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessorBase.java
>  f34bc126 
>   pom.xml bf363f8c 
>   
> ranger-hbase-plugin-shim/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
>  6ab595a3 
> 
> 
> Diff: https://reviews.apache.org/r/66690/diff/1/
> 
> 
> Testing
> ---
> 
> Tested authorization works correctly with a HBase 1.3.2 distribution.
> 
> 
> Thanks,
> 
> Colm O hEigeartaigh
> 
>



Re: Review Request 66818: RANGER-1889: Improvements to list Users belonging to Group in Group tab.

2018-04-30 Thread Velmurugan Periasamy

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


Ship it!




Ship It!

- Velmurugan Periasamy


On April 26, 2018, 6:08 p.m., Nitin Galave wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66818/
> ---
> 
> (Updated April 26, 2018, 6:08 p.m.)
> 
> 
> Review request for ranger, Gautam Borad, Mehul Parikh, Pradeep Agrawal, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1889
> https://issues.apache.org/jira/browse/RANGER-1889
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> 1.Show users in appropriate format and also add link to username label to see 
> user detail.
> 2.Add copy to clipboard functionality to copy list of users from pop-up.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/scripts/utils/XAUtils.js 8a0302d 
>   security-admin/src/main/webapp/scripts/utils/XAViewUtils.js a7abd1e 
>   security-admin/src/main/webapp/scripts/views/users/UserTableLayout.js 
> 886b789 
>   security-admin/src/main/webapp/styles/xa.css da3433f 
> 
> 
> Diff: https://reviews.apache.org/r/66818/diff/1/
> 
> 
> Testing
> ---
> 
> 1.Able to see users which are present inside each group
> 2.Able to see user details on clicking username
> 3.Verified copy to clipboard functionality.
> 
> 
> Thanks,
> 
> Nitin Galave
> 
>



Review Request 66867: RANGER-2083 : Resctict KMS audit events to KMS related users only

2018-04-30 Thread Fatima Khan

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

Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, and 
Sailaja Polavarapu.


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


Repository: ranger


Description
---

Only Keyadmin and KMS Auditor role users should be able to see KMS related 
audit logs.


Diffs
-

  security-admin/src/main/java/org/apache/ranger/biz/RangerBizUtil.java a0477fb 
  
security-admin/src/main/java/org/apache/ranger/service/RangerServiceDefServiceBase.java
 5cbe47a 
  
security-admin/src/main/java/org/apache/ranger/service/XAccessAuditService.java 
4c8ed83 
  
security-admin/src/main/java/org/apache/ranger/solr/SolrAccessAuditsService.java
 7dcb074 


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


Testing
---

Testing done by checking that only Keyadmin and KMS Auditor role users are be 
able to see KMS related audit logs.


Thanks,

Fatima Khan



[jira] [Updated] (RANGER-2083) Resctict KMS audit events to KMS related users only

2018-04-30 Thread Fatima Amjad Khan (JIRA)

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

Fatima Amjad Khan updated RANGER-2083:
--
Attachment: RANGER-2083.patch

> Resctict KMS audit events to KMS related users only 
> 
>
> Key: RANGER-2083
> URL: https://issues.apache.org/jira/browse/RANGER-2083
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Fatima Amjad Khan
>Assignee: Fatima Amjad Khan
>Priority: Major
> Fix For: master
>
> Attachments: RANGER-2083.patch
>
>
> Only Keyadmin and KMS Auditor role users should be able to see KMS related 
> audit logs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)