Re: Review Request 65645: Hbase audit log records may not show all tags associated with accessed column

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On Feb. 15, 2018, 12:45 a.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65645/
> ---
> 
> (Updated Feb. 15, 2018, 12:45 a.m.)
> 
> 
> Review request for ranger, Madhan Neethiraj, Ramesh Mani, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: RANGER-1984
> https://issues.apache.org/jira/browse/RANGER-1984
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> When a Hbase column is tagged with a classification,with an active tag and 
> resource policy that allows access, the audit log does not show the tag.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagForEval.java
>  b8f5b42 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerTagAccessRequest.java
>  dbdcacd 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
>  8051ec3 
>   
> agents-common/src/test/resources/policyengine/test_policyengine_tag_hdfs.json 
> b4941cd 
>   
> hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
>  058168f 
>   
> hbase-agent/src/test/java/org/apache/ranger/authorization/hbase/HBaseRangerAuthorizationTest.java
>  198aad9 
> 
> 
> Diff: https://reviews.apache.org/r/65645/diff/3/
> 
> 
> Testing
> ---
> 
> Tested with local VM
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Review Request 65645: Hbase audit log records may not show all tags associated with accessed column

[Abhay Kulkarni]

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

(Updated Feb. 15, 2018, 12:45 a.m.)


Review request for ranger, Madhan Neethiraj, Ramesh Mani, and Velmurugan 
Periasamy.


Changes
---

Rolled back table level authorization checks (when table has no 
column-families) introduced in previous revision.


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


Repository: ranger


Description
---

When a Hbase column is tagged with a classification,with an active tag and 
resource policy that allows access, the audit log does not show the tag.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagForEval.java
 b8f5b42 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerTagAccessRequest.java
 dbdcacd 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
 8051ec3 
  agents-common/src/test/resources/policyengine/test_policyengine_tag_hdfs.json 
b4941cd 
  
hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
 058168f 
  
hbase-agent/src/test/java/org/apache/ranger/authorization/hbase/HBaseRangerAuthorizationTest.java
 198aad9 


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

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


Testing
---

Tested with local VM


Thanks,

Abhay Kulkarni

[jira] [Created] (RANGER-1985) Auditing for Ranger Usersync operations

[Sailaja Polavarapu (JIRA)]

Sailaja Polavarapu created RANGER-1985:
--

 Summary: Auditing for Ranger Usersync operations
 Key: RANGER-1985
 URL: https://issues.apache.org/jira/browse/RANGER-1985
 Project: Ranger
  Issue Type: New Feature
  Components: Ranger, usersync
Reporter: Sailaja Polavarapu
 Fix For: master


During every sync cycle, ranger usersync should audit some basic information 
like number of users, number of groups that are sync'd for that cycle. Also 
provide details on sync source like the unix, file, or ldap with relevant 
configuration like ldap filters applied for that sync cycle, ldap host url, 
etc...

Add a new tab in the ranger admin UI audits for usersync and show the above 
information.



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

[jira] [Assigned] (RANGER-1985) Auditing for Ranger Usersync operations

[Sailaja Polavarapu (JIRA)]

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

Sailaja Polavarapu reassigned RANGER-1985:
--

Assignee: Sailaja Polavarapu

> Auditing for Ranger Usersync operations
> ---
>
> Key: RANGER-1985
> URL: https://issues.apache.org/jira/browse/RANGER-1985
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger, usersync
>Reporter: Sailaja Polavarapu
>Assignee: Sailaja Polavarapu
>Priority: Major
> Fix For: master
>
>
> During every sync cycle, ranger usersync should audit some basic information 
> like number of users, number of groups that are sync'd for that cycle. Also 
> provide details on sync source like the unix, file, or ldap with relevant 
> configuration like ldap filters applied for that sync cycle, ldap host url, 
> etc...
> Add a new tab in the ranger admin UI audits for usersync and show the above 
> information.



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

Fwd: Travel Assistance applications open. Please inform your communities

