[jira] [Resolved] (RANGER-2663) Add elasticsearch-plugin infomation to README.txt
[ https://issues.apache.org/jira/browse/RANGER-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2663. - Resolution: Fixed > Add elasticsearch-plugin infomation to README.txt > - > > Key: RANGER-2663 > URL: https://issues.apache.org/jira/browse/RANGER-2663 > Project: Ranger > Issue Type: Improvement > Components: documentation > Reporter: Qiang Zhang > Assignee: Qiang Zhang >Priority: Minor > Labels: doc > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2663-Add-elasticsearch-plugin-infomation-to-R.patch > > > As elasticsearch plugin has been submitted and merged into to Ranger, > we should add elasticsearch-plugin infomation to README.txt. > Related Issue: RANGER-2170 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2662) Upgrade Kylin version to 2.6.4
[ https://issues.apache.org/jira/browse/RANGER-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2662. - Resolution: Fixed > Upgrade Kylin version to 2.6.4 > -- > > Key: RANGER-2662 > URL: https://issues.apache.org/jira/browse/RANGER-2662 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Qiang Zhang > Assignee: Qiang Zhang >Priority: Major > Fix For: 2.1.0 > > Attachments: 0001-RANGER-2662-Upgrade-Kylin-version-to-2.6.4.patch > > > We should upgrade to the recently release Apache Kylin 2.6.4. No code changes > are required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 71877: RANGER-2663 Add elasticsearch-plugin infomation to README.txt
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71877/ --- Review request for ranger, Don Bosco Durai, Colm O hEigeartaigh, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Velmurugan Periasamy, and Zsombor Gegesy. Bugs: RANGER-2663 https://issues.apache.org/jira/browse/RANGER-2663 Repository: ranger Description --- As elasticsearch plugin has been submitted and merged into to Ranger, we should add elasticsearch-plugin infomation to README.txt. Related Issue: RANGER-2170 Diffs - README.txt 788b281de Diff: https://reviews.apache.org/r/71877/diff/1/ Testing --- Test OK. Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2663) Add elasticsearch-plugin infomation to README.txt
[ https://issues.apache.org/jira/browse/RANGER-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2663: Attachment: 0001-RANGER-2663-Add-elasticsearch-plugin-infomation-to-R.patch > Add elasticsearch-plugin infomation to README.txt > - > > Key: RANGER-2663 > URL: https://issues.apache.org/jira/browse/RANGER-2663 > Project: Ranger > Issue Type: Improvement > Components: documentation > Reporter: Qiang Zhang > Assignee: Qiang Zhang >Priority: Minor > Labels: doc > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2663-Add-elasticsearch-plugin-infomation-to-R.patch > > > As elasticsearch plugin has been submitted and merged into to Ranger, > we should add elasticsearch-plugin infomation to README.txt. > Related Issue: RANGER-2170 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2663) Add elasticsearch-plugin infomation to README.txt
Qiang Zhang created RANGER-2663: --- Summary: Add elasticsearch-plugin infomation to README.txt Key: RANGER-2663 URL: https://issues.apache.org/jira/browse/RANGER-2663 Project: Ranger Issue Type: Improvement Components: documentation Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.1.0 As elasticsearch plugin has been submitted and merged into to Ranger, we should add elasticsearch-plugin infomation to README.txt. Related Issue: RANGER-2170 -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 71876: RANGER-2662 Upgrade Kylin version to 2.6.4
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71876/ --- Review request for ranger, Don Bosco Durai, Colm O hEigeartaigh, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Velmurugan Periasamy, and Zsombor Gegesy. Bugs: RANGER-2662 https://issues.apache.org/jira/browse/RANGER-2662 Repository: ranger Description --- We should upgrade to the recently release Apache Kylin 2.6.4. No code changes are required. Diffs - pom.xml cb04757a8 Diff: https://reviews.apache.org/r/71876/diff/1/ Testing --- Tested Ranger with Kylin 2.6.4 Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2662) Upgrade Kylin version to 2.6.4
[ https://issues.apache.org/jira/browse/RANGER-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2662: Attachment: 0001-RANGER-2662-Upgrade-Kylin-version-to-2.6.4.patch > Upgrade Kylin version to 2.6.4 > -- > > Key: RANGER-2662 > URL: https://issues.apache.org/jira/browse/RANGER-2662 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Qiang Zhang > Assignee: Qiang Zhang >Priority: Major > Fix For: 2.1.0 > > Attachments: 0001-RANGER-2662-Upgrade-Kylin-version-to-2.6.4.patch > > > We should upgrade to the recently release Apache Kylin 2.6.4. No code changes > are required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2662) Upgrade Kylin version to 2.6.4
Qiang Zhang created RANGER-2662: --- Summary: Upgrade Kylin version to 2.6.4 Key: RANGER-2662 URL: https://issues.apache.org/jira/browse/RANGER-2662 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.1.0 We should upgrade to the recently release Apache Kylin 2.6.4. No code changes are required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2170) Ranger supports plugin to enable, monitor and manage Elasticsearch
[ https://issues.apache.org/jira/browse/RANGER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16910925#comment-16910925 ] Qiang Zhang commented on RANGER-2170: - Currently ranger only supports Elasticsearch v6.2.2 I have created JIRA [RANGER-2541|https://issues.apache.org/jira/browse/RANGER-2541] to support Elasticsearch 7.x. > Ranger supports plugin to enable, monitor and manage Elasticsearch > -- > > Key: RANGER-2170 > URL: https://issues.apache.org/jira/browse/RANGER-2170 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: new-feature, patch > Fix For: master, 2.0.0 > > Attachments: > 0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch, > 1_ElasticSearchServiceEntry.jpg, 2_EditElasticSearchService.jpg, > 3_ElasticSearchPolicies.jpg, 4_EditElasticSearchPolicy.jpg, > 5_ElasticSearchAuditLog.jpg, 6_ElasticSearchPlugins.jpg, > 7_ElasticSearchPluginStatus.jpg > > > Elasticsearch is a distributed, RESTful search and analytics engine capable > of solving a growing number of use cases. > Like Apache Solr, it is also an index server based on Lucence. > Ranger supports plugin to enable, monitor and manage Elasticsearch, > to control index security of Elasticsearch. > As there is X-Pack plugin for the Elasticsearch, but it is not free. > X-Pack is an Elastic Stack extension that bundles security, alerting, > monitoring, reporting, > and graph capabilities into one easy-to-install package. > We refer to the Indices Privileges design of X-Pack, > by keeping the permissions consistent, > to make user use ranger Elasticsearch plugin easily. > Reference X-Pack Indices Privileges: > https://www.elastic.co/guide/en/x-pack/current/security-privileges.html > Here we develop Ranger Elasticsearch plugin, based on Elasticsearch version > 6.2.2. > Elasticsearch 6.2.2 was released in February 20, 2018, reference > release-notes: > https://www.elastic.co/guide/en/elasticsearch/reference/6.2/release-notes-6.2.2.html > Not like other system, Elasticsearch has no basic authentication, > it uses X-pack plugin to support basic authentication, > role-based access control, SSL/TLS encryption, LDAP and so on. > Not like X-pack, our Ranger Elasticsearch plugin is designed to do > authorization, > it is to control index of Elasticsearch without authentication, > this plugin should work with other Elasticsearch plugin to authenticate users. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (RANGER-2541) Upgrade Ranger to support Elasticsearch 7.x
Qiang Zhang created RANGER-2541: --- Summary: Upgrade Ranger to support Elasticsearch 7.x Key: RANGER-2541 URL: https://issues.apache.org/jira/browse/RANGER-2541 Project: Ranger Issue Type: New Feature Components: plugins Reporter: Qiang Zhang Assignee: Qiang Zhang We should upgrade Elasticsearch to a more recent release. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang reassigned RANGER-2540: --- Assignee: (was: Qiang Zhang) > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Priority: Trivial > Labels: patch > Attachments: image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (RANGER-2540) When we create a new Solr service, the 'Solr URL' doesn't show a hit that we don't know how to use it.
[ https://issues.apache.org/jira/browse/RANGER-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang reassigned RANGER-2540: --- Assignee: Qiang Zhang > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. > -- > > Key: RANGER-2540 > URL: https://issues.apache.org/jira/browse/RANGER-2540 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: wu.kehua >Assignee: Qiang Zhang >Priority: Trivial > Labels: patch > Attachments: image-2019-08-20-09-09-44-818.png > > > When we create a new Solr service, the 'Solr URL' doesn't show a hit that we > don't know how to use it. As follow picture: > !image-2019-08-20-09-09-44-818.png! -- This message was sent by Atlassian Jira (v8.3.2#803003)
Re: Review Request 71261: RANGER-2533: After setting 'xasecure.audit.is.enabled' to 'false', the audit log is still logged
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71261/#review217258 --- Ship it! Ship It! - Qiang Zhang On 八月 9, 2019, 7:44 a.m., Xing Peng wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/71261/ > --- > > (Updated 八月 9, 2019, 7:44 a.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, > Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan > Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, Velmurugan > Periasamy, Qiang Zhang, and Zsombor Gegesy. > > > Bugs: RANGER-2533 > https://issues.apache.org/jira/browse/RANGER-2533 > > > Repository: ranger > > > Description > --- > > After setting 'xasecure.audit.is.enabled' to 'false', the audit log is still > logged > > > Diffs > - > > > agents-audit/src/main/java/org/apache/ranger/audit/provider/AuditProviderFactory.java > f858efe8f > security-admin/src/test/java/org/apache/ranger/audit/TestAuditQueue.java > cb0dcc4c2 > > > Diff: https://reviews.apache.org/r/71261/diff/2/ > > > Testing > --- > > Test Result: > > > Tested. > > > Thanks, > > Xing Peng > >
Re: Review Request 71261: RANGER-2533: After setting 'xasecure.audit.is.enabled' to 'false', the audit log is still logged
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71261/#review217238 --- Maven test failed, please fix! Results : Tests in error: TestAuditQueue.testAuditSummaryByInfra:197 ClassCast org.apache.ranger.audit.p... Tests run: 821, Failures: 0, Errors: 1, Skipped: 1 - Qiang Zhang On 八月 9, 2019, 7:44 a.m., Xing Peng wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/71261/ > --- > > (Updated 八月 9, 2019, 7:44 a.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, > Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan > Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, Velmurugan > Periasamy, Qiang Zhang, and Zsombor Gegesy. > > > Bugs: RANGER-2533 > https://issues.apache.org/jira/browse/RANGER-2533 > > > Repository: ranger > > > Description > --- > > After setting 'xasecure.audit.is.enabled' to 'false', the audit log is still > logged > > > Diffs > - > > > agents-audit/src/main/java/org/apache/ranger/audit/provider/AuditProviderFactory.java > f858efe8f > > > Diff: https://reviews.apache.org/r/71261/diff/1/ > > > Testing > --- > > Test Result: > > > Tested. > > > Thanks, > > Xing Peng > >
Re: Review Request 71152: RANGER-2514: Search field validation prompt is inconsistent with field names in audit page
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/71152/#review216883 --- Ship it! Ship It! - Qiang Zhang On July 24, 2019, 7:37 a.m., Xing Peng wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/71152/ > --- > > (Updated July 24, 2019, 7:37 a.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, > Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan > Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, Velmurugan > Periasamy, Qiang Zhang, and Zsombor Gegesy. > > > Bugs: RANGER-2514 > https://issues.apache.org/jira/browse/RANGER-2514 > > > Repository: ranger > > > Description > --- > > In Audit Page > > Access tab: > Search field validation prompt is inconsistent with field names in audit page. > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/rest/AssetREST.java > 347e24752 > > > Diff: https://reviews.apache.org/r/71152/diff/1/ > > > Testing > --- > > Test Result: > > Tested. > > > Thanks, > > Xing Peng > >
Re: Review Request 70456: RANGER-2374
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/70456/#review214718 --- security-admin/src/main/java/org/apache/ranger/patch/PatchForHiveServiceDefUpdate_J10027.java Lines 1 (patched) <https://reviews.apache.org/r/70456/#comment300936> Please add license header - Qiang Zhang On April 11, 2019, 9 p.m., Austin Nobis wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/70456/ > --- > > (Updated April 11, 2019, 9 p.m.) > > > Review request for ranger. > > > Bugs: RANGER-2374 > https://issues.apache.org/jira/browse/RANGER-2374 > > > Repository: ranger > > > Description > --- > > Created a patch file for the Hive Service Definition to add the Refresh > access type. This is to support sharing a service definition between Apache > Hive and Apache Impala. > > > Diffs > - > > agents-common/src/main/resources/service-defs/ranger-servicedef-hive.json > b0f877a01 > security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql > 2eaffccac > security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql > 5ca1e3667 > security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql > 51f4999f7 > > security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql > 5f64a2dba > security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql > fc21cec3e > > security-admin/src/main/java/org/apache/ranger/patch/PatchForHiveServiceDefUpdate_J10027.java > PRE-CREATION > > > Diff: https://reviews.apache.org/r/70456/diff/6/ > > > Testing > --- > > > Thanks, > > Austin Nobis > >
Re: Review Request 70260: RANGER-2367:Hive show grants when Ranger is authorizer should show permission details from Ranger
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/70260/#review214070 --- hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java Lines 1641 (patched) <https://reviews.apache.org/r/70260/#comment300243> Lines 1641-1652 are better to extract method - Qiang Zhang On 三月 21, 2019, 12:59 a.m., Ramesh Mani wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/70260/ > --- > > (Updated 三月 21, 2019, 12:59 a.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-2367 > https://issues.apache.org/jira/browse/RANGER-2367 > > > Repository: ranger > > > Description > --- > > RANGER-2367:Hive show grants when Ranger is authorizer should show permission > details from Ranger > > > Diffs > - > > > agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerPolicyEngineImpl.java > c00f072 > > agents-common/src/main/java/org/apache/ranger/plugin/policyengine/RangerResourceACLs.java > adee37e > > hive-agent/src/main/java/org/apache/ranger/authorization/hive/authorizer/RangerHiveAuthorizer.java > 0f3bee5 > > hive-agent/src/test/java/org/apache/ranger/services/hive/HIVERangerAuthorizerTest.java > af60479 > > ranger-examples/conditions-enrichers/src/main/java/org/apache/ranger/plugin/contextenricher/RangerSampleProjectProvider.java > df6da7c > > > Diff: https://reviews.apache.org/r/70260/diff/1/ > > > Testing > --- > > Testing done in Local VM. > > > Thanks, > > Ramesh Mani > >
[jira] [Commented] (RANGER-2381) Failed to refresh policies when servicename contains space
[ https://issues.apache.org/jira/browse/RANGER-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802350#comment-16802350 ] Qiang Zhang commented on RANGER-2381: - Review Requet: https://reviews.apache.org/r/70312/ > Failed to refresh policies when servicename contains space > -- > > Key: RANGER-2381 > URL: https://issues.apache.org/jira/browse/RANGER-2381 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2381-Failed-to-refresh-policies-when-servicen.patch > > > 2019-03-26 19:30:32,657 ERROR [http-bio-7070-exec-8] util.PolicyRefresher:275 > : PolicyRefresher(serviceName=kylin service): failed to refresh policies. > Will continue to use last known version of policies (-1) > java.lang.IllegalArgumentException: Illegal character in path at index 65: > http//:10.43.159.143:6080/service/plugins/policies/download/kylin service > at java.net.URI.create(URI.java:852) > at com.sun.jersey.api.client.Client.resource(Client.java:433) > at > org.apache.ranger.plugin.util.RangerRESTClient.getResource(RangerRESTClient.java:156) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.createWebResource(RangerAdminRESTClient.java:285) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:134) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:251) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:191) > at > org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:137) > at > org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:235) > at > org.apache.ranger.authorization.kylin.authorizer.RangerKylinPlugin.init(RangerKylinAuthorizer.java:152) > at > org.apache.ranger.authorization.kylin.authorizer.RangerKylinAuthorizer.init(RangerKylinAuthorizer.java:66) > at > org.apache.ranger.authorization.kylin.authorizer.RangerKylinAuthorizer.init(RangerKylinAuthorizer.java:68) > at > org.apache.kylin.rest.security.ExternalAclProvider.getInstance(ExternalAclProvider.java:45) > at > org.apache.kylin.rest.security.KylinAclPermissionEvaluator.hasPermission(KylinAclPermissionEvaluator.java:45) > at > org.springframework.security.access.expression.SecurityExpressionRoot.hasPermission(SecurityExpressionRoot.java:177) > 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:483) > at > org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:113) > at > org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:129) > at > org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:85) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) > at > org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:50) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) > at > org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) > at > org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) > at >
Review Request 70312: RANGER-2381 Failed to refresh policies when servicename contains space
/RangerAdminRESTClient.java b6a9380a4 ugsync/src/main/java/org/apache/ranger/ldapusersync/process/LdapPolicyMgrUserGroupBuilder.java f653b81f3 ugsync/src/main/java/org/apache/ranger/unixusersync/process/PolicyMgrUserGroupBuilder.java cb9b51c95 ugsync/src/main/java/org/apache/ranger/usersync/util/UserSyncUtil.java 22a75318a Diff: https://reviews.apache.org/r/70312/diff/1/ Testing --- Testing done in Local VM. Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2381) Failed to refresh policies when servicename contains space
[ https://issues.apache.org/jira/browse/RANGER-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2381: Attachment: 0001-RANGER-2381-Failed-to-refresh-policies-when-servicen.patch > Failed to refresh policies when servicename contains space > -- > > Key: RANGER-2381 > URL: https://issues.apache.org/jira/browse/RANGER-2381 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 2.0.0 > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Attachments: > 0001-RANGER-2381-Failed-to-refresh-policies-when-servicen.patch > > > 2019-03-26 19:30:32,657 ERROR [http-bio-7070-exec-8] util.PolicyRefresher:275 > : PolicyRefresher(serviceName=kylin service): failed to refresh policies. > Will continue to use last known version of policies (-1) > java.lang.IllegalArgumentException: Illegal character in path at index 65: > http//:10.43.159.143:6080/service/plugins/policies/download/kylin service > at java.net.URI.create(URI.java:852) > at com.sun.jersey.api.client.Client.resource(Client.java:433) > at > org.apache.ranger.plugin.util.RangerRESTClient.getResource(RangerRESTClient.java:156) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.createWebResource(RangerAdminRESTClient.java:285) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:134) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:251) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:191) > at > org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:137) > at > org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:235) > at > org.apache.ranger.authorization.kylin.authorizer.RangerKylinPlugin.init(RangerKylinAuthorizer.java:152) > at > org.apache.ranger.authorization.kylin.authorizer.RangerKylinAuthorizer.init(RangerKylinAuthorizer.java:66) > at > org.apache.ranger.authorization.kylin.authorizer.RangerKylinAuthorizer.init(RangerKylinAuthorizer.java:68) > at > org.apache.kylin.rest.security.ExternalAclProvider.getInstance(ExternalAclProvider.java:45) > at > org.apache.kylin.rest.security.KylinAclPermissionEvaluator.hasPermission(KylinAclPermissionEvaluator.java:45) > at > org.springframework.security.access.expression.SecurityExpressionRoot.hasPermission(SecurityExpressionRoot.java:177) > 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:483) > at > org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:113) > at > org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:129) > at > org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:85) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) > at > org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:50) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) > at > org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) > at > org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) > at > org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) > at > org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) >
[jira] [Created] (RANGER-2381) Failed to refresh policies when servicename contains space
Qiang Zhang created RANGER-2381: --- Summary: Failed to refresh policies when servicename contains space Key: RANGER-2381 URL: https://issues.apache.org/jira/browse/RANGER-2381 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 2.0.0 Reporter: Qiang Zhang Assignee: Qiang Zhang 2019-03-26 19:30:32,657 ERROR [http-bio-7070-exec-8] util.PolicyRefresher:275 : PolicyRefresher(serviceName=kylin service): failed to refresh policies. Will continue to use last known version of policies (-1) java.lang.IllegalArgumentException: Illegal character in path at index 65: http//:10.43.159.143:6080/service/plugins/policies/download/kylin service at java.net.URI.create(URI.java:852) at com.sun.jersey.api.client.Client.resource(Client.java:433) at org.apache.ranger.plugin.util.RangerRESTClient.getResource(RangerRESTClient.java:156) at org.apache.ranger.admin.client.RangerAdminRESTClient.createWebResource(RangerAdminRESTClient.java:285) at org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:134) at org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:251) at org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:191) at org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:137) at org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:235) at org.apache.ranger.authorization.kylin.authorizer.RangerKylinPlugin.init(RangerKylinAuthorizer.java:152) at org.apache.ranger.authorization.kylin.authorizer.RangerKylinAuthorizer.init(RangerKylinAuthorizer.java:66) at org.apache.ranger.authorization.kylin.authorizer.RangerKylinAuthorizer.init(RangerKylinAuthorizer.java:68) at org.apache.kylin.rest.security.ExternalAclProvider.getInstance(ExternalAclProvider.java:45) at org.apache.kylin.rest.security.KylinAclPermissionEvaluator.hasPermission(KylinAclPermissionEvaluator.java:45) at org.springframework.security.access.expression.SecurityExpressionRoot.hasPermission(SecurityExpressionRoot.java:177) 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:483) at org.springframework.expression.spel.support.ReflectiveMethodExecutor.execute(ReflectiveMethodExecutor.java:113) at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:129) at org.springframework.expression.spel.ast.MethodReference.getValueInternal(MethodReference.java:85) at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) at org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:50) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) at org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) at org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) at org.springframework.expression.spel.ast.SpelNodeImpl.getValue(SpelNodeImpl.java:170) at org.springframework.expression.spel.ast.OpOr.getBooleanValue(OpOr.java:55) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:46) at org.springframework.expression.spel.ast.OpOr.getValueInternal(OpOr.java:36) at org.springframework.expression.spel.ast.SpelNodeImpl.getTypedValue(SpelNodeImpl.java:131) at org.springframework.expression.spel.standard.SpelExpression.getValue(SpelExpression.java:297) at org.springframework.security.access.expression.ExpressionUtils.evaluateAsBoolean(ExpressionUtils.java:26) at org.springframework.security.access.expression.method.ExpressionBasedPreInvocationAdvice.before(ExpressionBasedPreInvocationAdvice.java:59
Re: Review Request 68667: RANGER-2205 Optimize view 'vx_trx_log' to improve query performance
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/68667/#review213796 --- Can you please add what all testing has been done with this patch. Thanks. - Qiang Zhang On 九月 7, 2018, 6:53 a.m., Xing Peng wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/68667/ > --- > > (Updated 九月 7, 2018, 6:53 a.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, > Selvamohan Neethiraj, sam rome, Venkat Ranganathan, Velmurugan Periasamy, > and Qiang Zhang. > > > Bugs: RANGER-2205 > https://issues.apache.org/jira/browse/RANGER-2205 > > > Repository: ranger > > > Description > --- > > When the number of records in the table 'x_trx_log' is 1000, the view > 'vx_trx_log' query takes about 14.651 seconds. > > > Diffs > - > > security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql > 3f23b0082 > > security-admin/db/mysql/patches/035-update-view-vx_trx_log-and-add-index-on-table-x_trx_log.sql > PRE-CREATION > security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql > bafdb9676 > > security-admin/db/oracle/patches/035-update-view-vx_trx_log-and-add-index-on-table-x_trx_log.sql > PRE-CREATION > security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql > 2bc58acfe > > security-admin/db/postgres/patches/035-update-view-vx_trx_log-and-add-index-on-table-x_trx_log.sql > PRE-CREATION > > security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql > 1b64eeac8 > > security-admin/db/sqlanywhere/patches/035-update-view-vx_trx_log-and-add-index-on-table-x_trx_log.sql > PRE-CREATION > security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql > 4a216fed9 > > security-admin/db/sqlserver/patches/035-update-view-vx_trx_log-and-add-index-on-table-x_trx_log.sql > PRE-CREATION > > > Diff: https://reviews.apache.org/r/68667/diff/2/ > > > Testing > --- > > > Thanks, > > Xing Peng > >
[jira] [Commented] (RANGER-1669) We need to support the original functionality of hive：show grant user username
[ https://issues.apache.org/jira/browse/RANGER-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795597#comment-16795597 ] Qiang Zhang commented on RANGER-1669: - Hi [~pengbo], Hive "show grants" when Ranger is authorizer should show permission details from Ranger. [RANGER-2367|https://issues.apache.org/jira/browse/RANGER-2367] will fix this issue > We need to support the original functionality of hive：show grant user username > -- > > Key: RANGER-1669 > URL: https://issues.apache.org/jira/browse/RANGER-1669 > Project: Ranger > Issue Type: New Feature > Components: plugins >Affects Versions: 1.0.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Critical > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1669-We-need-to-support-the-original-function.patch, > show-grant-error.png, show-grant-user-sucess.png > > > We need to support the original functionality of hive, > 1.Scene: the original hive supports sql:show grant user glc; > 2.Error：0: jdbc:hive2://10.43.182.241:1> show grant user glc; > Error: Error while processing statement: FAILED: Execution Error, return code > 1 from org.apache.hadoop.hive.ql.exec.DDLTask. showPrivileges() not > implemented in Ranger HiveAuthorizer (state=08S01,code=1) > 3.Solution：When you integrate the Ranger plug-in into hive, you can't execute > show grant user glc； > Modify RangerHiveAuthorizerBase.java to achieve the specific implementation > of showPrivileges, > 4.The modified results can continue to support the original functionality of > the hive. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69655: RANGER-2317 : make Ranger buildable on newer JDKs
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69655/#review213656 --- Ship it! Ship It! - Qiang Zhang On 三月 11, 2019, 7:10 p.m., Zsombor Gegesy wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69655/ > --- > > (Updated 三月 11, 2019, 7:10 p.m.) > > > Review request for ranger. > > > Bugs: RANGER-2317 > https://issues.apache.org/jira/browse/RANGER-2317 > > > Repository: ranger > > > Description > --- > > Upgrade librarias to become compatible with JDK11, and JAXB and other > librarias to the modules, and exclude jdk.tools. > (These modules was previously part of the JDK, now they are independent). > Add JDK10/11 to the travis build - with excluding the Hive tests, as we can't > even start the Hive tests on JDK 9 - because internal Hive code cast the > system classloader to URLClassLoader. > Removed one empty test class file, which triggered test failures with newer > mockito version. > > > Diffs > - > > .travis.yml b38b892bd > embeddedwebserver/scripts/ranger-admin-services.sh c04e1fc72 > enunciate.xml f64af1a56 > hbase-agent/pom.xml 6b3763f22 > kms/pom.xml 59dd2761f > knox-agent/pom.xml bd68221cc > plugin-solr/pom.xml 619cc9ebd > pom.xml d5c4e924a > ranger-hbase-plugin-shim/pom.xml 9ed0aebe8 > ranger-solr-plugin-shim/pom.xml 46b78218a > security-admin/pom.xml 2c587605b > > security-admin/src/test/java/org/apache/ranger/plugin/store/RangerDBStore.java > cd5bb384e > > ugsync/src/test/java/org/apache/ranger/unixusersync/process/TestUnixUserGroupBuilder.java > 2118c8430 > > > Diff: https://reviews.apache.org/r/69655/diff/4/ > > > Testing > --- > > Tested resulting binaries locally on JDK 8, to stay the same as previously. > All the dependency change was either in test code, or in Maven plugin config, > or has 'provided' scope. > > Tested on Travis that build is succesfull in 4 JVMs - > oraclejdk8/oraclejdk11/openjdk10/openjdk11: > https://travis-ci.org/gzsombor/ranger/builds/474559352 > > > Thanks, > > Zsombor Gegesy > >
[jira] [Resolved] (RANGER-2175) Write install guide for Ranger Elasticsearch plugin RANGER-2170
[ https://issues.apache.org/jira/browse/RANGER-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2175. - Resolution: Fixed Fix Version/s: 2.0.0 master > Write install guide for Ranger Elasticsearch plugin RANGER-2170 > --- > > Key: RANGER-2175 > URL: https://issues.apache.org/jira/browse/RANGER-2175 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: document, installguide > Fix For: master, 2.0.0 > > > Write install guide for Ranger Elasticsearch plugin RANGER-2170 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2314) Do some code improvement for the error message in SqoopClient.java
[ https://issues.apache.org/jira/browse/RANGER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2314: Attachment: 0001-RANGER-2314-Do-some-code-improvement-for-the-error-m.patch > Do some code improvement for the error message in SqoopClient.java > --- > > Key: RANGER-2314 > URL: https://issues.apache.org/jira/browse/RANGER-2314 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2314-Do-some-code-improvement-for-the-error-m.patch > > > Modify the error message to show the HTTP response code instead of 'got null > response'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2314) Do some code improvement for the error message in SqoopClient.java
[ https://issues.apache.org/jira/browse/RANGER-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729396#comment-16729396 ] Qiang Zhang commented on RANGER-2314: - Review Requet: https://reviews.apache.org/r/69637/ > Do some code improvement for the error message in SqoopClient.java > --- > > Key: RANGER-2314 > URL: https://issues.apache.org/jira/browse/RANGER-2314 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2314-Do-some-code-improvement-for-the-error-m.patch > > > Modify the error message to show the HTTP response code instead of 'got null > response'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2314) Do some code improvement for the error message in SqoopClient.java
Qiang Zhang created RANGER-2314: --- Summary: Do some code improvement for the error message in SqoopClient.java Key: RANGER-2314 URL: https://issues.apache.org/jira/browse/RANGER-2314 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.0.0 Modify the error message to show the HTTP response code instead of 'got null response'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69626: RANGER-2312 Internal users should have permission to modify their personal information in User Profile page.
> On 十二月 25, 2018, 2:36 a.m., Don Bosco Durai wrote: > > security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java > > Line 211 (original), 211 (patched) > > <https://reviews.apache.org/r/69626/diff/2/?file=2116199#file2116199line211> > > > > Please verify. It seems, users would be able to provide higher role to > > himself/herself. In 'updateRoles(userProfile.getId(),userProfile.getUserRoleList())', 'xUserMgr.checkAccessRoles(stringRolesList)' and 'rangerBizUtil.blockAuditorRoleUser()' will check access, so AuditorRole user and UserRole user can not update roles, will return 403 forbidden. - Qiang --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69626/#review211530 ------- On 十二月 22, 2018, 3:59 a.m., Qiang Zhang wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69626/ > --- > > (Updated 十二月 22, 2018, 3:59 a.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, > Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan > Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan > Periasamy. > > > Bugs: RANGER-2312 > https://issues.apache.org/jira/browse/RANGER-2312 > > > Repository: ranger > > > Description > --- > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java 9e457826e > security-admin/src/main/webapp/scripts/views/user/UserProfileForm.js > 5ebd29048 > security-admin/src/test/java/org/apache/ranger/biz/TestUserMgr.java > 202a113d8 > > > Diff: https://reviews.apache.org/r/69626/diff/2/ > > > Testing > --- > > > Thanks, > > Qiang Zhang > >
[jira] [Updated] (RANGER-2312) Internal users should have permission to modify their personal information in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2312: Attachment: 0001-RANGER-2312-Internal-users-should-have-permission-to.patch > Internal users should have permission to modify their personal information in > User Profile page. > > > Key: RANGER-2312 > URL: https://issues.apache.org/jira/browse/RANGER-2312 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2312-Internal-users-should-have-permission-to.patch > > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2312) Internal users should have permission to modify their personal information in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2312: Attachment: (was: 0001-RANGER-2312-Users-should-have-permission-to-modify-t.patch) > Internal users should have permission to modify their personal information in > User Profile page. > > > Key: RANGER-2312 > URL: https://issues.apache.org/jira/browse/RANGER-2312 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2312-Internal-users-should-have-permission-to.patch > > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2312) Internal users should have permission to modify their personal information in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2312: Summary: Internal users should have permission to modify their personal information in User Profile page. (was: Users should have permission to modify their personal information in User Profile page.) > Internal users should have permission to modify their personal information in > User Profile page. > > > Key: RANGER-2312 > URL: https://issues.apache.org/jira/browse/RANGER-2312 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2312-Users-should-have-permission-to-modify-t.patch > > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2312) Users should have permission to modify their personal information in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728290#comment-16728290 ] Qiang Zhang commented on RANGER-2312: - Hi [~bosco], external users are synced from AD/LDAP or unix system, they can not login into Ranger portal. This issue is for internal users which are created by ranger Admin. > Users should have permission to modify their personal information in User > Profile page. > --- > > Key: RANGER-2312 > URL: https://issues.apache.org/jira/browse/RANGER-2312 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2312-Users-should-have-permission-to-modify-t.patch > > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2312) Users should have permission to modify their personal information in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16727204#comment-16727204 ] Qiang Zhang commented on RANGER-2312: - Review Requet: https://reviews.apache.org/r/69626/ > Users should have permission to modify their personal information in User > Profile page. > --- > > Key: RANGER-2312 > URL: https://issues.apache.org/jira/browse/RANGER-2312 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2312-Users-should-have-permission-to-modify-t.patch > > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69626: RANGER-2312 Users should have permission to modify their personal information in User Profile page.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69626/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2312 https://issues.apache.org/jira/browse/RANGER-2312 Repository: ranger Description --- Auditor role users cannot modify their personal user profile. User role and KMSAuditor role users have the same problem. Diffs - security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java 9e457826e security-admin/src/main/webapp/scripts/views/user/UserProfileForm.js 5ebd29048 Diff: https://reviews.apache.org/r/69626/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2312) Users should have permission to modify their personal information in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2312: Attachment: 0001-RANGER-2312-Users-should-have-permission-to-modify-t.patch > Users should have permission to modify their personal information in User > Profile page. > --- > > Key: RANGER-2312 > URL: https://issues.apache.org/jira/browse/RANGER-2312 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2312-Users-should-have-permission-to-modify-t.patch > > > Auditor role users cannot modify their personal user profile. > User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2312) Users should have permission to modify their personal information in User Profile page.
Qiang Zhang created RANGER-2312: --- Summary: Users should have permission to modify their personal information in User Profile page. Key: RANGER-2312 URL: https://issues.apache.org/jira/browse/RANGER-2312 Project: Ranger Issue Type: Bug Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.0.0 Auditor role users cannot modify their personal user profile. User role and KMSAuditor role users have the same problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2311) After the user profile is updated, the page still displays the original information.
[ https://issues.apache.org/jira/browse/RANGER-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726489#comment-16726489 ] Qiang Zhang commented on RANGER-2311: - Review Requet: https://reviews.apache.org/r/69616/ > After the user profile is updated, the page still displays the original > information. > > > Key: RANGER-2311 > URL: https://issues.apache.org/jira/browse/RANGER-2311 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2311-After-the-user-profile-is-updated-the-pa.patch > > > After the user profile is updated, the page still displays the original > information. > 1.Go to the User Profile page > 2.Update basic info > 3.Go to the User Profile page again -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69616: RANGER-2311 After the user profile is updated, the page still displays the original information.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69616/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2311 https://issues.apache.org/jira/browse/RANGER-2311 Repository: ranger Description --- After the user profile is updated, the page still displays the original information. 1.Go to the User Profile page 2.Update basic info 3.Go to the User Profile page again Diffs - security-admin/src/main/webapp/scripts/mgrs/SessionMgr.js 35b48cb45 security-admin/src/main/webapp/scripts/views/user/UserProfile.js 408b3112d Diff: https://reviews.apache.org/r/69616/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2311) After the user profile is updated, the page still displays the original information.
[ https://issues.apache.org/jira/browse/RANGER-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2311: Attachment: 0001-RANGER-2311-After-the-user-profile-is-updated-the-pa.patch > After the user profile is updated, the page still displays the original > information. > > > Key: RANGER-2311 > URL: https://issues.apache.org/jira/browse/RANGER-2311 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2311-After-the-user-profile-is-updated-the-pa.patch > > > After the user profile is updated, the page still displays the original > information. > 1.Go to the User Profile page > 2.Update basic info > 3.Go to the User Profile page again -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2311) After the user profile is updated, the page still displays the original information.
Qiang Zhang created RANGER-2311: --- Summary: After the user profile is updated, the page still displays the original information. Key: RANGER-2311 URL: https://issues.apache.org/jira/browse/RANGER-2311 Project: Ranger Issue Type: Bug Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.0.0 After the user profile is updated, the page still displays the original information. 1.Go to the User Profile page 2.Update basic info 3.Go to the User Profile page again -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2170) Ranger supports plugin to enable, monitor and manage Elasticsearch
[ https://issues.apache.org/jira/browse/RANGER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2170: Attachment: 0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch > Ranger supports plugin to enable, monitor and manage Elasticsearch > -- > > Key: RANGER-2170 > URL: https://issues.apache.org/jira/browse/RANGER-2170 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: new-feature, patch > Attachments: > 0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch, > 1_ElasticSearchServiceEntry.jpg, 2_EditElasticSearchService.jpg, > 3_ElasticSearchPolicies.jpg, 4_EditElasticSearchPolicy.jpg, > 5_ElasticSearchAuditLog.jpg, 6_ElasticSearchPlugins.jpg, > 7_ElasticSearchPluginStatus.jpg > > > Elasticsearch is a distributed, RESTful search and analytics engine capable > of solving a growing number of use cases. > Like Apache Solr, it is also an index server based on Lucence. > Ranger supports plugin to enable, monitor and manage Elasticsearch, > to control index security of Elasticsearch. > As there is X-Pack plugin for the Elasticsearch, but it is not free. > X-Pack is an Elastic Stack extension that bundles security, alerting, > monitoring, reporting, > and graph capabilities into one easy-to-install package. > We refer to the Indices Privileges design of X-Pack, > by keeping the permissions consistent, > to make user use ranger Elasticsearch plugin easily. > Reference X-Pack Indices Privileges: > https://www.elastic.co/guide/en/x-pack/current/security-privileges.html > Here we develop Ranger Elasticsearch plugin, based on Elasticsearch version > 6.2.2. > Elasticsearch 6.2.2 was released in February 20, 2018, reference > release-notes: > https://www.elastic.co/guide/en/elasticsearch/reference/6.2/release-notes-6.2.2.html > Not like other system, Elasticsearch has no basic authentication, > it uses X-pack plugin to support basic authentication, > role-based access control, SSL/TLS encryption, LDAP and so on. > Not like X-pack, our Ranger Elasticsearch plugin is designed to do > authorization, > it is to control index of Elasticsearch without authentication, > this plugin should work with other Elasticsearch plugin to authenticate users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2170) Ranger supports plugin to enable, monitor and manage Elasticsearch
[ https://issues.apache.org/jira/browse/RANGER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563379#comment-16563379 ] Qiang Zhang edited comment on RANGER-2170 at 12/13/18 6:54 AM: --- Review Requet: https://reviews.apache.org/r/68128/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12951614/0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch] Implementation details: [1_ElasticSearchServiceEntry|https://issues.apache.org/jira/secure/attachment/12933730/1_ElasticSearchServiceEntry.jpg] [2_EditElasticSearchService|https://issues.apache.org/jira/secure/attachment/12933731/2_EditElasticSearchService.jpg] [3_ElasticSearchPolicies|https://issues.apache.org/jira/secure/attachment/12933732/3_ElasticSearchPolicies.jpg] [4_EditElasticSearchPolicy|https://issues.apache.org/jira/secure/attachment/12933733/4_EditElasticSearchPolicy.jpg] [5_ElasticSearchAuditLog|https://issues.apache.org/jira/secure/attachment/12933734/5_ElasticSearchAuditLog.jpg] [6_ElasticSearchPlugins|https://issues.apache.org/jira/secure/attachment/12933735/6_ElasticSearchPlugins.jpg] [7_ElasticSearchPluginStatus.jpg|https://issues.apache.org/jira/secure/attachment/12933736/7_ElasticSearchPluginStatus.jpg] was (Author: zhangqiang2): Review Requet: https://reviews.apache.org/r/68128/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12935505/0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch] Implementation details: [1_ElasticSearchServiceEntry|https://issues.apache.org/jira/secure/attachment/12933730/1_ElasticSearchServiceEntry.jpg] [2_EditElasticSearchService|https://issues.apache.org/jira/secure/attachment/12933731/2_EditElasticSearchService.jpg] [3_ElasticSearchPolicies|https://issues.apache.org/jira/secure/attachment/12933732/3_ElasticSearchPolicies.jpg] [4_EditElasticSearchPolicy|https://issues.apache.org/jira/secure/attachment/12933733/4_EditElasticSearchPolicy.jpg] [5_ElasticSearchAuditLog|https://issues.apache.org/jira/secure/attachment/12933734/5_ElasticSearchAuditLog.jpg] [6_ElasticSearchPlugins|https://issues.apache.org/jira/secure/attachment/12933735/6_ElasticSearchPlugins.jpg] [7_ElasticSearchPluginStatus.jpg|https://issues.apache.org/jira/secure/attachment/12933736/7_ElasticSearchPluginStatus.jpg] > Ranger supports plugin to enable, monitor and manage Elasticsearch > -- > > Key: RANGER-2170 > URL: https://issues.apache.org/jira/browse/RANGER-2170 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: new-feature, patch > Attachments: > 0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch, > 1_ElasticSearchServiceEntry.jpg, 2_EditElasticSearchService.jpg, > 3_ElasticSearchPolicies.jpg, 4_EditElasticSearchPolicy.jpg, > 5_ElasticSearchAuditLog.jpg, 6_ElasticSearchPlugins.jpg, > 7_ElasticSearchPluginStatus.jpg > > > Elasticsearch is a distributed, RESTful search and analytics engine capable > of solving a growing number of use cases. > Like Apache Solr, it is also an index server based on Lucence. > Ranger supports plugin to enable, monitor and manage Elasticsearch, > to control index security of Elasticsearch. > As there is X-Pack plugin for the Elasticsearch, but it is not free. > X-Pack is an Elastic Stack extension that bundles security, alerting, > monitoring, reporting, > and graph capabilities into one easy-to-install package. > We refer to the Indices Privileges design of X-Pack, > by keeping the permissions consistent, > to make user use ranger Elasticsearch plugin easily. > Reference X-Pack Indices Privileges: > https://www.elastic.co/guide/en/x-pack/current/security-privileges.html > Here we develop Ranger Elasticsearch plugin, based on Elasticsearch version > 6.2.2. > Elasticsearch 6.2.2 was released in February 20, 2018, reference > release-notes: > https://www.elastic.co/guide/en/elasticsearch/reference/6.2/release-notes-6.2.2.html > Not like other system, Elasticsearch has no basic authentication, > it uses X-pack plugin to support basic authentication, > role-based access control, SSL/TLS encryption, LDAP and so on. > Not like X-pack, our Ranger Elasticsearch plugin is designed to do > authorization, > it is to control index of Elasticsearch without authentication, > this plugin should work with other Elasticsearch plugin to authenticate users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2170) Ranger supports plugin to enable, monitor and manage Elasticsearch
[ https://issues.apache.org/jira/browse/RANGER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2170: Attachment: (was: 0001-RANGER-2170-Ranger-supports-plugin-to-enable-monitor.patch) > Ranger supports plugin to enable, monitor and manage Elasticsearch > -- > > Key: RANGER-2170 > URL: https://issues.apache.org/jira/browse/RANGER-2170 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: new-feature, patch > Attachments: 1_ElasticSearchServiceEntry.jpg, > 2_EditElasticSearchService.jpg, 3_ElasticSearchPolicies.jpg, > 4_EditElasticSearchPolicy.jpg, 5_ElasticSearchAuditLog.jpg, > 6_ElasticSearchPlugins.jpg, 7_ElasticSearchPluginStatus.jpg > > > Elasticsearch is a distributed, RESTful search and analytics engine capable > of solving a growing number of use cases. > Like Apache Solr, it is also an index server based on Lucence. > Ranger supports plugin to enable, monitor and manage Elasticsearch, > to control index security of Elasticsearch. > As there is X-Pack plugin for the Elasticsearch, but it is not free. > X-Pack is an Elastic Stack extension that bundles security, alerting, > monitoring, reporting, > and graph capabilities into one easy-to-install package. > We refer to the Indices Privileges design of X-Pack, > by keeping the permissions consistent, > to make user use ranger Elasticsearch plugin easily. > Reference X-Pack Indices Privileges: > https://www.elastic.co/guide/en/x-pack/current/security-privileges.html > Here we develop Ranger Elasticsearch plugin, based on Elasticsearch version > 6.2.2. > Elasticsearch 6.2.2 was released in February 20, 2018, reference > release-notes: > https://www.elastic.co/guide/en/elasticsearch/reference/6.2/release-notes-6.2.2.html > Not like other system, Elasticsearch has no basic authentication, > it uses X-pack plugin to support basic authentication, > role-based access control, SSL/TLS encryption, LDAP and so on. > Not like X-pack, our Ranger Elasticsearch plugin is designed to do > authorization, > it is to control index of Elasticsearch without authentication, > this plugin should work with other Elasticsearch plugin to authenticate users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 68128: RANGER-2170:Ranger supports plugin to enable, monitor and manage Elasticsearch
/authorization/elasticsearch/plugin/rest/filter/RangerSecurityRestFilter.java
PRE-CREATION
ranger-elasticsearch-plugin-shim/src/main/java/org/apache/ranger/authorization/elasticsearch/plugin/utils/RequestUtils.java
PRE-CREATION
src/main/assembly/admin-web.xml b3ec885
src/main/assembly/plugin-elasticsearch.xml PRE-CREATION
Diff: https://reviews.apache.org/r/68128/diff/3/
Changes: https://reviews.apache.org/r/68128/diff/2-3/
Testing
---
#Test Steps:
1.Intall
Ranger Elasticsearch Plugin Installation Guide
https://cwiki.apache.org/confluence/display/RANGER/Elasticsearch+Plugin
Include install Elasticsearch and Ranger Elasticsearch Plugin,
and verify install result.
2.Create policy in Ranger Admin
User "elasticsearch" has all permissions on all indices.
User "yuwen" has permission "read" on index "twitter".
3.Test permission
3.1 successful:
curl -u elasticsearch:xxx -X GET "localhost:9200/twitter/_stats?pretty"
curl -u elasticsearch:xxx -X GET "localhost:9200/twitter2/_stats?pretty"
curl -u yuwen:xxx -X GET "localhost:9200/twitter/_stats?pretty"
3.2 failed:
curl -X GET "localhost:9200/twitter/_stats?pretty"
{
"error" : {
"root_cause" : [
{
"type" : "status_exception",
"reason" : "Error: User is null, the request requires user
authentication."
}
],
"type" : "status_exception",
"reason" : "Error: User is null, the request requires user authentication."
},
"status" : 401
}
curl -u yuwen:xxx -X GET "localhost:9200/twitter2/_stats?pretty"
{
"error" : {
"root_cause" : [
{
"type" : "status_exception",
"reason" : "Error: User[yuwen] could not do
action[indices:monitor/stats] on index[twitter2]"
}
],
"type" : "status_exception",
"reason" : "Error: User[yuwen] could not do action[indices:monitor/stats]
on index[twitter2]"
},
"status" : 403
}
Thanks,
Qiang Zhang
Re: Review Request 69509: RANGER-2304 : Need to add property dfs.permissions.ContentSummary.subAccess when enabling Ranger HDFS plugin manually.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69509/#review211268 --- Ship it! Ship It! - Qiang Zhang On 十二月 5, 2018, 11:29 a.m., Vishal Suvagia wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69509/ > --- > > (Updated 十二月 5, 2018, 11:29 a.m.) > > > Review request for ranger, Ankita Sinha, bhavik patel, Colm O hEigeartaigh, > Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, pengjianhua, > Pradeep Agrawal, Ramesh Mani, Sailaja Polavarapu, Velmurugan Periasamy, and > Qiang Zhang. > > > Bugs: RANGER-2304 > https://issues.apache.org/jira/browse/RANGER-2304 > > > Repository: ranger > > > Description > --- > > As part of fixes in HDFS-14112 and RANGER-2297, need to update the script > that handles setting up HDFS authorizer when Ranger HDFS plugin is > enabled/disabled, as below: >* Set the property dfs.permissions.ContentSummary.subAccess in > hdfs-site.xml to ‘true’ when Ranger plugin is > enabled. >* Remove the property dfs.permissions.ContentSummary.subAccess in > hdfs-site.xml or set to ‘false’ when Ranger plugin > is disabled. > > > Diffs > - > > hdfs-agent/conf/hdfs-site-changes.cfg 8088b43f8 > hdfs-agent/disable-conf/hdfs-site-changes.cfg 652bf2ee8 > > > Diff: https://reviews.apache.org/r/69509/diff/1/ > > > Testing > --- > > Tested with a fresh install on Cent-OS, the property > dfs.permissions.ContentSummary.subAccess is set to true when Ranger HDFS > plugin is enabled manually. > > > Thanks, > > Vishal Suvagia > >
[jira] [Assigned] (RANGER-2163) Spelling error for "Persmission" in the PatchPersmissionModel_J10003.java.
[ https://issues.apache.org/jira/browse/RANGER-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang reassigned RANGER-2163: --- Assignee: Qiang Zhang > Spelling error for "Persmission" in the PatchPersmissionModel_J10003.java. > -- > > Key: RANGER-2163 > URL: https://issues.apache.org/jira/browse/RANGER-2163 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: xiehaihong >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2163-Spelling-error-in-the-PatchPersmissionMo.patch > > > Spelling error for "Persmission" in the > ranger/security-admin/src/main/java/org/apache/ranger/patch/PatchPersmissionModel_J10003.java. > "PatchPermissionModel" instead of "PatchPersmissionModel". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2303) Add kylin-plugin infomation to README.txt
Qiang Zhang created RANGER-2303: --- Summary: Add kylin-plugin infomation to README.txt Key: RANGER-2303 URL: https://issues.apache.org/jira/browse/RANGER-2303 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang As kylin plugin has been submitted and merged into to Ranger, we should add kylin-plugin infomation to README.txt. Related Issue: RANGER-1672 Ranger supports plugin to enable, monitor and manage apache kylin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2303) Add kylin-plugin infomation to README.txt
[ https://issues.apache.org/jira/browse/RANGER-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2303: Attachment: 0001-RANGER-2303-Add-kylin-plugin-infomation-to-README.tx.patch > Add kylin-plugin infomation to README.txt > - > > Key: RANGER-2303 > URL: https://issues.apache.org/jira/browse/RANGER-2303 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: doc, plugin > Attachments: > 0001-RANGER-2303-Add-kylin-plugin-infomation-to-README.tx.patch > > Original Estimate: 0.2h > Remaining Estimate: 0.2h > > As kylin plugin has been submitted and merged into to Ranger, > we should add kylin-plugin infomation to README.txt. > Related Issue: > RANGER-1672 Ranger supports plugin to enable, monitor and manage apache kylin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69506: RANGER-2303:Add kylin-plugin infomation to README.txt
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69506/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, sam rome, Venkat Ranganathan, Velmurugan Periasamy, and Zsombor Gegesy. Bugs: RANGER-2303 https://issues.apache.org/jira/browse/RANGER-2303 Repository: ranger Description --- As kylin plugin has been submitted and merged into to Ranger, we should add kylin-plugin infomation to README.txt. Related Issue: RANGER-1672 Ranger supports plugin to enable, monitor and manage apache kylin Diffs - README.txt e54ce33 Diff: https://reviews.apache.org/r/69506/diff/1/ Testing --- Test OK. Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2299) Modify the permissions of the kms install.properties file to 700
[ https://issues.apache.org/jira/browse/RANGER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2299: Attachment: 0001-RANGER-2299-Modify-the-permissions-of-the-kms-instal.patch > Modify the permissions of the kms install.properties file to 700 > > > Key: RANGER-2299 > URL: https://issues.apache.org/jira/browse/RANGER-2299 > Project: Ranger > Issue Type: Bug > Components: kms >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2299-Modify-the-permissions-of-the-kms-instal.patch > > > Now the owner of the kms install.properties file has only read and execute > permissions, no write permissions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2299) Modify the permissions of the kms install.properties file to 700
[ https://issues.apache.org/jira/browse/RANGER-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704445#comment-16704445 ] Qiang Zhang commented on RANGER-2299: - Review Requet: https://reviews.apache.org/r/69489/ > Modify the permissions of the kms install.properties file to 700 > > > Key: RANGER-2299 > URL: https://issues.apache.org/jira/browse/RANGER-2299 > Project: Ranger > Issue Type: Bug > Components: kms >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2299-Modify-the-permissions-of-the-kms-instal.patch > > > Now the owner of the kms install.properties file has only read and execute > permissions, no write permissions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69489: RANGER-2299 Modify the permissions of the kms install.properties file to 700
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69489/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2299 https://issues.apache.org/jira/browse/RANGER-2299 Repository: ranger Description --- Now the owner of the kms install.properties file has only read and execute permissions, no write permissions. Diffs - src/main/assembly/kms.xml ed818b1a7 Diff: https://reviews.apache.org/r/69489/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Created] (RANGER-2299) Modify the permissions of the kms install.properties file to 700
Qiang Zhang created RANGER-2299: --- Summary: Modify the permissions of the kms install.properties file to 700 Key: RANGER-2299 URL: https://issues.apache.org/jira/browse/RANGER-2299 Project: Ranger Issue Type: Bug Components: kms Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.0.0 Now the owner of the kms install.properties file has only read and execute permissions, no write permissions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69488: RANGER-2298 Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69488/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2298 https://issues.apache.org/jira/browse/RANGER-2298 Repository: ranger Description --- Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties Diffs - kms/scripts/install.properties 947d9f389 security-admin/scripts/install.properties 674844cec Diff: https://reviews.apache.org/r/69488/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Commented] (RANGER-2298) Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties
[ https://issues.apache.org/jira/browse/RANGER-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704358#comment-16704358 ] Qiang Zhang commented on RANGER-2298: - Review Requet: https://reviews.apache.org/r/69488/ > Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties > - > > Key: RANGER-2298 > URL: https://issues.apache.org/jira/browse/RANGER-2298 > Project: Ranger > Issue Type: Bug > Components: admin, kms >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2298-Modify-JAVA_VERSION_REQUIRED-to-1.8-in-i.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2298) Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties
[ https://issues.apache.org/jira/browse/RANGER-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2298: Attachment: 0001-RANGER-2298-Modify-JAVA_VERSION_REQUIRED-to-1.8-in-i.patch > Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties > - > > Key: RANGER-2298 > URL: https://issues.apache.org/jira/browse/RANGER-2298 > Project: Ranger > Issue Type: Bug > Components: admin, kms >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2298-Modify-JAVA_VERSION_REQUIRED-to-1.8-in-i.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2298) Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties
Qiang Zhang created RANGER-2298: --- Summary: Modify JAVA_VERSION_REQUIRED to 1.8 in install.properties Key: RANGER-2298 URL: https://issues.apache.org/jira/browse/RANGER-2298 Project: Ranger Issue Type: Bug Components: admin, kms Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2294) Front-end and back-end email address regular expression should be the same
[ https://issues.apache.org/jira/browse/RANGER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2294: Attachment: 0001-RANGER-2294-Front-end-and-back-end-email-address-reg.patch > Front-end and back-end email address regular expression should be the same > -- > > Key: RANGER-2294 > URL: https://issues.apache.org/jira/browse/RANGER-2294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: email, validation, web > Attachments: > 0001-RANGER-2294-Front-end-and-back-end-email-address-reg.patch, > FixedJsValidateEmail.jpg, JavaValidateEmail.jpg, JsValidateEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > When edit user email address, and input the incorrect email address, > there are two kinds of error message: > 1.Input .@ab.ab, there is error message: > Invalid email address > [JsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949801/JsValidateEmail.jpg] > 2.Input a...@ab.ab, there is error message: > Please provide valid email address. > [JavaValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949800/JavaValidateEmail.jpg] > It is not reasonable when email address passed front-end validation, > but failed back-end validation. > So front-end and back-end email address regular expression should be the same, > and add hint message for user to fill email address. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2294) Front-end and back-end email address regular expression should be the same
[ https://issues.apache.org/jira/browse/RANGER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16701512#comment-16701512 ] Qiang Zhang commented on RANGER-2294: - Review Requet: https://reviews.apache.org/r/69466/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12949806/0001-RANGER-2294-Front-end-and-back-end-email-address-reg.patch] Test: [FixedJsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949805/FixedJsValidateEmail.jpg] > Front-end and back-end email address regular expression should be the same > -- > > Key: RANGER-2294 > URL: https://issues.apache.org/jira/browse/RANGER-2294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: email, validation, web > Attachments: > 0001-RANGER-2294-Front-end-and-back-end-email-address-reg.patch, > FixedJsValidateEmail.jpg, JavaValidateEmail.jpg, JsValidateEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > When edit user email address, and input the incorrect email address, > there are two kinds of error message: > 1.Input .@ab.ab, there is error message: > Invalid email address > [JsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949801/JsValidateEmail.jpg] > 2.Input a...@ab.ab, there is error message: > Please provide valid email address. > [JavaValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949800/JavaValidateEmail.jpg] > It is not reasonable when email address passed front-end validation, > but failed back-end validation. > So front-end and back-end email address regular expression should be the same, > and add hint message for user to fill email address. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69466: RANGER-2294:Front-end and back-end email address regular expression should be the same
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69466/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, sam rome, Venkat Ranganathan, Velmurugan Periasamy, and Zsombor Gegesy. Bugs: RANGER-2294 https://issues.apache.org/jira/browse/RANGER-2294 Repository: ranger Description --- When edit user email address, and input the incorrect email address, there are two kinds of error message: 1.Input .@ab.ab, there is error message: Invalid email address [JsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949801/JsValidateEmail.jpg] 2.Input a...@ab.ab, there is error message: Please provide valid email address. [JavaValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949800/JavaValidateEmail.jpg] It is not reasonable when email address passed front-end validation, but failed back-end validation. So front-end and back-end email address regular expression should be the same, and add hint message for user to fill email address. Diffs - security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 2c0ee98 security-admin/src/main/webapp/scripts/views/users/UserForm.js ee0d256 Diff: https://reviews.apache.org/r/69466/diff/1/ Testing --- #Test Result: Test OK. [FixedJsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949805/FixedJsValidateEmail.jpg] Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2294) Front-end and back-end email address regular expression should be the same
[ https://issues.apache.org/jira/browse/RANGER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2294: Attachment: FixedJsValidateEmail.jpg > Front-end and back-end email address regular expression should be the same > -- > > Key: RANGER-2294 > URL: https://issues.apache.org/jira/browse/RANGER-2294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: email, validation, web > Attachments: FixedJsValidateEmail.jpg, JavaValidateEmail.jpg, > JsValidateEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > When edit user email address, and input the incorrect email address, > there are two kinds of error message: > 1.Input .@ab.ab, there is error message: > Invalid email address > [JsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949801/JsValidateEmail.jpg] > 2.Input a...@ab.ab, there is error message: > Please provide valid email address. > [JavaValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949800/JavaValidateEmail.jpg] > It is not reasonable when email address passed front-end validation, > but failed back-end validation. > So front-end and back-end email address regular expression should be the same, > and add hint message for user to fill email address. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2294) Front-end and back-end email address regular expression should be the same
Qiang Zhang created RANGER-2294: --- Summary: Front-end and back-end email address regular expression should be the same Key: RANGER-2294 URL: https://issues.apache.org/jira/browse/RANGER-2294 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang When edit user email address, and input the incorrect email address, there are two kinds of error message: 1.Input .@ab.ab, there is error message: Invalid email address screenshot 2.Input a...@ab.ab, there is error message: Please provide valid email address. screenshot It is not reasonable when email address passed front-end validation, but failed back-end validation. So front-end and back-end email address regular expression should be the same, and add hint message for user to fill email address. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2294) Front-end and back-end email address regular expression should be the same
[ https://issues.apache.org/jira/browse/RANGER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2294: Description: When edit user email address, and input the incorrect email address, there are two kinds of error message: 1.Input .@ab.ab, there is error message: Invalid email address [JsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949801/JsValidateEmail.jpg] 2.Input a...@ab.ab, there is error message: Please provide valid email address. [JavaValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949800/JavaValidateEmail.jpg] It is not reasonable when email address passed front-end validation, but failed back-end validation. So front-end and back-end email address regular expression should be the same, and add hint message for user to fill email address. was: When edit user email address, and input the incorrect email address, there are two kinds of error message: 1.Input .@ab.ab, there is error message: Invalid email address screenshot 2.Input a...@ab.ab, there is error message: Please provide valid email address. screenshot It is not reasonable when email address passed front-end validation, but failed back-end validation. So front-end and back-end email address regular expression should be the same, and add hint message for user to fill email address. > Front-end and back-end email address regular expression should be the same > -- > > Key: RANGER-2294 > URL: https://issues.apache.org/jira/browse/RANGER-2294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: email, validation, web > Attachments: JavaValidateEmail.jpg, JsValidateEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > When edit user email address, and input the incorrect email address, > there are two kinds of error message: > 1.Input .@ab.ab, there is error message: > Invalid email address > [JsValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949801/JsValidateEmail.jpg] > 2.Input a...@ab.ab, there is error message: > Please provide valid email address. > [JavaValidateEmail.jpg|https://issues.apache.org/jira/secure/attachment/12949800/JavaValidateEmail.jpg] > It is not reasonable when email address passed front-end validation, > but failed back-end validation. > So front-end and back-end email address regular expression should be the same, > and add hint message for user to fill email address. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2294) Front-end and back-end email address regular expression should be the same
[ https://issues.apache.org/jira/browse/RANGER-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2294: Attachment: JsValidateEmail.jpg JavaValidateEmail.jpg > Front-end and back-end email address regular expression should be the same > -- > > Key: RANGER-2294 > URL: https://issues.apache.org/jira/browse/RANGER-2294 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: email, validation, web > Attachments: JavaValidateEmail.jpg, JsValidateEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > When edit user email address, and input the incorrect email address, > there are two kinds of error message: > 1.Input .@ab.ab, there is error message: > Invalid email address > screenshot > 2.Input a...@ab.ab, there is error message: > Please provide valid email address. > screenshot > It is not reasonable when email address passed front-end validation, > but failed back-end validation. > So front-end and back-end email address regular expression should be the same, > and add hint message for user to fill email address. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Attachment: error.PNG > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch, error.PNG, > error.PNG, error_page.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: > !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Attachment: (was: error.PNG) > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch, error.PNG, > error_page.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: > !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Description: Unable to get Audit Admin tab page. Steps: 1. Go to Audit Admin tab page. 2. Click on 'Session ID' to show session detail modal. 3. Click on 'Show Actions' button. Error log: !error.PNG! was: Unable to get Audit Admin tab page. Steps: 1. Go to Audit Admin tab page. 2. Click on 'Session ID' to show session detail modal. 3. Click on 'Show Actions' button. Error log: !error.PNG! > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch, error.PNG, > error_page.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Attachment: error_page.PNG > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch, error.PNG, > error_page.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: > !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69406: RANGER-2289 Unable to get Audit Admin tab page
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69406/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2289 https://issues.apache.org/jira/browse/RANGER-2289 Repository: ranger Description --- Unable to get Audit Admin tab page. Steps: 1. Go to Audit Admin tab page. 2. Click on 'Session ID' to show session detail modal. 3. Click on 'Show Actions' button. Diffs - security-admin/src/main/webapp/scripts/utils/XAUtils.js bb88ec306 security-admin/src/main/webapp/scripts/views/reports/AuditLayout.js 718a95d70 Diff: https://reviews.apache.org/r/69406/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Attachment: 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch, error.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: > !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2289) Unable to get Audit Admin tab page.
Qiang Zhang created RANGER-2289: --- Summary: Unable to get Audit Admin tab page. Key: RANGER-2289 URL: https://issues.apache.org/jira/browse/RANGER-2289 Project: Ranger Issue Type: Bug Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Unable to get Audit Admin tab page. Steps: 1. Go to Audit Admin tab page. 2. Click on 'Session ID' to show session detail modal. 3. Click on 'Show Actions' button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692969#comment-16692969 ] Qiang Zhang commented on RANGER-2289: - Review Requet: https://reviews.apache.org/r/69406/ > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2289-Unable-to-get-Audit-Admin-tab-page.patch, error.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: > !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Description: Unable to get Audit Admin tab page. Steps: 1. Go to Audit Admin tab page. 2. Click on 'Session ID' to show session detail modal. 3. Click on 'Show Actions' button. Error log: !error.PNG! was: Unable to get Audit Admin tab page. Steps: 1. Go to Audit Admin tab page. 2. Click on 'Session ID' to show session detail modal. 3. Click on 'Show Actions' button. > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: error.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. > Error log: > !error.PNG! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2289) Unable to get Audit Admin tab page.
[ https://issues.apache.org/jira/browse/RANGER-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2289: Attachment: error.PNG > Unable to get Audit Admin tab page. > --- > > Key: RANGER-2289 > URL: https://issues.apache.org/jira/browse/RANGER-2289 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: error.PNG > > > Unable to get Audit Admin tab page. > Steps: > 1. Go to Audit Admin tab page. > 2. Click on 'Session ID' to show session detail modal. > 3. Click on 'Show Actions' button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2288) Sqoop repository config missing "Common Name for Certificate"
[ https://issues.apache.org/jira/browse/RANGER-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689106#comment-16689106 ] Qiang Zhang commented on RANGER-2288: - Review Requet: https://reviews.apache.org/r/69371/ > Sqoop repository config missing "Common Name for Certificate" > - > > Key: RANGER-2288 > URL: https://issues.apache.org/jira/browse/RANGER-2288 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2288-Sqoop-repository-config-missing-Common-N.patch > > > Currently there is no field for specifying "Common Name for Certificate" in > Sqoop repository configuration. To get SSL setup between ranger admin and > Sqoop plugin working, this field should be added to the repo config. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2288) Sqoop repository config missing "Common Name for Certificate"
[ https://issues.apache.org/jira/browse/RANGER-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2288: Attachment: 0001-RANGER-2288-Sqoop-repository-config-missing-Common-N.patch > Sqoop repository config missing "Common Name for Certificate" > - > > Key: RANGER-2288 > URL: https://issues.apache.org/jira/browse/RANGER-2288 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2288-Sqoop-repository-config-missing-Common-N.patch > > > Currently there is no field for specifying "Common Name for Certificate" in > Sqoop repository configuration. To get SSL setup between ranger admin and > Sqoop plugin working, this field should be added to the repo config. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69371: RANGER-2288 Sqoop repository config missing "Common Name for Certificate"
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69371/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2288 https://issues.apache.org/jira/browse/RANGER-2288 Repository: ranger Description --- Currently there is no field for specifying "Common Name for Certificate" in Sqoop repository configuration. To get SSL setup between ranger admin and Sqoop plugin working, this field should be added to the repo config. Diffs - agents-common/src/main/resources/service-defs/ranger-servicedef-sqoop.json 902a0b88b Diff: https://reviews.apache.org/r/69371/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Created] (RANGER-2288) Sqoop repository config missing "Common Name for Certificate"
Qiang Zhang created RANGER-2288: --- Summary: Sqoop repository config missing "Common Name for Certificate" Key: RANGER-2288 URL: https://issues.apache.org/jira/browse/RANGER-2288 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Currently there is no field for specifying "Common Name for Certificate" in Sqoop repository configuration. To get SSL setup between ranger admin and Sqoop plugin working, this field should be added to the repo config. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2244) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.91 or later.
[ https://issues.apache.org/jira/browse/RANGER-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16687671#comment-16687671 ] Qiang Zhang commented on RANGER-2244: - Review Requet: https://reviews.apache.org/r/69340/ > Tomcat Security Vulnerability Alert. The version of the tomcat for ranger > should upgrade to 7.0.91 or later. > > > Key: RANGER-2244 > URL: https://issues.apache.org/jira/browse/RANGER-2244 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2244-Tomcat-Security-Vulnerability-Alert.-The.patch > > > h2. [SECURITY] CVE-2018-11784 Apache Tomcat - Open Redirect > CVE-2018-11784 Apache Tomcat - Open Redirect > Severity: Moderate > Vendor: The Apache Software Foundation > Versions Affected: > Apache Tomcat 9.0.0.M1 to 9.0.11 > Apache Tomcat 8.5.0 to 8.5.33 > Apache Tomcat 7.0.23 to 7.0.90 > The unsupported 8.0.x release line has not been analysed but is likely > to be affected. > Description: > When the default servlet returned a redirect to a directory (e.g. > redirecting to '/foo/' when the user requested '/foo') a specially > crafted URL could be used to cause the redirect to be generated to any > URI of the attackers choice. > Mitigation: > Users of the affected versions should apply one of the following > mitigations: > * Upgrade to Apache Tomcat 9.0.12 or later. > * Upgrade to Apache Tomcat 8.5.34 or later. > * Upgrade to Apache Tomcat 7.0.91 or later. > * Use mapperDirectoryRedirectEnabled="true" and > mapperContextRootRedirectEnabled="true" on the Context to ensure that > redirects are issued by the Mapper rather than the default Servlet. > See the Context configuration documentation for further important > details. > Credit: > This vulnerability was found by Sergey Bobrov and reported responsibly > to the Apache Tomcat Security Team. > History: > 2018-10-03 Original advisory > References: > [1] http://tomcat.apache.org/security-9.html > [2] http://tomcat.apache.org/security-8.html > [3] http://tomcat.apache.org/security-7.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2244) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.91 or later.
[ https://issues.apache.org/jira/browse/RANGER-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2244: Attachment: 0001-RANGER-2244-Tomcat-Security-Vulnerability-Alert.-The.patch > Tomcat Security Vulnerability Alert. The version of the tomcat for ranger > should upgrade to 7.0.91 or later. > > > Key: RANGER-2244 > URL: https://issues.apache.org/jira/browse/RANGER-2244 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2244-Tomcat-Security-Vulnerability-Alert.-The.patch > > > h2. [SECURITY] CVE-2018-11784 Apache Tomcat - Open Redirect > CVE-2018-11784 Apache Tomcat - Open Redirect > Severity: Moderate > Vendor: The Apache Software Foundation > Versions Affected: > Apache Tomcat 9.0.0.M1 to 9.0.11 > Apache Tomcat 8.5.0 to 8.5.33 > Apache Tomcat 7.0.23 to 7.0.90 > The unsupported 8.0.x release line has not been analysed but is likely > to be affected. > Description: > When the default servlet returned a redirect to a directory (e.g. > redirecting to '/foo/' when the user requested '/foo') a specially > crafted URL could be used to cause the redirect to be generated to any > URI of the attackers choice. > Mitigation: > Users of the affected versions should apply one of the following > mitigations: > * Upgrade to Apache Tomcat 9.0.12 or later. > * Upgrade to Apache Tomcat 8.5.34 or later. > * Upgrade to Apache Tomcat 7.0.91 or later. > * Use mapperDirectoryRedirectEnabled="true" and > mapperContextRootRedirectEnabled="true" on the Context to ensure that > redirects are issued by the Mapper rather than the default Servlet. > See the Context configuration documentation for further important > details. > Credit: > This vulnerability was found by Sergey Bobrov and reported responsibly > to the Apache Tomcat Security Team. > History: > 2018-10-03 Original advisory > References: > [1] http://tomcat.apache.org/security-9.html > [2] http://tomcat.apache.org/security-8.html > [3] http://tomcat.apache.org/security-7.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69340: RANGER-2244 Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.91 or later.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69340/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2244 https://issues.apache.org/jira/browse/RANGER-2244 Repository: ranger Description --- [SECURITY] CVE-2018-11784 Apache Tomcat - Open Redirect CVE-2018-11784 Apache Tomcat - Open Redirect Severity: Moderate Vendor: The Apache Software Foundation Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.11 Apache Tomcat 8.5.0 to 8.5.33 Apache Tomcat 7.0.23 to 7.0.90 The unsupported 8.0.x release line has not been analysed but is likely to be affected. Description: When the default servlet returned a redirect to a directory (e.g. redirecting to '/foo/' when the user requested '/foo') a specially crafted URL could be used to cause the redirect to be generated to any URI of the attackers choice. Mitigation: Users of the affected versions should apply one of the following mitigations: Upgrade to Apache Tomcat 9.0.12 or later. Upgrade to Apache Tomcat 8.5.34 or later. Upgrade to Apache Tomcat 7.0.91 or later. Use mapperDirectoryRedirectEnabled="true" and mapperContextRootRedirectEnabled="true" on the Context to ensure that redirects are issued by the Mapper rather than the default Servlet. See the Context configuration documentation for further important details. Credit: This vulnerability was found by Sergey Bobrov and reported responsibly to the Apache Tomcat Security Team. History: 2018-10-03 Original advisory References: [1] http://tomcat.apache.org/security-9.html [2] http://tomcat.apache.org/security-8.html [3] http://tomcat.apache.org/security-7.html Diffs - embeddedwebserver/src/main/java/org/apache/ranger/server/tomcat/EmbeddedServer.java eac0dacaf pom.xml 514f87e7f Diff: https://reviews.apache.org/r/69340/diff/1/ Testing --- 1.Modify the ssl configuration item in install.properties for the Ranger Admin. **SSL config** db_ssl_enabled=true db_ssl_required=true db_ssl_verifyServerCertificate=true javax_net_ssl_keyStore=/opt/ranger-ssl/keystore javax_net_ssl_keyStorePassword=hdp1234$ javax_net_ssl_trustStore=/opt/ranger-ssl/truststore javax_net_ssl_trustStorePassword=hdp1234$ ... **--- PolicyManager CONFIG ** policymgr_external_url=https://localhost:6182 policymgr_http_enabled=false policymgr_https_keystore_file=/opt/ranger-ssl/rangertomcatverify.jks policymgr_https_keystore_keyalias=rangertomcatverify policymgr_https_keystore_password=hdp1234$ 2.Install the Ranger Admin 3.Modify the ssl configuration item in install.properties for the usersync. **POLICY_MGR_URL = http://policymanager.xasecure.net:6080** POLICY_MGR_URL = https://sslrangerserver:6182 **SSL Authentication** AUTH_SSL_ENABLED=false AUTH_SSL_KEYSTORE_FILE=/opt/ranger-ssl/keystore AUTH_SSL_KEYSTORE_PASSWORD=hdp1234$ AUTH_SSL_TRUSTSTORE_FILE=/opt/ranger-ssl/truststore AUTH_SSL_TRUSTSTORE_PASSWORD=hdp1234$ 4.Install the Ranger usersync 5.Modified the ssl configuration item in install.properties for the kms. **POLICY_MGR_URL = http://policymanager.xasecure.net:6080** POLICY_MGR_URL = https://sslrangerserver:6182 db_ssl_enabled=true db_ssl_required=true db_ssl_verifyServerCertificate=true db_ssl_auth_type=2-way javax_net_ssl_keyStore=/opt/ranger-ssl/keystore javax_net_ssl_keyStorePassword=hdp1234$ javax_net_ssl_trustStore=/opt/ranger-ssl/truststore javax_net_ssl_trustStorePassword=hdp1234$ **SSL Client Certificate Information** SSL_KEYSTORE_FILE_PATH=/opt/ranger-ssl/rangertomcatverify-keystore.jks SSL_KEYSTORE_PASSWORD=myKeyFilePassword SSL_TRUSTSTORE_FILE_PATH=/opt/ranger-ssl/rangertomcatverify-truststore.jks SSL_TRUSTSTORE_PASSWORD=myTrustFilePassword 6.Install the KMS 7.Modified the ssl configuration item in install.properties for plugins **POLICY_MGR_URL = http://policymanager.xasecure.net:6080** POLICY_MGR_URL = https://sslrangerserver:6182 **SSL Client Certificate Information** SSL_KEYSTORE_FILE_PATH=/opt/ranger-ssl/rangertomcatverify-keystore.jks SSL_KEYSTORE_PASSWORD=myKeyFilePassword SSL_TRUSTSTORE_FILE_PATH=/opt/ranger-ssl/rangertomcatverify-truststore.jks SSL_TRUSTSTORE_PASSWORD=myTrustFilePassword 8.Install plugins Thanks, Qiang Zhang
[jira] [Created] (RANGER-2282) The error message for changing password is incorrect in User Profile page.
Qiang Zhang created RANGER-2282: --- Summary: The error message for changing password is incorrect in User Profile page. Key: RANGER-2282 URL: https://issues.apache.org/jira/browse/RANGER-2282 Project: Ranger Issue Type: Bug Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang The error message for changing password is incorrect in User Profile page. Following error message needs to be fixed： 1.Enter the wrong old password Error message：You can not use old password. 2.The new password entered is the same as the old password Error message：Invalid Password. Minimum 8 characters with min one alphabet and one numeric. After fixing： 1.Enter the wrong old password Error message：Your password does not match. Please try again with proper password. 2.The new password entered is the same as the old password Error message：You can not use old password. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2282) The error message for changing password is incorrect in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2282: Attachment: 0001-RANGER-2282-The-error-message-for-changing-password-.patch > The error message for changing password is incorrect in User Profile page. > -- > > Key: RANGER-2282 > URL: https://issues.apache.org/jira/browse/RANGER-2282 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2282-The-error-message-for-changing-password-.patch > > > The error message for changing password is incorrect in User Profile page. > Following error message needs to be fixed： > 1.Enter the wrong old password > Error message：You can not use old password. > 2.The new password entered is the same as the old password > Error message：Invalid Password. Minimum 8 characters with min one alphabet > and one numeric. > After fixing： > 1.Enter the wrong old password > Error message：Your password does not match. Please try again with proper > password. > 2.The new password entered is the same as the old password > Error message：You can not use old password. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2282) The error message for changing password is incorrect in User Profile page.
[ https://issues.apache.org/jira/browse/RANGER-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684648#comment-16684648 ] Qiang Zhang commented on RANGER-2282: - Review Requet: https://reviews.apache.org/r/69320/ > The error message for changing password is incorrect in User Profile page. > -- > > Key: RANGER-2282 > URL: https://issues.apache.org/jira/browse/RANGER-2282 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2282-The-error-message-for-changing-password-.patch > > > The error message for changing password is incorrect in User Profile page. > Following error message needs to be fixed： > 1.Enter the wrong old password > Error message：You can not use old password. > 2.The new password entered is the same as the old password > Error message：Invalid Password. Minimum 8 characters with min one alphabet > and one numeric. > After fixing： > 1.Enter the wrong old password > Error message：Your password does not match. Please try again with proper > password. > 2.The new password entered is the same as the old password > Error message：You can not use old password. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69320: RANGER-2282 The error message for changing password is incorrect in User Profile page.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69320/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, Nitin Galave, pengjianhua, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, Sailaja Polavarapu, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-2282 https://issues.apache.org/jira/browse/RANGER-2282 Repository: ranger Description --- The error message for changing password is incorrect in User Profile page. Following error message needs to be fixed. 1.Enter the wrong old password Error message: You can not use old password. 2.The new password entered is the same as the old password Error message: Invalid Password. Minimum 8 characters with min one alphabet and one numeric. After fixing: 1.Enter the wrong old password Error message: Your password does not match. Please try again with proper password. 2.The new password entered is the same as the old password Error message: You can not use old password. Diffs - security-admin/src/main/java/org/apache/ranger/biz/UserMgr.java 2a638f890 security-admin/src/main/webapp/scripts/views/user/UserProfile.js 8e60b53b9 Diff: https://reviews.apache.org/r/69320/diff/1/ Testing --- Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2276) Email Address should be verified when Add New User in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2276: Attachment: 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch > Email Address should be verified when Add New User in Ranger Admin > -- > > Key: RANGER-2276 > URL: https://issues.apache.org/jira/browse/RANGER-2276 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: rangeradmin, validation > Attachments: > 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch, > UpdateUserWithEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > Click Add New User in Ranger Admin to create user, > and fill in Email Address with a@b.c, user can be created successfully. > But when you update the user with Email Address like x@y.z, > update would be failed with the following message: > Error:Please provide valid email address. > Please refer screenshots: > [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] > Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2276) Email Address should be verified when Add New User in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683402#comment-16683402 ] Qiang Zhang edited comment on RANGER-2276 at 11/12/18 8:37 AM: --- [~pradeep.agrawal] OK, thanks. I have tested with ranger usersync to sync user, and make sure there are no problems with the new patch. was (Author: zhangqiang2): [~pradeep.agrawal]] OK, thanks. I have tested with ranger usersync to sync user, and make sure there are no problems with the new patch. > Email Address should be verified when Add New User in Ranger Admin > -- > > Key: RANGER-2276 > URL: https://issues.apache.org/jira/browse/RANGER-2276 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: rangeradmin, validation > Attachments: > 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch, > UpdateUserWithEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > Click Add New User in Ranger Admin to create user, > and fill in Email Address with a@b.c, user can be created successfully. > But when you update the user with Email Address like x@y.z, > update would be failed with the following message: > Error:Please provide valid email address. > Please refer screenshots: > [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] > Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2276) Email Address should be verified when Add New User in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16672684#comment-16672684 ] Qiang Zhang edited comment on RANGER-2276 at 11/12/18 8:35 AM: --- Review Requet: https://reviews.apache.org/r/69239/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12947791/0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch] was (Author: zhangqiang2): Review Requet: https://reviews.apache.org/r/69239/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12946647/0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch] > Email Address should be verified when Add New User in Ranger Admin > -- > > Key: RANGER-2276 > URL: https://issues.apache.org/jira/browse/RANGER-2276 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: rangeradmin, validation > Attachments: > 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch, > UpdateUserWithEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > Click Add New User in Ranger Admin to create user, > and fill in Email Address with a@b.c, user can be created successfully. > But when you update the user with Email Address like x@y.z, > update would be failed with the following message: > Error:Please provide valid email address. > Please refer screenshots: > [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] > Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69239: RANGER-2276:Email Address should be verified when Add New User in Ranger Admin
> On 十一月 9, 2018, 9:29 a.m., pengjianhua wrote: > > security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java > > Lines 31 (patched) > > <https://reviews.apache.org/r/69239/diff/1/?file=2103713#file2103713line31> > > > > This path has conflicts, StringUtils is already defined in the latest > > code. > > > > security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java:[89] > > error: org.apache.commons.lang.StringUtils is already defined in a > > single-type import OK, thanks. - Qiang --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69239/#review210436 ------- On 十一月 12, 2018, 8:34 a.m., Qiang Zhang wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/69239/ > --- > > (Updated 十一月 12, 2018, 8:34 a.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, > Selvamohan Neethiraj, sam rome, Venkat Ranganathan, Velmurugan Periasamy, > and Zsombor Gegesy. > > > Bugs: RANGER-2276 > https://issues.apache.org/jira/browse/RANGER-2276 > > > Repository: ranger > > > Description > --- > > Click Add New User in Ranger Admin to create user, > and fill in Email Address with a@b.c, user can be created successfully. > But when you update the user with Email Address like x@y.z, > update would be failed with the following message: > Error:Please provide valid email address. > Please refer screenshots: > [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] > Email Address should be verified when creating users like updating users. > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java ced600f > > > Diff: https://reviews.apache.org/r/69239/diff/2/ > > > Testing > --- > > Tested: > Email Address is verified when Add New User in Ranger Admin. > > > Thanks, > > Qiang Zhang > >
[jira] [Updated] (RANGER-2276) Email Address should be verified when Add New User in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2276: Attachment: (was: 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch) > Email Address should be verified when Add New User in Ranger Admin > -- > > Key: RANGER-2276 > URL: https://issues.apache.org/jira/browse/RANGER-2276 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: rangeradmin, validation > Attachments: > 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch, > UpdateUserWithEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > Click Add New User in Ranger Admin to create user, > and fill in Email Address with a@b.c, user can be created successfully. > But when you update the user with Email Address like x@y.z, > update would be failed with the following message: > Error:Please provide valid email address. > Please refer screenshots: > [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] > Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Review Request 69239: RANGER-2276:Email Address should be verified when Add New User in Ranger Admin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69239/ --- (Updated 十一月 12, 2018, 8:34 a.m.) Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, sam rome, Venkat Ranganathan, Velmurugan Periasamy, and Zsombor Gegesy. Changes --- Update patch to resolve file conflicts. Bugs: RANGER-2276 https://issues.apache.org/jira/browse/RANGER-2276 Repository: ranger Description --- Click Add New User in Ranger Admin to create user, and fill in Email Address with a@b.c, user can be created successfully. But when you update the user with Email Address like x@y.z, update would be failed with the following message: Error:Please provide valid email address. Please refer screenshots: [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] Email Address should be verified when creating users like updating users. Diffs (updated) - security-admin/src/main/java/org/apache/ranger/biz/XUserMgr.java ced600f Diff: https://reviews.apache.org/r/69239/diff/2/ Changes: https://reviews.apache.org/r/69239/diff/1-2/ Testing --- Tested: Email Address is verified when Add New User in Ranger Admin. Thanks, Qiang Zhang
[jira] [Commented] (RANGER-2276) Email Address should be verified when Add New User in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683402#comment-16683402 ] Qiang Zhang commented on RANGER-2276: - [~pradeep.agrawal]] OK, thanks. I have tested with ranger usersync to sync user, and make sure there are no problems with the new patch. > Email Address should be verified when Add New User in Ranger Admin > -- > > Key: RANGER-2276 > URL: https://issues.apache.org/jira/browse/RANGER-2276 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: rangeradmin, validation > Attachments: > 0001-RANGER-2276-Email-Address-should-be-verified-when-Ad.patch, > UpdateUserWithEmail.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > Click Add New User in Ranger Admin to create user, > and fill in Email Address with a@b.c, user can be created successfully. > But when you update the user with Email Address like x@y.z, > update would be failed with the following message: > Error:Please provide valid email address. > Please refer screenshots: > [UpdateUserWithEmail.jpg|https://issues.apache.org/jira/secure/attachment/12946646/UpdateUserWithEmail.jpg] > Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Review Request 69297: RANGER-2280:The emptyText of User Sync and Plugin Status should be reasonable
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/69297/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, sam rome, Venkat Ranganathan, Velmurugan Periasamy, and Zsombor Gegesy. Bugs: RANGER-2280 https://issues.apache.org/jira/browse/RANGER-2280 Repository: ranger Description --- In the User Sync webpage under the Audit of Ranger Admin? if the form is empty, it will show emptyText: No plugin found! Refer screenshots: [AuditUserSyncNotFound|https://issues.apache.org/jira/secure/attachment/12947353/AuditUserSyncNotFound.jpg] The message shown above is not reasonable. It should be changed to: No user sync audit found! Fixed screenshots: [AuditUserSyncNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947354/AuditUserSyncNotFound_Fix.jpg] Similar to User Sync, the emptyText of Plugin Status is not reasonable. It should be changed to: No plugin status found! Fixed screenshots: [AuditPluginStatusNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947352/AuditPluginStatusNotFound_Fix.jpg] Diffs - security-admin/src/main/webapp/scripts/views/reports/AuditLayout.js fe9566c Diff: https://reviews.apache.org/r/69297/diff/1/ Testing --- Tested Thanks, Qiang Zhang
[jira] [Updated] (RANGER-2280) The emptyText of User Sync and Plugin Status should be reasonable
[ https://issues.apache.org/jira/browse/RANGER-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2280: Attachment: 0001-RANGER-2280-The-emptyText-of-User-Sync-and-Plugin-St.patch > The emptyText of User Sync and Plugin Status should be reasonable > - > > Key: RANGER-2280 > URL: https://issues.apache.org/jira/browse/RANGER-2280 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, message > Attachments: > 0001-RANGER-2280-The-emptyText-of-User-Sync-and-Plugin-St.patch, > AuditPluginStatusNotFound_Fix.jpg, AuditUserSyncNotFound.jpg, > AuditUserSyncNotFound_Fix.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > In the User Sync webpage under the Audit of Ranger Admin， > if the form is empty, it will show emptyText: > No plugin found! > Refer screenshots: > [AuditUserSyncNotFound|https://issues.apache.org/jira/secure/attachment/12947353/AuditUserSyncNotFound.jpg] > The message shown above is not reasonable. It should be changed to: > No user sync audit found! > Fixed screenshots: > [AuditUserSyncNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947354/AuditUserSyncNotFound_Fix.jpg] > Similar to User Sync, the emptyText of Plugin Status is not reasonable. > It should be changed to: > No plugin status found! > Fixed screenshots: > [AuditPluginStatusNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947352/AuditPluginStatusNotFound_Fix.jpg] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2280) The emptyText of User Sync and Plugin Status should be reasonable
[ https://issues.apache.org/jira/browse/RANGER-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2280: Description: In the User Sync webpage under the Audit of Ranger Admin， if the form is empty, it will show emptyText: No plugin found! Refer screenshots: [AuditUserSyncNotFound|https://issues.apache.org/jira/secure/attachment/12947353/AuditUserSyncNotFound.jpg] The message shown above is not reasonable. It should be changed to: No user sync audit found! Fixed screenshots: [AuditUserSyncNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947354/AuditUserSyncNotFound_Fix.jpg] Similar to User Sync, the emptyText of Plugin Status is not reasonable. It should be changed to: No plugin status found! Fixed screenshots: [AuditPluginStatusNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947352/AuditPluginStatusNotFound_Fix.jpg] was: In the User Sync webpage under the Audit of Ranger Admin， if the form is empty, it will show emptyText: No plugin found! Refer screenshots: The message shown above is not reasonable. It should be changed to: No user sync audit found! Fixed screenshots: Similar to User Sync, the emptyText of Plugin Status is not reasonable. It should be changed to: No plugin status found! Fixed screenshots: > The emptyText of User Sync and Plugin Status should be reasonable > - > > Key: RANGER-2280 > URL: https://issues.apache.org/jira/browse/RANGER-2280 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, message > Attachments: AuditPluginStatusNotFound_Fix.jpg, > AuditUserSyncNotFound.jpg, AuditUserSyncNotFound_Fix.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > In the User Sync webpage under the Audit of Ranger Admin， > if the form is empty, it will show emptyText: > No plugin found! > Refer screenshots: > [AuditUserSyncNotFound|https://issues.apache.org/jira/secure/attachment/12947353/AuditUserSyncNotFound.jpg] > The message shown above is not reasonable. It should be changed to: > No user sync audit found! > Fixed screenshots: > [AuditUserSyncNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947354/AuditUserSyncNotFound_Fix.jpg] > Similar to User Sync, the emptyText of Plugin Status is not reasonable. > It should be changed to: > No plugin status found! > Fixed screenshots: > [AuditPluginStatusNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947352/AuditPluginStatusNotFound_Fix.jpg] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2280) The emptyText of User Sync and Plugin Status should be reasonable
[ https://issues.apache.org/jira/browse/RANGER-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16679366#comment-16679366 ] Qiang Zhang commented on RANGER-2280: - Review Requet: https://reviews.apache.org/r/69297/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12947360/0001-RANGER-2280-The-emptyText-of-User-Sync-and-Plugin-St.patch] > The emptyText of User Sync and Plugin Status should be reasonable > - > > Key: RANGER-2280 > URL: https://issues.apache.org/jira/browse/RANGER-2280 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, message > Attachments: > 0001-RANGER-2280-The-emptyText-of-User-Sync-and-Plugin-St.patch, > AuditPluginStatusNotFound_Fix.jpg, AuditUserSyncNotFound.jpg, > AuditUserSyncNotFound_Fix.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > In the User Sync webpage under the Audit of Ranger Admin， > if the form is empty, it will show emptyText: > No plugin found! > Refer screenshots: > [AuditUserSyncNotFound|https://issues.apache.org/jira/secure/attachment/12947353/AuditUserSyncNotFound.jpg] > The message shown above is not reasonable. It should be changed to: > No user sync audit found! > Fixed screenshots: > [AuditUserSyncNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947354/AuditUserSyncNotFound_Fix.jpg] > Similar to User Sync, the emptyText of Plugin Status is not reasonable. > It should be changed to: > No plugin status found! > Fixed screenshots: > [AuditPluginStatusNotFound_Fix|https://issues.apache.org/jira/secure/attachment/12947352/AuditPluginStatusNotFound_Fix.jpg] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2280) The emptyText of User Sync and Plugin Status should be reasonable
[ https://issues.apache.org/jira/browse/RANGER-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2280: Attachment: AuditUserSyncNotFound_Fix.jpg AuditUserSyncNotFound.jpg AuditPluginStatusNotFound_Fix.jpg > The emptyText of User Sync and Plugin Status should be reasonable > - > > Key: RANGER-2280 > URL: https://issues.apache.org/jira/browse/RANGER-2280 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master > Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, message > Attachments: AuditPluginStatusNotFound_Fix.jpg, > AuditUserSyncNotFound.jpg, AuditUserSyncNotFound_Fix.jpg > > Original Estimate: 24h > Remaining Estimate: 24h > > In the User Sync webpage under the Audit of Ranger Admin， > if the form is empty, it will show emptyText: > No plugin found! > Refer screenshots: > The message shown above is not reasonable. It should be changed to: > No user sync audit found! > Fixed screenshots: > Similar to User Sync, the emptyText of Plugin Status is not reasonable. > It should be changed to: > No plugin status found! > Fixed screenshots: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2280) The emptyText of User Sync and Plugin Status should be reasonable
Qiang Zhang created RANGER-2280: --- Summary: The emptyText of User Sync and Plugin Status should be reasonable Key: RANGER-2280 URL: https://issues.apache.org/jira/browse/RANGER-2280 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang In the User Sync webpage under the Audit of Ranger Admin， if the form is empty, it will show emptyText: No plugin found! Refer screenshots: The message shown above is not reasonable. It should be changed to: No user sync audit found! Fixed screenshots: Similar to User Sync, the emptyText of Plugin Status is not reasonable. It should be changed to: No plugin status found! Fixed screenshots: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2277) Kylin repository config missing "Common Name for Certificate"
[ https://issues.apache.org/jira/browse/RANGER-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16674867#comment-16674867 ] Qiang Zhang commented on RANGER-2277: - Review Requet: https://reviews.apache.org/r/69156/ > Kylin repository config missing "Common Name for Certificate" > - > > Key: RANGER-2277 > URL: https://issues.apache.org/jira/browse/RANGER-2277 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2277-Kylin-repository-config-missing-Common-N.patch > > > Currently there is no field for specifying "Common Name for Certificate" in > Kylin repository configuration. To get SSL setup between ranger admin and > Kylin plugin working, this field should be added to the repo config. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
