[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)
[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)
[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&focusedCommentId=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)
[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&focusedCommentId=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 > 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.springframewo
[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) > 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) >
[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) at org.springframework.security.access.prepost.
[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&focusedCommentId=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)
[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&focusedCommentId=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)
[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&focusedCommentId=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&focusedCommentId=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)
[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&focusedCommentId=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)
[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&focusedCommentId=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)
[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)
[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&focusedCommentId=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)
[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)
[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&focusedCommentId=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&focusedCommentId=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)
[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)
[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&focusedCommentId=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&focusedCommentId=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)
[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&focusedCommentId=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)
[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&focusedCommentId=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)
[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&focusedCommentId=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&focusedCommentId=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)
[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)
[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&focusedCommentId=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)
[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&focusedCommentId=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&focusedCommentId=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)
[jira] [Updated] (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:all-tabpanel ] Qiang Zhang updated RANGER-2277: Attachment: 0001-RANGER-2277-Kylin-repository-config-missing-Common-N.patch > 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)
[jira] [Created] (RANGER-2277) Kylin repository config missing "Common Name for Certificate"
Qiang Zhang created RANGER-2277: --- Summary: 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 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)
[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] [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: Summary: Email Address should be verified when Add New User in Ranger Admin (was: Email Address should be verified when Add New User in Ranger Admin.) > 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: 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] [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: 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. was: 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: []() Email Address should be verified when creating users like updating users. > 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: 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] [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: UpdateUserWithEmail.jpg > 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: 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: > []() > Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2276) Email Address should be verified when Add New User in Ranger Admin.
Qiang Zhang created RANGER-2276: --- Summary: 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 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: []() Email Address should be verified when creating users like updating users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Description: On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a icon to differentiate the status of the service Modified screenshots: [^Modify.PNG] was: On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a "disabled" lable to differentiate the status of the service Modified screenshots: https://issues.apache.org/jira/secure/attachment/12946338/Modify.PNG > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2267-Add-a-icon-to-differentiate-the-status-o.patch, Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a icon to differentiate the status of the service > Modified screenshots: > [^Modify.PNG] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Description: On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a "disabled" lable to differentiate the status of the service Modified screenshots: https://issues.apache.org/jira/secure/attachment/12946338/Modify.PNG was: On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a "disabled" lable to differentiate the status of the service Modified screenshots: https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2267-Add-a-icon-to-differentiate-the-status-o.patch, Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12946338/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Attachment: 0001-RANGER-2267-Add-a-icon-to-differentiate-the-status-o.patch > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2267-Add-a-icon-to-differentiate-the-status-o.patch, Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Attachment: Modify.PNG > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2267-Add-a-icon-to-differentiate-the-status-o.patch, Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Summary: Add a icon to differentiate the status of the service (was: Add a "disabled" lable to differentiate the status of the service) > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Attachment: (was: Modify.PNG) > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a icon to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Attachment: (was: 0001-RANGER-2267-Add-a-disabled-lable-to-differentiate-th.patch) > Add a icon to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2265) To make the profile "all" to be active by default when ranger build
[
https://issues.apache.org/jira/browse/RANGER-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664557#comment-16664557
]
Qiang Zhang commented on RANGER-2265:
-
[~vperiasamy] My maven version:
{noformat}
[root@zdh-11 ~]# mvn -version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-11T00:41:47+08:00)
Maven home: /home/maven/apache-maven-3.3.9
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/java/jdk1.8.0_151/jre
Default locale: zh_CN, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family:
"unix"
{noformat}
> To make the profile "all" to be active by default when ranger build
>
>
> Key: RANGER-2265
> URL: https://issues.apache.org/jira/browse/RANGER-2265
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
> Labels: build
> Attachments:
> 0001-RANGER-2265-Added-all-the-modules-for-linux-profile-.patch,
> 0001-RANGER-2265-To-make-the-profile-all-to-be-active-by-.patch
>
>
> After merge https://issues.apache.org/jira/browse/RANGER-2243 patch, we need
> to pass -Pall to the build.
> Refer command:
> mvn -DskipTests=true clean compile package install assembly:assembly -Pall
> If use the following command would cause failue:
> mvn -DskipTests=true clean compile package install assembly:assembly
> {noformat}
> OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family:
> "unix"
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ranger . SKIPPED
> [INFO] Unix Native Authenticator .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [ERROR] Could not find goal 'assembly' in plugin
> org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals
> help, single -> [Help 1]
> {noformat}
> Use the following command to find default profile,
> we can see the profile "linux" is active:
> {noformat}
> mvn help:active-profiles -N
> Active Profiles for Project 'org.apache.ranger:ranger:pom:2.0.0-SNAPSHOT':
> The following profiles are active:
> - env-settings (source: external)
> - env-unix (source: external)
> - linux (source: org.apache.ranger:ranger:2.0.0-SNAPSHOT)
> {noformat}
> Which we expect the default profile "all" to be active.
> Refer to the Maven issue:
> Profile not active even though it has activeByDefault set to true
> https://issues.apache.org/jira/browse/MNG-4917
> {noformat}
> And from Introduction to Build Profiles:
> This profile will automatically be active for all builds unless another
> profile in the same pom is activated using one of the previously described
> methods. All profiles that are active by default are automatically
> deactivated when a profile in the pom is activated on the command line or
> through its activation config.
> {noformat}
> *In short, the profile "linux" disables "all" when ranger build without
> specifying the profile id.*
> To make the profile "all" to be active by default,
> we should remove the property "activation" of profile "linux".
> In fact, the property "activation" of profile "linux" make no sense,
> just prompt us to compile under linux os,
> and it should not be activated automatically instead of "all".
> It should be activated by specifying the profile id:
> mvn -DskipTests=true clean compile package install assembly:assembly -Plinux
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2265) To make the profile "all" to be active by default when ranger build
[
https://issues.apache.org/jira/browse/RANGER-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664553#comment-16664553
]
Qiang Zhang edited comment on RANGER-2265 at 10/26/18 2:21 AM:
---
[~rmani] Please use the following command to see which profile is active:
mvn help:active-profiles -N
I think there is another profile disables "all" in your enviroment.
And it is better to remove activation configuration of profiles except "all"
in Ranger pom.
In Ranger build scenario, we expect to build all modules by default,
and in other cases we need to specify the profile ID to build specific modules.
In fact, more than two profiles with activation configuration would not work
as we expect.
So we can build individual plugins as issue RANGER-2243 describe,
and the default value "all" is used without specifying the -P parameter.
Reference:
[https://stackoverflow.com/questions/16167206/does-using-activebydefault-go-against-maven-best-practices#|https://stackoverflow.com/questions/16167206/does-using-activebydefault-go-against-maven-best-practices]
[https://stackoverflow.com/questions/5309379/how-to-keep-maven-profiles-which-are-activebydefault-active-even-if-another-prof]
https://issues.apache.org/jira/browse/MNG-4917
was (Author: zhangqiang2):
[~Ramesh Mani] Please use the following command to see which profile is active:
mvn help:active-profiles -N
I think there is another profile disables "all" in your enviroment.
And it is better to remove activation configuration of profiles except "all" in
Ranger pom.
In Ranger build scenario, we expect to build all modules by default,
and in other cases we need to specify the profile ID to build specific modules.
In fact, more than two profiles with activation configuration would not work as
we expect.
So we can build individual plugins as issue RANGER-2243 describe,
and the default value "all" is used without specifying the -P parameter.
Reference:
https://stackoverflow.com/questions/16167206/does-using-activebydefault-go-against-maven-best-practices#
https://stackoverflow.com/questions/5309379/how-to-keep-maven-profiles-which-are-activebydefault-active-even-if-another-prof
https://issues.apache.org/jira/browse/MNG-4917
> To make the profile "all" to be active by default when ranger build
>
>
> Key: RANGER-2265
> URL: https://issues.apache.org/jira/browse/RANGER-2265
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
> Labels: build
> Attachments:
> 0001-RANGER-2265-Added-all-the-modules-for-linux-profile-.patch,
> 0001-RANGER-2265-To-make-the-profile-all-to-be-active-by-.patch
>
>
> After merge https://issues.apache.org/jira/browse/RANGER-2243 patch, we need
> to pass -Pall to the build.
> Refer command:
> mvn -DskipTests=true clean compile package install assembly:assembly -Pall
> If use the following command would cause failue:
> mvn -DskipTests=true clean compile package install assembly:assembly
> {noformat}
> OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family:
> "unix"
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ranger . SKIPPED
> [INFO] Unix Native Authenticator .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [ERROR] Could not find goal 'assembly' in plugin
> org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals
> help, single -> [Help 1]
> {noformat}
> Use the following command to find default profile,
> we can see the profile "linux" is active:
> {noformat}
> mvn help:active-profiles -N
> Active Profiles for Project 'org.apache.ranger:ranger:pom:2.0.0-SNAPSHOT':
> The following profiles are active:
> - env-settings (source: external)
> - env-unix (source: external)
> - linux (source: org.apache.ranger:ranger:2.0.0-SNAPSHOT)
> {noformat}
> Which we expect the default profile "all" to be active.
> Refer to the Maven issue:
> Profile not active even though it has activeByDefault set to true
> https://issues.apache.org/jira/browse/MNG-4917
> {noformat}
> And from Introduction to Build Profiles:
> This profile will automatically be active for all builds unless another
> profile in the same pom is activated using one of the previously described
> methods. All profiles that are active by default are automatically
> deactivated when a profile in the pom is activated on the command line or
> through its activation config.
> {noformat}
> *In short, the profile "linux" disables "all" when ranger build without
> specifying the profile
[jira] [Commented] (RANGER-2265) To make the profile "all" to be active by default when ranger build
[
https://issues.apache.org/jira/browse/RANGER-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664553#comment-16664553
]
Qiang Zhang commented on RANGER-2265:
-
[~Ramesh Mani] Please use the following command to see which profile is active:
mvn help:active-profiles -N
I think there is another profile disables "all" in your enviroment.
And it is better to remove activation configuration of profiles except "all" in
Ranger pom.
In Ranger build scenario, we expect to build all modules by default,
and in other cases we need to specify the profile ID to build specific modules.
In fact, more than two profiles with activation configuration would not work as
we expect.
So we can build individual plugins as issue RANGER-2243 describe,
and the default value "all" is used without specifying the -P parameter.
Reference:
https://stackoverflow.com/questions/16167206/does-using-activebydefault-go-against-maven-best-practices#
https://stackoverflow.com/questions/5309379/how-to-keep-maven-profiles-which-are-activebydefault-active-even-if-another-prof
https://issues.apache.org/jira/browse/MNG-4917
> To make the profile "all" to be active by default when ranger build
>
>
> Key: RANGER-2265
> URL: https://issues.apache.org/jira/browse/RANGER-2265
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Major
> Labels: build
> Attachments:
> 0001-RANGER-2265-Added-all-the-modules-for-linux-profile-.patch,
> 0001-RANGER-2265-To-make-the-profile-all-to-be-active-by-.patch
>
>
> After merge https://issues.apache.org/jira/browse/RANGER-2243 patch, we need
> to pass -Pall to the build.
> Refer command:
> mvn -DskipTests=true clean compile package install assembly:assembly -Pall
> If use the following command would cause failue:
> mvn -DskipTests=true clean compile package install assembly:assembly
> {noformat}
> OS name: "linux", version: "2.6.32-431.el6.x86_64", arch: "amd64", family:
> "unix"
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ranger . SKIPPED
> [INFO] Unix Native Authenticator .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [ERROR] Could not find goal 'assembly' in plugin
> org.apache.maven.plugins:maven-assembly-plugin:3.0.0 among available goals
> help, single -> [Help 1]
> {noformat}
> Use the following command to find default profile,
> we can see the profile "linux" is active:
> {noformat}
> mvn help:active-profiles -N
> Active Profiles for Project 'org.apache.ranger:ranger:pom:2.0.0-SNAPSHOT':
> The following profiles are active:
> - env-settings (source: external)
> - env-unix (source: external)
> - linux (source: org.apache.ranger:ranger:2.0.0-SNAPSHOT)
> {noformat}
> Which we expect the default profile "all" to be active.
> Refer to the Maven issue:
> Profile not active even though it has activeByDefault set to true
> https://issues.apache.org/jira/browse/MNG-4917
> {noformat}
> And from Introduction to Build Profiles:
> This profile will automatically be active for all builds unless another
> profile in the same pom is activated using one of the previously described
> methods. All profiles that are active by default are automatically
> deactivated when a profile in the pom is activated on the command line or
> through its activation config.
> {noformat}
> *In short, the profile "linux" disables "all" when ranger build without
> specifying the profile id.*
> To make the profile "all" to be active by default,
> we should remove the property "activation" of profile "linux".
> In fact, the property "activation" of profile "linux" make no sense,
> just prompt us to compile under linux os,
> and it should not be activated automatically instead of "all".
> It should be activated by specifying the profile id:
> mvn -DskipTests=true clean compile package install assembly:assembly -Plinux
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-2267) Add a "disabled" lable to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663481#comment-16663481 ] Qiang Zhang commented on RANGER-2267: - Review Requet: https://reviews.apache.org/r/69156/ > Add a "disabled" lable to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2267-Add-a-disabled-lable-to-differentiate-th.patch, Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a "disabled" lable to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Attachment: 0001-RANGER-2267-Add-a-disabled-lable-to-differentiate-th.patch > Add a "disabled" lable to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2267-Add-a-disabled-lable-to-differentiate-th.patch, Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a "disabled" lable to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Attachment: Modify.PNG > Add a "disabled" lable to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2267) Add a "disabled" lable to differentiate the status of the service
[ https://issues.apache.org/jira/browse/RANGER-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2267: Description: On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a "disabled" lable to differentiate the status of the service Modified screenshots: https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG was: On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a "disabled" lable to differentiate the status of the service > Add a "disabled" lable to differentiate the status of the service > - > > Key: RANGER-2267 > URL: https://issues.apache.org/jira/browse/RANGER-2267 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: 2.0.0 > > Attachments: Modify.PNG > > > On the Service Manager page, the enabled service and the disabled service are > displayed the same, and the user cannot distinguish between them. > Add a "disabled" lable to differentiate the status of the service > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12945573/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2267) Add a "disabled" lable to differentiate the status of the service
Qiang Zhang created RANGER-2267: --- Summary: Add a "disabled" lable to differentiate the status of the service Key: RANGER-2267 URL: https://issues.apache.org/jira/browse/RANGER-2267 Project: Ranger Issue Type: Improvement Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: 2.0.0 On the Service Manager page, the enabled service and the disabled service are displayed the same, and the user cannot distinguish between them. Add a "disabled" lable to differentiate the status of the service -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2266) To make Id to ID in Audit Pages of Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2266: Attachment: 0001-RANGER-2266-To-make-Id-to-ID-in-Audit-Pages-of-Range.patch > To make Id to ID in Audit Pages of Ranger Admin > > > Key: RANGER-2266 > URL: https://issues.apache.org/jira/browse/RANGER-2266 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, web > Attachments: > 0001-RANGER-2266-To-make-Id-to-ID-in-Audit-Pages-of-Range.patch, > Access_PolicyID.jpg, Admin_SessionID.jpg, > LoginSeeions_LoginIDandSessionID.jpg, Plugins_PluginID.jpg > > > The ID in the Audit web pages of Ranger Admin is not uniform. > There are two ways to write in the pages: Id and ID. > In Access, Table Head: Policy ID > In Admin, Table Head and Search Options: Session Id > In Login Sessions, Table Head and Search Options: Session Id, Login Id > In Plugins, Table Head: Plugin Id, but Search Options: Plugin ID > Please check the following screenshots: > [Access|https://issues.apache.org/jira/secure/attachment/12945554/Access_PolicyID.jpg] > [Admin|https://issues.apache.org/jira/secure/attachment/1294/Admin_SessionID.jpg] > [Login > Sessions|https://issues.apache.org/jira/secure/attachment/12945556/LoginSeeions_LoginIDandSessionID.jpg] > [Plugins|https://issues.apache.org/jira/secure/attachment/12945557/Plugins_PluginID.jpg] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2266) To make Id to ID in Audit Pages of Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2266: Description: The ID in the Audit web pages of Ranger Admin is not uniform. There are two ways to write in the pages: Id and ID. In Access, Table Head: Policy ID In Admin, Table Head and Search Options: Session Id In Login Sessions, Table Head and Search Options: Session Id, Login Id In Plugins, Table Head: Plugin Id, but Search Options: Plugin ID Please check the following screenshots: [Access|https://issues.apache.org/jira/secure/attachment/12945554/Access_PolicyID.jpg] [Admin|https://issues.apache.org/jira/secure/attachment/1294/Admin_SessionID.jpg] [Login Sessions|https://issues.apache.org/jira/secure/attachment/12945556/LoginSeeions_LoginIDandSessionID.jpg] [Plugins|https://issues.apache.org/jira/secure/attachment/12945557/Plugins_PluginID.jpg] was: The ID in the Audit web pages of Ranger Admin is not uniform. There are two ways to write in the pages: Id and ID. In Access, Table Head: Policy ID In Admin, Table Head and Search Options: Session Id In Login Sessions, Table Head and Search Options: Session Id, Login Id In Plugins, Table Head: Plugin Id, but Search Options: Plugin ID Please check the following screenshots: [Access|] [Admin|] [Login Sessions|] [Plugins|] > To make Id to ID in Audit Pages of Ranger Admin > > > Key: RANGER-2266 > URL: https://issues.apache.org/jira/browse/RANGER-2266 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, web > Attachments: Access_PolicyID.jpg, Admin_SessionID.jpg, > LoginSeeions_LoginIDandSessionID.jpg, Plugins_PluginID.jpg > > > The ID in the Audit web pages of Ranger Admin is not uniform. > There are two ways to write in the pages: Id and ID. > In Access, Table Head: Policy ID > In Admin, Table Head and Search Options: Session Id > In Login Sessions, Table Head and Search Options: Session Id, Login Id > In Plugins, Table Head: Plugin Id, but Search Options: Plugin ID > Please check the following screenshots: > [Access|https://issues.apache.org/jira/secure/attachment/12945554/Access_PolicyID.jpg] > [Admin|https://issues.apache.org/jira/secure/attachment/1294/Admin_SessionID.jpg] > [Login > Sessions|https://issues.apache.org/jira/secure/attachment/12945556/LoginSeeions_LoginIDandSessionID.jpg] > [Plugins|https://issues.apache.org/jira/secure/attachment/12945557/Plugins_PluginID.jpg] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2266) To make Id to ID in Audit Pages of Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2266: Attachment: Plugins_PluginID.jpg LoginSeeions_LoginIDandSessionID.jpg Admin_SessionID.jpg Access_PolicyID.jpg > To make Id to ID in Audit Pages of Ranger Admin > > > Key: RANGER-2266 > URL: https://issues.apache.org/jira/browse/RANGER-2266 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: UI, web > Attachments: Access_PolicyID.jpg, Admin_SessionID.jpg, > LoginSeeions_LoginIDandSessionID.jpg, Plugins_PluginID.jpg > > > The ID in the Audit web pages of Ranger Admin is not uniform. > There are two ways to write in the pages: Id and ID. > In Access, Table Head: Policy ID > In Admin, Table Head and Search Options: Session Id > In Login Sessions, Table Head and Search Options: Session Id, Login Id > In Plugins, Table Head: Plugin Id, but Search Options: Plugin ID > Please check the following screenshots: > [Access|] > [Admin|] > [Login Sessions|] > [Plugins|] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2266) To make Id to ID in Audit Pages of Ranger Admin
Qiang Zhang created RANGER-2266: --- Summary: To make Id to ID in Audit Pages of Ranger Admin Key: RANGER-2266 URL: https://issues.apache.org/jira/browse/RANGER-2266 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang The ID in the Audit web pages of Ranger Admin is not uniform. There are two ways to write in the pages: Id and ID. In Access, Table Head: Policy ID In Admin, Table Head and Search Options: Session Id In Login Sessions, Table Head and Search Options: Session Id, Login Id In Plugins, Table Head: Plugin Id, but Search Options: Plugin ID Please check the following screenshots: [Access|] [Admin|] [Login Sessions|] [Plugins|] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