[Alan Gates]

-- Forwarded message --
From: Gavin McDonald 
Date: Wed, Feb 14, 2018 at 1:34 AM
Subject: Travel Assistance applications open. Please inform your communities
To: travel-assista...@apache.org


Hello PMCs.

Please could you forward on the below email to your dev and user lists.

Thanks

Gav…

—
The Travel Assistance Committee (TAC) are pleased to announce that travel
assistance applications for ApacheCon NA 2018 are now open!

We will be supporting ApacheCon NA Montreal, Canada on 24th - 29th
September 2018

 TAC exists to help those that would like to attend ApacheCon events, but
are unable to do so for financial reasons.
For more info on this years applications and qualifying criteria, please
visit the TAC website at < http://www.apache.org/travel/ >. Applications
are now open and will close 1st May.

*Important*: Applications close on May 1st, 2018. Applicants have until the
closing date above to submit their applications (which should contain as
much supporting material as required to efficiently and accurately process
their request), this will enable TAC to announce successful awards shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a diverse
range of backgrounds. We therefore encourage (as always) anyone thinking
about sending in an application to do so ASAP.
We look forward to greeting many of you in Montreal

Kind Regards,
Gavin - (On behalf of the Travel Assistance Committee)
—

[jira] [Assigned] (RANGER-1897) TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient tag-download from Atlas

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj reassigned RANGER-1897:


Assignee: Abhay Kulkarni  (was: Madhan Neethiraj)

> TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient 
> tag-download from Atlas
> --
>
> Key: RANGER-1897
> URL: https://issues.apache.org/jira/browse/RANGER-1897
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 0.7.2
>Reporter: Madhan Neethiraj
>Assignee: Abhay Kulkarni
>Priority: Major
> Fix For: 1.0.0, 0.7.2
>
> Attachments: RANGER-1897.patch
>
>
> Currently tag-synchronization via REST API method uses Atlas V1 APIs, which 
> requires large number of calls from Ranger tag-sync to Atlas server. In 
> environments having large number of entities, this approach can take a long 
> time to download tags from Atlas. Use of Atlas V2 APIs would significantly 
> improve the performance.



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

Re: Review Request 65567: RANGER-1972 : Ability to label policies, filter/search and show policies by labels

[bhavik patel]

> On Feb. 8, 2018, 1:30 p.m., Zsombor Gegesy wrote:
> > security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java
> > Lines 3140 (patched)
> > 
> >
> > You can create a 
> > 'daoMgr.getXXPolicyLabelMap().deleteByPolicyId(policy.getId())' method, 
> > which just calls one simple sql delete statement, something like: 
> > 
> > delete = em.createQuery(
> >   "DELETE FROM XPolicyLabelMap pol WHERE pol.policyId = :id");
> > delete.setParameter("id", id);
> > delete.executeUpdate();

Yes, we can do that but just following the standard which are used for deleting 
the Policy Resources, Items, Users and Groups.


> On Feb. 8, 2018, 1:30 p.m., Zsombor Gegesy wrote:
> > security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java
> > Lines 3184 (patched)
> > 
> >
> > First, the deleteExistingPolicyLabel do the same, why the duplication ?
> > Second, the xxPolicyLabelMap.getPolicyId() will return the same ID in 
> > the loop, so no need to iterate, the first delete will delete all the 
> > records.

Method deleteExistingPolicyLabel is used for deleting policy while 
deleteExistingPolicyLabelNative is used for deleting service


- bhavik


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


