[jira] [Assigned] (RANGER-2102) Popup, Date picker and Dropdown list of select field remains open on-click of a back button from browser

2018-05-17 Thread Mehul Parikh (JIRA) 

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

Mehul Parikh reassigned RANGER-2102:


Assignee: Dhaval Rajpara

> Popup, Date picker and Dropdown list of select field remains open on-click of 
> a back button from browser
> 
>
> Key: RANGER-2102
> URL: https://issues.apache.org/jira/browse/RANGER-2102
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Reporter: Dhaval Rajpara
>Assignee: Dhaval Rajpara
>Priority: Minor
> Fix For: master
>
> Attachments: Validity_Period_popup_remain_open_1.png, 
> list_will_remain_open1.png
>
>
> It is reproduced in most of the case where modals/popups/dropdown list are 
> used in the page.
> Few cases are mention below:
>  # Click on policy validity period in policy create page and hit the back 
> button of the browser, popup remains open.
>  # Click any drop-down list throughout in Ranger UI and simply press back 
> button of the browser, the drop-down list remains open.
>  # Click on date-selector throughout in Ranger UI and press back button of 
> the browser, date-selector remains open.



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

Review Request 67206: RANGER-2108: Ensure that resource and access-type names in service definition are in lower case

2018-05-17 Thread Abhay Kulkarni 

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

Review request for ranger and Madhan Neethiraj.


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


Repository: ranger


Description
---

Ranger policy validations depend on resource names and access-type names being 
lower case. A corresponding validation check should ensure that all resource 
and access-type names in the service definitions too are in lower case, and 
fail to validate the service definition if not so.


Diffs
-

  
agents-common/src/main/java/org/apache/ranger/plugin/errors/ValidationErrorCode.java
 ab120b729 
  
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerServiceDefValidator.java
 d5f3fe5c9 
  
agents-common/src/main/java/org/apache/ranger/plugin/model/validation/RangerValidator.java
 55973f545 
  
agents-common/src/test/java/org/apache/ranger/plugin/model/validation/TestRangerServiceDefValidator.java
 72c4520b7 


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


Testing
---

Wrote corresponding unit test. Ran all unit tests successfully.


Thanks,

Abhay Kulkarni

[jira] [Created] (RANGER-2108) Ensure that resource and access-type names in service definition are in lower case

2018-05-17 Thread Abhay Kulkarni (JIRA) 
Abhay Kulkarni created RANGER-2108:
--

 Summary: Ensure that resource and access-type names in service 
definition are in lower case
 Key: RANGER-2108
 URL: https://issues.apache.org/jira/browse/RANGER-2108
 Project: Ranger
  Issue Type: Bug
  Components: admin
Affects Versions: master
Reporter: Abhay Kulkarni
Assignee: Abhay Kulkarni
 Fix For: master


Ranger policy validations depend on resource names and access-type names being 
lower case. A corresponding validation check should ensure that all resource 
and access-type names in the service definitions too are in lower case, and 
fail to validate the service definition if not so.



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

Re: Review Request 67192: RANGER-2105:Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY

2018-05-17 Thread Madhan Neethiraj 

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




hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java
Line 271 (original), 271 (patched)


getURIAccessType() is called only when hiveObjType is URI - both in #271 
and #317. Please review if it is necessary to send in hiveObjType as parameter.


- Madhan Neethiraj


