[jira] [Created] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names
Harshal Chavan created RANGER-4615: -- Summary: Keep the LDAP usersync details popup names same as the backbone js names Key: RANGER-4615 URL: https://issues.apache.org/jira/browse/RANGER-4615 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan The data field names are different in the usersync audits sync details popup in ReactJS when compared to backbone JS. Ideally, both BackBone JS and React JS field names should be the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4615) Keep the LDAP usersync details popup names same as the backbone js names
[ https://issues.apache.org/jira/browse/RANGER-4615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan reassigned RANGER-4615: -- Assignee: Mugdha Varadkar > Keep the LDAP usersync details popup names same as the backbone js names > > > Key: RANGER-4615 > URL: https://issues.apache.org/jira/browse/RANGER-4615 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Mugdha Varadkar >Priority: Major > > The data field names are different in the usersync audits sync details popup > in ReactJS when compared to backbone JS. > Ideally, both BackBone JS and React JS field names should be the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4424) Security zone: Should be able to create security zone without any resource
[ https://issues.apache.org/jira/browse/RANGER-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-4424: --- Description: Due to RANGER-4286 we need to handle from UI also to crete security zone without any resource Steps 1.Create a zone without any resource 2.Click on edit zone button was:RANGER-4286 removed the restriction that a security zone must have at least one service and one resource. UI should be updated to remove this validation, to allow create/update of security zones with no service/resource. > Security zone: Should be able to create security zone without any resource > -- > > Key: RANGER-4424 > URL: https://issues.apache.org/jira/browse/RANGER-4424 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Harshal Chavan >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > > Due to RANGER-4286 we need to handle from UI also to crete security zone > without any resource > Steps > 1.Create a zone without any resource > 2.Click on edit zone button -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4424) Security zone: Should be able to create security zone without any resource
[ https://issues.apache.org/jira/browse/RANGER-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-4424: --- Summary: Security zone: Should be able to create security zone without any resource (was: Security zone: Should be able to create ) > Security zone: Should be able to create security zone without any resource > -- > > Key: RANGER-4424 > URL: https://issues.apache.org/jira/browse/RANGER-4424 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > > Steps > 1.Create a zone without any resource > 2.Click on edit zone button -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4424) Security zone: Should be able to create security zone without any resource
[ https://issues.apache.org/jira/browse/RANGER-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-4424: --- Issue Type: Improvement (was: Bug) > Security zone: Should be able to create security zone without any resource > -- > > Key: RANGER-4424 > URL: https://issues.apache.org/jira/browse/RANGER-4424 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Harshal Chavan >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > > Steps > 1.Create a zone without any resource > 2.Click on edit zone button -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4424) Security zone: Should be able to create
[ https://issues.apache.org/jira/browse/RANGER-4424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-4424: --- Summary: Security zone: Should be able to create (was: 'Something went wrong' page is displayed when zone edit button is clicked having no resource) > Security zone: Should be able to create > > > Key: RANGER-4424 > URL: https://issues.apache.org/jira/browse/RANGER-4424 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > > Steps > 1.Create a zone without any resource > 2.Click on edit zone button -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4424) 'Something went wrong' page is displayed when zone edit button is clicked having no resource
Harshal Chavan created RANGER-4424: -- Summary: 'Something went wrong' page is displayed when zone edit button is clicked having no resource Key: RANGER-4424 URL: https://issues.apache.org/jira/browse/RANGER-4424 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Assignee: Brijesh Bhalala Steps 1.Create a zone without any resource 2.Click on edit zone button -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4360) On error page Go back button not work properly
Harshal Chavan created RANGER-4360: -- Summary: On error page Go back button not work properly Key: RANGER-4360 URL: https://issues.apache.org/jira/browse/RANGER-4360 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan On error page Go back button not work properly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4187) Not able to search using muliple user filter in access audit tab
Harshal Chavan created RANGER-4187: -- Summary: Not able to search using muliple user filter in access audit tab Key: RANGER-4187 URL: https://issues.apache.org/jira/browse/RANGER-4187 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Steps 1. Go to access audit tab 2. Search with one user 3. Try selecting user filter again Note - we dont see user filter in 3 step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-3797) Not able to create security zone for solr service after upgrade
Harshal Chavan created RANGER-3797:
--
Summary: Not able to create security zone for solr service after
upgrade
Key: RANGER-3797
URL: https://issues.apache.org/jira/browse/RANGER-3797
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Harshal Chavan
{code:java}
2022-06-17 10:51:26,622 INFO
org.apache.ranger.plugin.service.RangerBaseService: cm_solr: adding default
policy: name=RANGER_AUDITS_COLLECTION
2022-06-17 10:51:26,733 ERROR
org.apache.ranger.service.RangerSecurityZoneServiceService: postCreate
processing failed for security-zone:[{name=z1, services={cm_solr={resources={[
{resource-def-name=admin, values=[gbgfbfb]}, ],}}}, tagServices=[],
adminUsers=[rangerusersync], adminUserGroups=[], auditUsers=[keyadmin],
auditUserGroups=[], description=}]
java.lang.Exception: others: is not a valid access-type.
policy='RANGER_AUDITS_COLLECTION' service='cm_solr'
at
org.apache.ranger.biz.PolicyRefUpdater.createNewPolMappingForRefTable(PolicyRefUpdater.java:233)
at
org.apache.ranger.biz.ServiceDBStore.createPolicy(ServiceDBStore.java:2028)
at
org.apache.ranger.biz.ServiceDBStore.createZoneDefaultPolicies(ServiceDBStore.java:3288)
at
org.apache.ranger.service.RangerSecurityZoneServiceService.postCreate(RangerSecurityZoneServiceService.java:140)
at
org.apache.ranger.service.RangerSecurityZoneServiceService.postCreate(RangerSecurityZoneServiceService.java:52)
at
org.apache.ranger.service.RangerBaseModelService.create(RangerBaseModelService.java:226)
{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (RANGER-3568) Services of one zone are seen in other zone from UI
Harshal Chavan created RANGER-3568: -- Summary: Services of one zone are seen in other zone from UI Key: RANGER-3568 URL: https://issues.apache.org/jira/browse/RANGER-3568 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Services of one zone are seen in other zone from Ranger UI Steps 1.Create zone 'zone1' with HBASE, HIVE, KAFKA, ATLAS service 2.Craete zone 'zone2' with 'KAFKA' service 3.Now go to unzone resource based page 4.From dropdown select 'zone1' you will see HBASE, HIVE, KAFKA, ATLAS service 5.Now select 'zone2' from zone dropdown we see HBASE, HIVE, KAFKA, ATLAS service and for KAFKA we see 2 services but as per step2 only KAFKA service is there in zone2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3516) Java patch 'J10045' taking more time during upgrade.
Harshal Chavan created RANGER-3516: -- Summary: Java patch 'J10045' taking more time during upgrade. Key: RANGER-3516 URL: https://issues.apache.org/jira/browse/RANGER-3516 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan J10045 patch is taking more time to apply when we upgrade -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3352) Create table query wont work in same session till we run show roles command
Harshal Chavan created RANGER-3352: -- Summary: Create table query wont work in same session till we run show roles command Key: RANGER-3352 URL: https://issues.apache.org/jira/browse/RANGER-3352 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Steps - 1.Create a db (vehicle) with hive user 2.create a user 'unixuser1' and make him admin from Ranger 3.login into beeline with unixuser1 4.create a role Create role unixrole1; 5.Run show role query 6.create a role Create role unixrole2; 7.create a access policy with create permission for the role unixrole2 8.Run create table query in same session created he will be denied create table vehicle.unixrole2(car_id int, car_name string, car_color string, car_price int); 9.Run show role query in same session 10.now again run create query in same session created now he will be allowed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3338) Masking and Row filter policy are getting exported from report page when Policy type=Access
Harshal Chavan created RANGER-3338: -- Summary: Masking and Row filter policy are getting exported from report page when Policy type=Access Key: RANGER-3338 URL: https://issues.apache.org/jira/browse/RANGER-3338 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Steps 1.Create a policy in hive masking and hive row. 2.Go to report page 3.Export excel, csv and json 4.Check the exported file it has masking and row filter policy also. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3272) Zone tag policies are getting deleted when zone is updated
[ https://issues.apache.org/jira/browse/RANGER-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-3272: --- Fix Version/s: 2.2.0 3.0.0 > Zone tag policies are getting deleted when zone is updated > -- > > Key: RANGER-3272 > URL: https://issues.apache.org/jira/browse/RANGER-3272 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Assignee: Mateen Mansoori >Priority: Major > Fix For: 3.0.0, 2.2.0 > > > Zone tag policies are getting deleted when zone is updated > Steps to reproduce : > 1.Create a zone with tag service and some service like yarn service. > 2.Create a tag policy in zone > 3.Edit the zone by adding new service like hive service with existing service. > 4.Click on save > 5.Check the tag policy created in step 2. The tag policy gets deleted -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3044) User is not able to change the password from user profile page
Harshal Chavan created RANGER-3044: -- Summary: User is not able to change the password from user profile page Key: RANGER-3044 URL: https://issues.apache.org/jira/browse/RANGER-3044 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Steps 1.Create a user with any role from UI 2.Login with that user 3.Go to User profile page 4.Go to change password 5.Try to change the password -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2794) Search is not working in Role page
Harshal Chavan created RANGER-2794: -- Summary: Search is not working in Role page Key: RANGER-2794 URL: https://issues.apache.org/jira/browse/RANGER-2794 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2790) Import start and import end are not in sequence
Harshal Chavan created RANGER-2790: -- Summary: Import start and import end are not in sequence Key: RANGER-2790 URL: https://issues.apache.org/jira/browse/RANGER-2790 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2762) Logout issue when knox-trusted proxy is enabled
Harshal Chavan created RANGER-2762: -- Summary: Logout issue when knox-trusted proxy is enabled Key: RANGER-2762 URL: https://issues.apache.org/jira/browse/RANGER-2762 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2727) Ghost policy occurs in plugin when creating and getting policies concurrently
[
https://issues.apache.org/jira/browse/RANGER-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034193#comment-17034193
]
Harshal Chavan commented on RANGER-2727:
[~stigahuang] - Tried on apache master, was not able to reproduce the issue
with 7000 rounds. But one thing i observed that when i stop the script
aftersome and do not refresh the page and try to delete the policy then i get
the issue '*org.apache.ranger.plugin.model.RangerPolicy :Data Not Found for
given Id*' which is correct because the policy is deleted but page is not
refreshed, and when i refresh the page the policy wont be there.
> Ghost policy occurs in plugin when creating and getting policies concurrently
> -
>
> Key: RANGER-2727
> URL: https://issues.apache.org/jira/browse/RANGER-2727
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: Quanlong Huang
>Assignee: Quanlong Huang
>Priority: Major
> Attachments: create_delete_policy.py
>
>
> Attached a python script to reproduce this issue. It creates and deletes 10
> column masking policies repeatedly. Run it and refresh column masking
> policies in Hive service in Ranger Admin UI. Some policies won't be deleted
> after several rounds.
> Delete them manually in Ranger Admin UI will get an error as
> org.apache.ranger.plugin.model.RangerPolicy :Data Not Found for given Id
> Can't neither view them nor edit them. The web UI will hang. Ranger logs
> reveal the same error:
> {code}
> 2020-02-10 03:08:05,597 [http-bio-6080-exec-2] INFO
> org.apache.ranger.common.RESTErrorUtil (RESTErrorUtil.java:63) - Request
> failed. loginId=admin, logMessage=org.apache.ranger.plugin.model.RangerPolicy
> :Data Not Found for given Id
> javax.ws.rs.WebApplicationException
> at
> org.apache.ranger.common.RESTErrorUtil.createRESTException(RESTErrorUtil.java:56)
> at
> org.apache.ranger.common.RESTErrorUtil.createRESTException(RESTErrorUtil.java:301)
> at
> org.apache.ranger.service.RangerBaseModelService.read(RangerBaseModelService.java:240)
> at
> org.apache.ranger.biz.ServiceDBStore.getPolicy(ServiceDBStore.java:2171)
> at org.apache.ranger.rest.ServiceREST.getPolicy(ServiceREST.java:1829)
> at
> org.apache.ranger.rest.ServiceREST$$FastClassBySpringCGLIB$$92dab672.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
> at
> org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:282)
> at
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
> at
> org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
> at
> org.apache.ranger.rest.ServiceREST$$EnhancerBySpringCGLIB$$315c4133.getPolicy()
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.applic
[jira] [Resolved] (RANGER-2598) Last update time of tag services under "Plugin Status" tab are not getting updated.
[ https://issues.apache.org/jira/browse/RANGER-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan resolved RANGER-2598. Resolution: Not A Bug > Last update time of tag services under "Plugin Status" tab are not getting > updated. > --- > > Key: RANGER-2598 > URL: https://issues.apache.org/jira/browse/RANGER-2598 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Harshal Chavan >Priority: Major > > 'Last update' time under Tag(Time) column of "Plugin Status" tab in Audit > page is not getting updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2602) Import is failing with "Can not construct instance of java.util.Date from String" error
Harshal Chavan created RANGER-2602: -- Summary: Import is failing with "Can not construct instance of java.util.Date from String" error Key: RANGER-2602 URL: https://issues.apache.org/jira/browse/RANGER-2602 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Steps to reproduce 1.Create a service 'Hdfsservice1' 2.Create a new policy 'Hdfspolicy1' 3.Export the policies of 'Hdfsservice1' 4.Import the same policies in 'Hdfsservice1' -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2598) Last update time of tag services under "Plugin Status" tab are not getting updated.
Harshal Chavan created RANGER-2598: -- Summary: Last update time of tag services under "Plugin Status" tab are not getting updated. Key: RANGER-2598 URL: https://issues.apache.org/jira/browse/RANGER-2598 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan 'Last update' time under Tag(Time) column of "Plugin Status" tab in Audit page is not getting updated -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2523) Ranger Admin debug config improvement
Harshal Chavan created RANGER-2523: -- Summary: Ranger Admin debug config improvement Key: RANGER-2523 URL: https://issues.apache.org/jira/browse/RANGER-2523 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Improvement in debug log config -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (RANGER-2445) Import of Tagservice for zone
Harshal Chavan created RANGER-2445: -- Summary: Import of Tagservice for zone Key: RANGER-2445 URL: https://issues.apache.org/jira/browse/RANGER-2445 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Import of tagservice is not working for zone -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2444) Admin logs are not getting generated when "policy level" policy condition is updated
Harshal Chavan created RANGER-2444: -- Summary: Admin logs are not getting generated when "policy level" policy condition is updated Key: RANGER-2444 URL: https://issues.apache.org/jira/browse/RANGER-2444 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Steps- 1.Create a Knox service. 2.Edit the "policy level" policy condition of default policy. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2441) Import of Tagservice for zone
Harshal Chavan created RANGER-2441: -- Summary: Import of Tagservice for zone Key: RANGER-2441 URL: https://issues.apache.org/jira/browse/RANGER-2441 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Harshal Chavan Import of tagservice is not working for zone -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2411) Restrict Admin role user to create Zone for KMS service
[
https://issues.apache.org/jira/browse/RANGER-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harshal Chavan updated RANGER-2411:
---
Description:
Expected Result: Admin role user should not be allowed to create Zone for KMS
service.
CURL Request: curl -i -u admin:admin123 --header "Accept:application/json" -H
"Content-Type: application/json" -X POST
http://:6080/service/zones/zones -d
'{"adminUserGroups":["admingroup1"],"adminUsers":["admintest1"],"auditUserGroups":["auditgroup1"],"auditUsers":["auditest1"],"name":"kms-accesspolicy","services":{"cl1_kms":{"resources":[
{"keyname":["kmstest1"]}
]}}}'
was:
Expected Result: Admin role user should not be allowed to create Zone for KMS
service.
CURL Request: curl -i -u admin:admin123 --header "Accept:application/json" -H
"Content-Type: application/json" -X POST
[http://:6080/service/zones/zones|http://172.22.114.5:6080/service/zones/zones]
-d
'{"adminUserGroups":["admingroup1"],"adminUsers":["admintest1"],"auditUserGroups":["auditgroup1"],"auditUsers":["auditest1"],"name":"kms-accesspolicy","services":{"cl1_kms":{"resources":[
{"keyname":["kmstest1"]}
]}}}'
> Restrict Admin role user to create Zone for KMS service
> ---
>
> Key: RANGER-2411
> URL: https://issues.apache.org/jira/browse/RANGER-2411
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.0.0
>Reporter: Harshal Chavan
>Assignee: Nikhil Purbhe
>Priority: Major
>
> Expected Result: Admin role user should not be allowed to create Zone for KMS
> service.
> CURL Request: curl -i -u admin:admin123 --header "Accept:application/json" -H
> "Content-Type: application/json" -X POST
> http://:6080/service/zones/zones -d
> '{"adminUserGroups":["admingroup1"],"adminUsers":["admintest1"],"auditUserGroups":["auditgroup1"],"auditUsers":["auditest1"],"name":"kms-accesspolicy","services":{"cl1_kms":{"resources":[
> {"keyname":["kmstest1"]}
> ]}}}'
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2411) Restrict Admin role user to create Zone for KMS service
Harshal Chavan created RANGER-2411:
--
Summary: Restrict Admin role user to create Zone for KMS service
Key: RANGER-2411
URL: https://issues.apache.org/jira/browse/RANGER-2411
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 2.0.0
Reporter: Harshal Chavan
Expected Result: Admin role user should not be allowed to create Zone for KMS
service.
CURL Request: curl -i -u admin:admin123 --header "Accept:application/json" -H
"Content-Type: application/json" -X POST
[http://:6080/service/zones/zones|http://172.22.114.5:6080/service/zones/zones]
-d
'{"adminUserGroups":["admingroup1"],"adminUsers":["admintest1"],"auditUserGroups":["auditgroup1"],"auditUsers":["auditest1"],"name":"kms-accesspolicy","services":{"cl1_kms":{"resources":[
{"keyname":["kmstest1"]}
]}}}'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2262) Improvement of export to excel from report listing page for Oracle database.
[ https://issues.apache.org/jira/browse/RANGER-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-2262: --- Description: (was: Steps - 1.Go to report page. 2.Click on export to excel.) > Improvement of export to excel from report listing page for Oracle database. > > > Key: RANGER-2262 > URL: https://issues.apache.org/jira/browse/RANGER-2262 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Harshal Chavan >Priority: Major > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2262) Improvement of export to excel from report listing page for Oracle database.
Harshal Chavan created RANGER-2262: -- Summary: Improvement of export to excel from report listing page for Oracle database. Key: RANGER-2262 URL: https://issues.apache.org/jira/browse/RANGER-2262 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Harshal Chavan Fix For: 2.0.0 Steps - 1.Go to report page. 2.Click on export to excel. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2160) 'Email Address' search is not working properly along with other filter in user listing page,userRoles filters also needs to be improved.
[ https://issues.apache.org/jira/browse/RANGER-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan resolved RANGER-2160. Resolution: Resolved > 'Email Address' search is not working properly along with other filter in > user listing page,userRoles filters also needs to be improved. > > > Key: RANGER-2160 > URL: https://issues.apache.org/jira/browse/RANGER-2160 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Harshal Chavan >Assignee: Nikhil Purbhe >Priority: Major > Fix For: 2.0.0 > > Attachments: > RANGER-2160-Email-Address-search-is-not-working-prop.patch > > > Issues related to search in user listing page > 1.Email search is not working in userlisting page. > 2.In userrole if we enter wrong data then it should show invalid data (Eg - > userrole:fbvhbfdhb) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2160) 'Email Address' search is not working properly along with other filter in user listing page,userRoles filters also needs to be improved.
[ https://issues.apache.org/jira/browse/RANGER-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harshal Chavan updated RANGER-2160: --- Description: Issues related to search in user listing page 1.Email search is not working in userlisting page. 2.In userrole if we enter wrong data then it should show invalid data (Eg - userrole:fbvhbfdhb) was: Issues related to search in user listing page 1.Email search is not working in userlisting page. 2.In userrole if we enter wrong data then it should show invalid data (Eg - userrole:fbvhbfdhb) 3.When searched with \admin as username it should not show user list (eg - username:\admin) > 'Email Address' search is not working properly along with other filter in > user listing page,userRoles filters also needs to be improved. > > > Key: RANGER-2160 > URL: https://issues.apache.org/jira/browse/RANGER-2160 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Harshal Chavan >Assignee: Nikhil Purbhe >Priority: Major > Fix For: 2.0.0 > > > Issues related to search in user listing page > 1.Email search is not working in userlisting page. > 2.In userrole if we enter wrong data then it should show invalid data (Eg - > userrole:fbvhbfdhb) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2160) 'Email Address' search is not working in user listing page,userRoles filters also needs to be improved.
Harshal Chavan created RANGER-2160: -- Summary: 'Email Address' search is not working in user listing page,userRoles filters also needs to be improved. Key: RANGER-2160 URL: https://issues.apache.org/jira/browse/RANGER-2160 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0 Reporter: Harshal Chavan Fix For: 2.0.0 Issues related to search in user listing page 1.Email search is not working in userlisting page. 2.In userrole if we enter wrong data then it should show invalid data (Eg - userrole:fbvhbfdhb) 3.When searched with \admin as username it should not show user list (eg - username:\admin) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