On Feb. 14, 2018, 12:06 p.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65567/
> ---
> 
> (Updated Feb. 14, 2018, 12:06 p.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1972
> https://issues.apache.org/jira/browse/RANGER-1972
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> In Ranger Admin, need a feature to be able to group (for example by tenant 
> name or business unit) sets of policies with one or more labels that are 
> relevant to business. 
> Furthermore, Need to able to search policies on this additional set of 
> labels. This will be useful for export/import policies as well.
> 
> 
> Diffs
> -
> 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/model/RangerPolicy.java 
> 60daed9 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/AbstractPredicateUtil.java
>  7583864 
>   agents-common/src/main/java/org/apache/ranger/plugin/util/SearchFilter.java 
> fa4f767 
>   security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 69f3768 
>   security-admin/db/mysql/patches/030-policy-labels-schema.sql PRE-CREATION 
>   security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
> 5abbcd0 
>   security-admin/db/oracle/patches/030-policy-labels-schema.sql PRE-CREATION 
>   security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
> 6dfc841 
>   security-admin/db/postgres/patches/030-policy-labels-schema.sql 
> PRE-CREATION 
>   
> security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql
>  d01 
>   security-admin/db/sqlanywhere/patches/030-policy-labels-schema.sql 
> PRE-CREATION 
>   security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
> a2be2d4 
>   security-admin/db/sqlserver/patches/030-policy-labels-schema.sql 
> PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/biz/RangerPolicyRetriever.java 
> 1b6f440 
>   security-admin/src/main/java/org/apache/ranger/biz/ServiceDBStore.java 
> 7aee433 
>   security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
> 92b0e03 
>   security-admin/src/main/java/org/apache/ranger/db/RangerDaoManagerBase.java 
> db20a14 
>   security-admin/src/main/java/org/apache/ranger/db/XXPolicyLabelDao.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/db/XXPolicyLabelMapDao.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/entity/XXPolicyLabel.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/entity/XXPolicyLabelMap.java 
> PRE-CREATION 
>   security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java 
> 9e4d799 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerPolicyLabelsService.java
>  PRE-CREATION 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerPolicyService.java
>  5aec948 
>   
> security-admin/src/main/java/org/apache/ranger/service/RangerPolicyServiceBase.java
>  5d3af2f 
>   security-admin/src/main/java/org/apache/ranger/view/VXPolicy.java c73d42b 
>   

[jira] [Updated] (RANGER-1972) Ability to label policies, filter/search and show policies by labels

[bhavik patel (JIRA)]

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

bhavik patel updated RANGER-1972:
-
Attachment: RANGER-1972-master-03.patch

> Ability to label policies, filter/search and show policies by labels
> 
>
> Key: RANGER-1972
> URL: https://issues.apache.org/jira/browse/RANGER-1972
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: bhavik patel
>Assignee: bhavik patel
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: RANGER-1972-master-01.patch, 
> RANGER-1972-master-02.patch, RANGER-1972-master-03.patch, 
> RANGER-1972-master.patch
>
>
> In Ranger Admin, need a feature to be able to group (for example by tenant 
> name or business unit) sets of policies with one or more labels that are 
> relevant to business. 
> Furthermore, Need to able to search policies on this additional set of 
> labels. This will be useful for export/import policies as well.



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

Review Request 65651: RANGER-1889: List Users belonging to Group in Group tab

[Nitin Galave]

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

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

Request to add the list of users inside each group page on the Settings -> 
Users/Groups page.


Diffs
-

  security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
b71427c 
  security-admin/src/main/webapp/scripts/views/users/UserTableLayout.js 9febd99 


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


Testing
---

1. Able to see users which are present inside each group.(Added user list 
column on group listing page)
2. User search filter is also working on thoses users.
3. Also tested with internal and external groups/users.


Thanks,

Nitin Galave

[jira] [Assigned] (RANGER-1897) TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient tag-download from Atlas

[Nikhil Purbhe (JIRA)]

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

Nikhil Purbhe reassigned RANGER-1897:
-

Assignee: Nikhil Purbhe  (was: Madhan Neethiraj)

> TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient 
> tag-download from Atlas
> --
>
> Key: RANGER-1897
> URL: https://issues.apache.org/jira/browse/RANGER-1897
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 0.7.2
>Reporter: Madhan Neethiraj
>Assignee: Nikhil Purbhe
>Priority: Major
> Fix For: 1.0.0, 0.7.2
>
> Attachments: RANGER-1897.patch
>
>
> Currently tag-synchronization via REST API method uses Atlas V1 APIs, which 
> requires large number of calls from Ranger tag-sync to Atlas server. In 
> environments having large number of entities, this approach can take a long 
> time to download tags from Atlas. Use of Atlas V2 APIs would significantly 
> improve the performance.



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

[jira] [Assigned] (RANGER-1897) TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient tag-download from Atlas

[Nikhil Purbhe (JIRA)]

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

Nikhil Purbhe reassigned RANGER-1897:
-

Assignee: Madhan Neethiraj  (was: Nikhil Purbhe)

> TagSync should replace use of V1 Atlas APIs with V2 APIs for efficient 
> tag-download from Atlas
> --
>
> Key: RANGER-1897
> URL: https://issues.apache.org/jira/browse/RANGER-1897
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 0.7.2
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 1.0.0, 0.7.2
>
> Attachments: RANGER-1897.patch
>
>
> Currently tag-synchronization via REST API method uses Atlas V1 APIs, which 
> requires large number of calls from Ranger tag-sync to Atlas server. In 
> environments having large number of entities, this approach can take a long 
> time to download tags from Atlas. Use of Atlas V2 APIs would significantly 
> improve the performance.



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

Re: Review Request 65645: Hbase audit log records may not show all tags associated with accessed column

[Abhay Kulkarni]

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

(Updated Feb. 14, 2018, 10:05 a.m.)


Review request for ranger, Madhan Neethiraj, Ramesh Mani, and Velmurugan 
Periasamy.


Changes
---

Added table level authorization check


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


Repository: ranger


Description
---

When a Hbase column is tagged with a classification,with an active tag and 
resource policy that allows access, the audit log does not show the tag.


Diffs (updated)
-

  
agents-common/src/main/java/org/apache/ranger/plugin/contextenricher/RangerTagForEval.java
 b8f5b42 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerTagAccessRequest.java
 dbdcacd 
  
agents-common/src/main/java/org/apache/ranger/plugin/policyevaluator/RangerDefaultPolicyEvaluator.java
 8051ec3 
  agents-common/src/test/resources/policyengine/test_policyengine_tag_hdfs.json 
b4941cd 
  
hbase-agent/src/main/java/org/apache/ranger/authorization/hbase/RangerAuthorizationCoprocessor.java
 058168f 
  
hbase-agent/src/test/java/org/apache/ranger/authorization/hbase/HBaseRangerAuthorizationTest.java
 198aad9 
  hbase-agent/src/test/resources/hbase-policies.json b7b44c9 
  hbase-agent/src/test/resources/log4j.properties cb409e8 


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

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


Testing
---

Tested with local VM


Thanks,

Abhay Kulkarni

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

[Nitin Galave (JIRA)]

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

Nitin Galave updated RANGER-1889:
-
Summary: List Users belonging to Group in Group tab  (was: List Users 
belonging to Group on Group Detail page)

> 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.0.0
>
> Attachments: 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)

[jira] [Commented] (RANGER-1889) List Users belonging to Group on Group Detail page

[Nitin Galave (JIRA)]

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

Nitin Galave commented on RANGER-1889:
--

FYI:
It's better to show group associated users on listing page instead of edit page 
(read only).
If we show users on edit page then it might confuse because create group page 
does not contain any option related to add users which is because we are not 
supporting adding users to group through UI.

So, I have added show users option itself on the group listing page

> List Users belonging to Group on Group Detail page
> --
>
> 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.0.0
>
> Attachments: 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)

[jira] [Updated] (RANGER-1889) List Users belonging to Group on Group Detail page

[Nitin Galave (JIRA)]

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

Nitin Galave updated RANGER-1889:
-
Fix Version/s: 1.0.0

> List Users belonging to Group on Group Detail page
> --
>
> 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.0.0
>
>
> 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)