On May 17, 2018, 8:06 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67192/
> ---
> 
> (Updated May 17, 2018, 8:06 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, Thejas Nair, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2105
> https://issues.apache.org/jira/browse/RANGER-2105
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> RANGER-2105:Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY
> 
> 
> Diffs
> -
> 
>   
> hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java
>  780afac 
> 
> 
> Diff: https://reviews.apache.org/r/67192/diff/1/
> 
> 
> Testing
> ---
> 
> Testing done in Local VM
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

Review Request 67196: RANGER-2107 - use spring for injecting DAO by generic parameters, and remove the unnecessary code

2018-05-17 Thread Zsombor Gegesy 

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

Review request for ranger.


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


Repository: ranger


Description
---

Currently, instead of relying on Spring to inject the DAOs internally, Ranger 
use a RangerDaoManager to create and acquire objects, which lead to a lot of 
unnecessary generic code which complicates the code.
 Instead of this, all the 'DAO' needs a simple '@Service' annotation, and 
RangerBaseModelService.entityDao and AbstractBaseResourceService.entityDao can 
be marked as @Autowired - and Spring will do her job. (Spring before 4.0 were 
unable to autowire fields based on the generic parameters).


Diffs
-

  security-admin/src/main/java/org/apache/ranger/biz/RangerBizUtil.java 
da7144673 
  security-admin/src/main/java/org/apache/ranger/common/RangerSearchUtil.java 
94374ab2f 
  security-admin/src/main/java/org/apache/ranger/common/SearchUtil.java 
2c918fdc3 
  security-admin/src/main/java/org/apache/ranger/db/RangerDaoManager.java 
fddfda399 
  security-admin/src/main/java/org/apache/ranger/db/RangerDaoManagerBase.java 
c57ecc84a 
  security-admin/src/main/java/org/apache/ranger/db/XXAssetDao.java cf25c8eef 
  security-admin/src/main/java/org/apache/ranger/db/XXAuditMapDao.java 
113dbca75 
  security-admin/src/main/java/org/apache/ranger/db/XXAuthSessionDao.java 
475b27846 
  
security-admin/src/main/java/org/apache/ranger/db/XXContextEnricherDefDao.java 
c3d322dc4 
  security-admin/src/main/java/org/apache/ranger/db/XXCredentialStoreDao.java 
1e6c443e2 
  security-admin/src/main/java/org/apache/ranger/db/XXDBBaseDao.java 2a64c8952 
  security-admin/src/main/java/org/apache/ranger/db/XXDataHistDao.java 
b5e785569 
  security-admin/src/main/java/org/apache/ranger/db/XXDataMaskTypeDefDao.java 
f6e1aff0b 
  security-admin/src/main/java/org/apache/ranger/db/XXEnumDefDao.java 2590455ac 
  security-admin/src/main/java/org/apache/ranger/db/XXEnumElementDefDao.java 
4b7fb708c 
  security-admin/src/main/java/org/apache/ranger/db/XXGroupDao.java 19e2e11f3 
  security-admin/src/main/java/org/apache/ranger/db/XXGroupGroupDao.java 
cbe95f93b 
  security-admin/src/main/java/org/apache/ranger/db/XXGroupPermissionDao.java 
9281cb5e5 
  security-admin/src/main/java/org/apache/ranger/db/XXGroupUserDao.java 
c8c105de4 
  security-admin/src/main/java/org/apache/ranger/db/XXModuleDefDao.java 
85f284690 
  security-admin/src/main/java/org/apache/ranger/db/XXPermMapDao.java c455fdc45 
  security-admin/src/main/java/org/apache/ranger/db/XXPluginInfoDao.java 
8eb163605 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyConditionDefDao.java 
21afcac89 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyDao.java 562351710 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyExportAuditDao.java 
d2fc6e2d7 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemAccessDao.java 
de37e10cd 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemConditionDao.java 
11596ef4d 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemDao.java 
567717333 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemDataMaskInfoDao.java
 a8418c626 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemGroupPermDao.java 
8c05699b2 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemRowFilterInfoDao.java
 4618e7dc7 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyItemUserPermDao.java 
40a0da13b 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyResourceDao.java 
4b04b9664 
  security-admin/src/main/java/org/apache/ranger/db/XXPolicyResourceMapDao.java 
70657370a 
  
security-admin/src/main/java/org/apache/ranger/db/XXPolicyWithAssignedIdDao.java
 2353bf0b7 
  security-admin/src/main/java/org/apache/ranger/db/XXPortalUserDao.java 
98411317e 
  security-admin/src/main/java/org/apache/ranger/db/XXPortalUserRoleDao.java 
adf100ad6 
  security-admin/src/main/java/org/apache/ranger/db/XXResourceDao.java 
9fa77f20a 
  security-admin/src/main/java/org/apache/ranger/db/XXResourceDefDao.java 
aee56e833 
  security-admin/src/main/java/org/apache/ranger/db/XXServiceConfigDefDao.java 
30a9ce8e0 
  security-admin/src/main/java/org/apache/ranger/db/XXServiceConfigMapDao.java 
9f97b6073 
  security-admin/src/main/java/org/apache/ranger/db/XXServiceDao.java 93c65a840 
  security-admin/src/main/java/org/apache/ranger/db/XXServiceDefDao.java 
dd32c3a41 
  
security-admin/src/main/java/org/apache/ranger/db/XXServiceDefWithAssignedIdDao.java
 7e866d295 
  security-admin/src/main/java/org/apache/ranger/db/XXServiceResourceDao.java 
f87c0ae59 
  
security-admin/src/main/java/org/apache/ranger/db/XXServiceResourceElementDao.java
 72fe2140b

[jira] [Updated] (RANGER-2107) Use Spring to inject DAOs

2018-05-17 Thread Zsombor Gegesy (JIRA) 

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

Zsombor Gegesy updated RANGER-2107:
---
Attachment: RANGER-2107.patch

> Use Spring to inject DAOs
> -
>
> Key: RANGER-2107
> URL: https://issues.apache.org/jira/browse/RANGER-2107
> Project: Ranger
>  Issue Type: Bug
>  Components: admin
>Affects Versions: 1.0.0
>Reporter: Zsombor Gegesy
>Assignee: Zsombor Gegesy
>Priority: Major
>  Labels: code-cleanup, codehealth
> Fix For: 1.1.0
>
> Attachments: RANGER-2107.patch
>
>
> Currently, instead of relying on Spring to inject the DAOs internally, Ranger 
> use a RangerDaoManager to create and acquire objects, which lead to a lot of 
> unnecessary generic code which complicates the code. 
>  Instead of this, all the 'DAO' needs a simple '@Service' annotation, and 
> RangerBaseModelService.entityDao and AbstractBaseResourceService.entityDao 
> can be marked as @Autowired - and Spring will do her job. (Spring before <4.0 
> were unable to autowire fields based on the generic parameters). 
> Later all the RangerDaoManagerBase method could be removed.



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

[jira] [Created] (RANGER-2107) Use Spring to inject DAOs

2018-05-17 Thread Zsombor Gegesy (JIRA) 
Zsombor Gegesy created RANGER-2107:
--

 Summary: Use Spring to inject DAOs
 Key: RANGER-2107
 URL: https://issues.apache.org/jira/browse/RANGER-2107
 Project: Ranger
  Issue Type: Bug
  Components: admin
Affects Versions: 1.0.0
Reporter: Zsombor Gegesy
Assignee: Zsombor Gegesy
 Fix For: 1.1.0


Currently, instead of relying on Spring to inject the DAOs internally, Ranger 
use a RangerDaoManager to create and acquire objects, which lead to a lot of 
unnecessary generic code which complicates the code. 
 Instead of this, all the 'DAO' needs a simple '@Service' annotation, and 
RangerBaseModelService.entityDao and AbstractBaseResourceService.entityDao can 
be marked as @Autowired - and Spring will do her job. (Spring before <4.0 were 
unable to autowire fields based on the generic parameters). 
Later all the RangerDaoManagerBase method could be removed.



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

Review Request 67192: RANGER-2105:Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY

2018-05-17 Thread Ramesh Mani 

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

Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, Thejas Nair, and 
Velmurugan Periasamy.


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


Repository: ranger


Description
---

RANGER-2105:Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY


Diffs
-

  
hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java
 780afac 


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


Testing
---

Testing done in Local VM


Thanks,

Ramesh Mani

[jira] [Assigned] (RANGER-2105) Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY

2018-05-17 Thread Ramesh Mani (JIRA) 

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

Ramesh Mani reassigned RANGER-2105:
---

Assignee: Ramesh Mani

> Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY
> ---
>
> Key: RANGER-2105
> URL: https://issues.apache.org/jira/browse/RANGER-2105
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 1.0.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0
>
>
> Ranger HiveAuthorization for INSERT OVERWRITE DIRECTORY



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

[jira] [Updated] (RANGER-2093) RangerHiveAuthorizer showPrivileges should show Hive Objects ACLs from Ranger

2018-05-17 Thread Ramesh Mani (JIRA) 

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

Ramesh Mani updated RANGER-2093:

Fix Version/s: 1.0.0

> RangerHiveAuthorizer showPrivileges should show Hive Objects ACLs from Ranger
> -
>
> Key: RANGER-2093
> URL: https://issues.apache.org/jira/browse/RANGER-2093
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0, 1.1.0
>
>
> RangerHiveAuthorizer showPrivileges should show Hive Resources ACLs from 
> Ranger Policies Currently StandardSQLAuth ACLs is shown when the call is made 
> and this is misleading. 
> Proposal is to show privileges for a Hive Resource or  Hive Resource and 
> user/group from Ranger Policies when ranger plugin is enabled for hive.
>  



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

[jira] [Updated] (RANGER-2093) RangerHiveAuthorizer showPrivileges should show Hive Objects ACLs from Ranger

2018-05-17 Thread Ramesh Mani (JIRA) 

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

Ramesh Mani updated RANGER-2093:

Affects Version/s: 1.0.0

> RangerHiveAuthorizer showPrivileges should show Hive Objects ACLs from Ranger
> -
>
> Key: RANGER-2093
> URL: https://issues.apache.org/jira/browse/RANGER-2093
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Ramesh Mani
>Assignee: Ramesh Mani
>Priority: Major
> Fix For: 1.0.0, 1.1.0
>
>
> RangerHiveAuthorizer showPrivileges should show Hive Resources ACLs from 
> Ranger Policies Currently StandardSQLAuth ACLs is shown when the call is made 
> and this is misleading. 
> Proposal is to show privileges for a Hive Resource or  Hive Resource and 
> user/group from Ranger Policies when ranger plugin is enabled for hive.
>  



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

[jira] [Comment Edited] (RANGER-2104) Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits

2018-05-17 Thread Abhay Kulkarni (JIRA) 

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

Abhay Kulkarni edited comment on RANGER-2104 at 5/17/18 5:00 PM:
-

Patch is available at the review board:

ranger-0.7:

[https://reviews.apache.org/r/67160/]


was (Author: abhayk):
Patch is available at the review board:

https://reviews.apache.org/r/67160/

> Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does 
> not have associated traits
> ---
>
> Key: RANGER-2104
> URL: https://issues.apache.org/jira/browse/RANGER-2104
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 1.0.0, master, 0.7.1
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
> Fix For: master, 0.7.2, 1.0.1
>
>
> Tagsync may receive a large number of ENTITY_UPDATE events when used in a 
> large EDW environment. If an update entity is not associated with any tags 
> (aka traits, classifications), then this event does not have material impact 
> on the resource->tag associations in the Ranger, and therefore, can be safely 
> dropped. Processing such event adds processing overhead to tagsync, 
> ranger-admin and network, and also causes ranger-admin database to be 
> populated with service-resource that is not tagged and is not needed for 
> access evaluation.



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

[jira] [Comment Edited] (RANGER-2104) Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits

2018-05-17 Thread Abhay Kulkarni (JIRA) 

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

Abhay Kulkarni edited comment on RANGER-2104 at 5/17/18 5:00 PM:
-

Patch is available at the review board:

Patch for ranger-0.7:

[https://reviews.apache.org/r/67160/]


was (Author: abhayk):
Patch is available at the review board:

ranger-0.7:

[https://reviews.apache.org/r/67160/]

> Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does 
> not have associated traits
> ---
>
> Key: RANGER-2104
> URL: https://issues.apache.org/jira/browse/RANGER-2104
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync
>Affects Versions: 1.0.0, master, 0.7.1
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
> Fix For: master, 0.7.2, 1.0.1
>
>
> Tagsync may receive a large number of ENTITY_UPDATE events when used in a 
> large EDW environment. If an update entity is not associated with any tags 
> (aka traits, classifications), then this event does not have material impact 
> on the resource->tag associations in the Ranger, and therefore, can be safely 
> dropped. Processing such event adds processing overhead to tagsync, 
> ranger-admin and network, and also causes ranger-admin database to be 
> populated with service-resource that is not tagged and is not needed for 
> access evaluation.



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

Re: Review Request 67178: RANGER-2104: Ranger tagsync should ignore ENTITY_UPDATE events if the updated entity does not have associated traits

2018-05-17 Thread Madhan Neethiraj 

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


Ship it!




Ship It!

- Madhan Neethiraj


On May 17, 2018, 3:13 a.m., Abhay Kulkarni wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67178/
> ---
> 
> (Updated May 17, 2018, 3:13 a.m.)
> 
> 
> Review request for ranger and Madhan Neethiraj.
> 
> 
> Bugs: RANGER-2104
> https://issues.apache.org/jira/browse/RANGER-2104
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Tagsync may receive a large number of ENTITY_UPDATE events when used in a 
> large EDW environment. If an update entity is not associated with any tags 
> (aka traits, classifications), then this event does not have material impact 
> on the resource->tag associations in the Ranger, and therefore, can be safely 
> dropped. Processing such event adds processing overhead to tagsync, 
> ranger-admin and network, and also causes ranger-admin database to be 
> populated with service-resource that is not tagged and is not needed for 
> access evaluation.
> 
> 
> Diffs
> -
> 
>   pom.xml c7632bac9 
>   src/main/assembly/tagsync.xml 0b17151b9 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasNotificationMapper.java
>  f007ae55e 
>   
> tagsync/src/main/java/org/apache/ranger/tagsync/source/atlas/AtlasTagSource.java
>  c382db018 
> 
> 
> Diff: https://reviews.apache.org/r/67178/diff/2/
> 
> 
> Testing
> ---
> 
> Tested with local VM
> 
> 
> Thanks,
> 
> Abhay Kulkarni
> 
>

Re: Request to add me as a contributor.

2018-05-17 Thread Velmurugan Periasamy 
Welcome to Ranger community. I have added you as contributor.

From:  Dhaval Rajpara 
Reply-To:  "dev@ranger.apache.org" 
Date:  Wednesday, May 16, 2018 at 1:19 AM
To:  "dev@ranger.apache.org" 
Subject:  Request to add me as a contributor.

Hi All,

I would like to contribute to Apache Ranger project, Can
you please add me as a contributor to the project?

Thanks,
Dhaval Rajpara

[jira] [Updated] (RANGER-2106) Keyadmin is not able to see 'Audit tab' and 'User tab' by default.

2018-05-17 Thread Velmurugan Periasamy (JIRA) 

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

Velmurugan Periasamy updated RANGER-2106:
-
Fix Version/s: (was: master)
   1.1.0

> Keyadmin is not able to see 'Audit tab' and 'User tab' by default.
> --
>
> Key: RANGER-2106
> URL: https://issues.apache.org/jira/browse/RANGER-2106
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master
>Reporter: Fatima Amjad Khan
>Assignee: Fatima Amjad Khan
>Priority: Major
> Fix For: 1.1.0
>
> Attachments: RANGER-2106.patch
>
>
> Keyadmin is not able to see audit and user tab by default when consolidated 
> db schema executes



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

Re: Review Request 67151: User is not able to see revoke audits for HBASE.

2018-05-17 Thread Velmurugan Periasamy 

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


Ship it!




Ship It!

- Velmurugan Periasamy


On May 16, 2018, 12:57 p.m., Nikhil P wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67151/
> ---
> 
> (Updated May 16, 2018, 12:57 p.m.)
> 
> 
> Review request for ranger, Don Bosco Durai, Gautam Borad, Abhay Kulkarni, 
> Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja 
> Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2103
> https://issues.apache.org/jira/browse/RANGER-2103
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> User is not able to see revoke audits for HBASE.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java b2a43d2 
>   
> security-admin/src/main/java/org/apache/ranger/solr/SolrAccessAuditsService.java
>  397639b 
> 
> 
> Diff: https://reviews.apache.org/r/67151/diff/1/
> 
> 
> Testing
> ---
> 
> validated if user is able to see grant/revoke audits for hbase.
> validated if user is able to see grant/revoke audits for hive.
> 
> 
> Thanks,
> 
> Nikhil P
> 
>

Review Request 67181: RANGER-2106 : Keyadmin is not able to see 'Audit tab' and 'User tab' by default.

2018-05-17 Thread Fatima Khan 

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

Review request for ranger.


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


Repository: ranger


Description
---

Keyadmin user is not able to see audit and user tab by default when 
consolidated db schema executes.


Diffs
-

  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 23c3562 
  security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql eb12d56 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
f60ad5c 
  
security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql 
91f7b7a 
  security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
28c89dc 


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


Testing
---

Tested that Keyadmin gets by default access to users/groups tab and Audit tab


Thanks,

Fatima Khan

[jira] [Updated] (RANGER-2106) Keyadmin is not able to see 'Audit tab' and 'User tab' by default.

2018-05-17 Thread Fatima Amjad Khan (JIRA) 

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

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

> Keyadmin is not able to see 'Audit tab' and 'User tab' by default.
> --
>
> Key: RANGER-2106
> URL: https://issues.apache.org/jira/browse/RANGER-2106
> 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-2106.patch
>
>
> Keyadmin is not able to see audit and user tab by default when consolidated 
> db schema executes



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

[jira] [Created] (RANGER-2106) Keyadmin is not able to see 'Audit tab' and 'User tab' by default.

2018-05-17 Thread Fatima Amjad Khan (JIRA) 
Fatima Amjad Khan created RANGER-2106:
-

 Summary: Keyadmin is not able to see 'Audit tab' and 'User tab' by 
default.
 Key: RANGER-2106
 URL: https://issues.apache.org/jira/browse/RANGER-2106
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: master
Reporter: Fatima Amjad Khan
Assignee: Fatima Amjad Khan
 Fix For: master


Keyadmin is not able to see audit and user tab by default when consolidated db 
schema executes



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