[jira] [Created] (RANGER-2265) To make the profile "all" to be active by default when ranger build
Qiang Zhang created RANGER-2265: --- Summary: 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 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 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] Use the following command to find default profile, we can see the profile "linux" is active: 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) 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 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. 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-2258) Improve the policy list page to prompt users when the service is disabled
[ https://issues.apache.org/jira/browse/RANGER-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656426#comment-16656426 ] Qiang Zhang commented on RANGER-2258: - Review request available at: https://reviews.apache.org/r/69081/ > Improve the policy list page to prompt users when the service is disabled > - > > Key: RANGER-2258 > URL: https://issues.apache.org/jira/browse/RANGER-2258 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2258-Improve-the-policy-list-page-to-prompt-u.patch, Modify.PNG > > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944673/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2258) Improve the policy list page to prompt users when the service is disabled
[ https://issues.apache.org/jira/browse/RANGER-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2258: Attachment: 0001-RANGER-2258-Improve-the-policy-list-page-to-prompt-u.patch > Improve the policy list page to prompt users when the service is disabled > - > > Key: RANGER-2258 > URL: https://issues.apache.org/jira/browse/RANGER-2258 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2258-Improve-the-policy-list-page-to-prompt-u.patch, Modify.PNG > > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944673/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2258) Improve the policy list page to prompt users when the service is disabled
[ https://issues.apache.org/jira/browse/RANGER-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2258: Attachment: Modify.PNG > Improve the policy list page to prompt users when the service is disabled > - > > Key: RANGER-2258 > URL: https://issues.apache.org/jira/browse/RANGER-2258 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: Modify.PNG > > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2258) Improve the policy list page to prompt users when the service is disabled
[ https://issues.apache.org/jira/browse/RANGER-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2258: Description: After disabling the service, the policy list page displays "No Policies found!", the user can still add policies, but the page still displays 'No Policies found!', which may cause user confusion. Modify the prompt message to “No Policies found! The service is disabled!” and hide the “Add new policy” button when the service is disabled. Modified screenshots: https://issues.apache.org/jira/secure/attachment/12944673/Modify.PNG was: After disabling the service, the policy list page displays "No Policies found!", the user can still add policies, but the page still displays 'No Policies found!', which may cause user confusion. Modify the prompt message to “No Policies found! The service is disabled!” and hide the “Add new policy” button when the service is disabled. > Improve the policy list page to prompt users when the service is disabled > - > > Key: RANGER-2258 > URL: https://issues.apache.org/jira/browse/RANGER-2258 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: Modify.PNG > > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944673/Modify.PNG -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2258) Improve the policy list page to prompt users when the service is disabled
[ https://issues.apache.org/jira/browse/RANGER-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2258: Description: After disabling the service, the policy list page displays "No Policies found!", the user can still add policies, but the page still displays 'No Policies found!', which may cause user confusion. Modify the prompt message to “No Policies found! The service is disabled!” and hide the “Add new policy” button when the service is disabled. > Improve the policy list page to prompt users when the service is disabled > - > > Key: RANGER-2258 > URL: https://issues.apache.org/jira/browse/RANGER-2258 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > > After disabling the service, the policy list page displays "No Policies > found!", the user can still add policies, but the page still displays 'No > Policies found!', which may cause user confusion. > Modify the prompt message to “No Policies found! The service is disabled!” > and hide the “Add new policy” button when the service is disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2258) Improve the policy list page to prompt users when the service is disabled
Qiang Zhang created RANGER-2258: --- Summary: Improve the policy list page to prompt users when the service is disabled Key: RANGER-2258 URL: https://issues.apache.org/jira/browse/RANGER-2258 Project: Ranger Issue Type: Improvement Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2257) Add policyID to error message when click the Access log of Audit
[ https://issues.apache.org/jira/browse/RANGER-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656232#comment-16656232 ] Qiang Zhang commented on RANGER-2257: - Review Requet: https://reviews.apache.org/r/69080/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12944656/0001-RANGER-2257-Add-policyID-to-error-message-when-click.patch] Implementation details: [Modified screenshots|https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png] > Add policyID to error message when click the Access log of Audit > > > Key: RANGER-2257 > URL: https://issues.apache.org/jira/browse/RANGER-2257 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: ErrorMessage, UI > Attachments: > 0001-RANGER-2257-Add-policyID-to-error-message-when-click.patch, > IDandTime.png, OnlyTime.png > > Original Estimate: 12h > Remaining Estimate: 12h > > Check the Access log of Audit in RangerAdmin, > click on a log to see its corresponding policyID history, > If the policyID does not exist, the following error will occur: > No policy history found for given time: 2018-08-14T08:43:11Z > Please check the following screenshots: > https://issues.apache.org/jira/secure/attachment/12944645/OnlyTime.png > The information given in the above error message does not give policyID > information, > which can lead to user confusion. > Add policyID to modify the error message as follows: > No policy history found for given policy ID: 1 and event time: > 2018-08-14T08:43:11Z > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2257) Add policyID to error message when click the Access log of Audit
[ https://issues.apache.org/jira/browse/RANGER-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2257: Attachment: 0001-RANGER-2257-Add-policyID-to-error-message-when-click.patch > Add policyID to error message when click the Access log of Audit > > > Key: RANGER-2257 > URL: https://issues.apache.org/jira/browse/RANGER-2257 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: ErrorMessage, UI > Attachments: > 0001-RANGER-2257-Add-policyID-to-error-message-when-click.patch, > IDandTime.png, OnlyTime.png > > Original Estimate: 12h > Remaining Estimate: 12h > > Check the Access log of Audit in RangerAdmin, > click on a log to see its corresponding policyID history, > If the policyID does not exist, the following error will occur: > No policy history found for given time: 2018-08-14T08:43:11Z > Please check the following screenshots: > https://issues.apache.org/jira/secure/attachment/12944645/OnlyTime.png > The information given in the above error message does not give policyID > information, > which can lead to user confusion. > Add policyID to modify the error message as follows: > No policy history found for given policy ID: 1 and event time: > 2018-08-14T08:43:11Z > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2257) Add policyID to error message when click the Access log of Audit
[ https://issues.apache.org/jira/browse/RANGER-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2257: Description: Check the Access log of Audit in RangerAdmin, click on a log to see its corresponding policyID history, If the policyID does not exist, the following error will occur: No policy history found for given time: 2018-08-14T08:43:11Z Please check the following screenshots: https://issues.apache.org/jira/secure/attachment/12944645/OnlyTime.png The information given in the above error message does not give policyID information, which can lead to user confusion. Add policyID to modify the error message as follows: No policy history found for given policy ID: 1 and event time: 2018-08-14T08:43:11Z Modified screenshots: https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png was: Check the Access log of Audit in RangerAdmin, click on a log to see its corresponding policyID history, If the policyID does not exist, the following error will occur: No policy history found for given time: 2018-08-14T08:43:11Z Please check the following screenshots: The information given in the above error message does not give policyID information, which can lead to user confusion. Add policyID to modify the error message as follows: No policy history found for given policy ID: 1 and event time: 2018-08-14T08:43:11Z > Add policyID to error message when click the Access log of Audit > > > Key: RANGER-2257 > URL: https://issues.apache.org/jira/browse/RANGER-2257 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: ErrorMessage, UI > Attachments: IDandTime.png, OnlyTime.png > > Original Estimate: 12h > Remaining Estimate: 12h > > Check the Access log of Audit in RangerAdmin, > click on a log to see its corresponding policyID history, > If the policyID does not exist, the following error will occur: > No policy history found for given time: 2018-08-14T08:43:11Z > Please check the following screenshots: > https://issues.apache.org/jira/secure/attachment/12944645/OnlyTime.png > The information given in the above error message does not give policyID > information, > which can lead to user confusion. > Add policyID to modify the error message as follows: > No policy history found for given policy ID: 1 and event time: > 2018-08-14T08:43:11Z > Modified screenshots: > https://issues.apache.org/jira/secure/attachment/12944644/IDandTime.png -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2257) Add policyID to error message when click the Access log of Audit
[ https://issues.apache.org/jira/browse/RANGER-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2257: Attachment: OnlyTime.png IDandTime.png > Add policyID to error message when click the Access log of Audit > > > Key: RANGER-2257 > URL: https://issues.apache.org/jira/browse/RANGER-2257 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: ErrorMessage, UI > Attachments: IDandTime.png, OnlyTime.png > > Original Estimate: 12h > Remaining Estimate: 12h > > Check the Access log of Audit in RangerAdmin, > click on a log to see its corresponding policyID history, > If the policyID does not exist, the following error will occur: > No policy history found for given time: 2018-08-14T08:43:11Z > Please check the following screenshots: > The information given in the above error message does not give policyID > information, > which can lead to user confusion. > Add policyID to modify the error message as follows: > No policy history found for given policy ID: 1 and event time: > 2018-08-14T08:43:11Z -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2257) Add policyID to error message when click the Access log of Audit
Qiang Zhang created RANGER-2257: --- Summary: Add policyID to error message when click the Access log of Audit Key: RANGER-2257 URL: https://issues.apache.org/jira/browse/RANGER-2257 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Check the Access log of Audit in RangerAdmin, click on a log to see its corresponding policyID history, If the policyID does not exist, the following error will occur: No policy history found for given time: 2018-08-14T08:43:11Z Please check the following screenshots: The information given in the above error message does not give policyID information, which can lead to user confusion. Add policyID to modify the error message as follows: No policy history found for given policy ID: 1 and event time: 2018-08-14T08:43:11Z -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2238) String comparison should not use ‘==’ in ServiceUtil.java
[
https://issues.apache.org/jira/browse/RANGER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16647517#comment-16647517
]
Qiang Zhang commented on RANGER-2238:
-
Committed to Apache master branch:
https://github.com/apache/ranger/commit/3d59099dcff757d420748793d6d9abe904a59165
Committed to Apache ranger-1.2 branch:
https://github.com/apache/ranger/commit/d21b7b54e75c5b0155345cc1fbcd181241e36ca0
Committed to Apache ranger-1.1 branch:
https://github.com/apache/ranger/commit/821b6ecbca2672f3ea6d278ddaa779a822fdb305
Committed to Apache ranger-1 branch:
https://github.com/apache/ranger/commit/f2a080d5dd9e9b931b8f19045633b36a7b76a2bd
> String comparison should not use ‘==’ in ServiceUtil.java
> -
>
> Key: RANGER-2238
> URL: https://issues.apache.org/jira/browse/RANGER-2238
> 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-2238-String-comparison-should-not-use-in-Serv.patch
>
>
> Here is related code:
> {code:java}
> for(RangerPolicy.RangerPolicyItemCondition condition :
> policyItem.getConditions()) {
> if(condition.getType() == "ipaddress") {
> {code}
> equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-2248) Sorting does not work in AbstractPredicateUtil.java
[ https://issues.apache.org/jira/browse/RANGER-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646064#comment-16646064 ] Qiang Zhang commented on RANGER-2248: - Review request available at: https://reviews.apache.org/r/68990/ > Sorting does not work in AbstractPredicateUtil.java > --- > > Key: RANGER-2248 > URL: https://issues.apache.org/jira/browse/RANGER-2248 > 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-2248-Sorting-does-not-work-in-AbstractPredica.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2248) Sorting does not work in AbstractPredicateUtil.java
[ https://issues.apache.org/jira/browse/RANGER-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2248: Attachment: 0001-RANGER-2248-Sorting-does-not-work-in-AbstractPredica.patch > Sorting does not work in AbstractPredicateUtil.java > --- > > Key: RANGER-2248 > URL: https://issues.apache.org/jira/browse/RANGER-2248 > 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-2248-Sorting-does-not-work-in-AbstractPredica.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2248) Sorting does not work in AbstractPredicateUtil.java
Qiang Zhang created RANGER-2248: --- Summary: Sorting does not work in AbstractPredicateUtil.java Key: RANGER-2248 URL: https://issues.apache.org/jira/browse/RANGER-2248 Project: Ranger Issue Type: Bug Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2244) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.91 or later.
Qiang Zhang created RANGER-2244: --- Summary: 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 Fix For: 2.0.0 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-2238) String comparison should not use ‘==’ in ServiceUtil.java
[
https://issues.apache.org/jira/browse/RANGER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang updated RANGER-2238:
Attachment: (was:
0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch)
> String comparison should not use ‘==’ in ServiceUtil.java
> -
>
> Key: RANGER-2238
> URL: https://issues.apache.org/jira/browse/RANGER-2238
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Attachments:
> 0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch
>
>
> Here is related code:
> {code:java}
> for(RangerPolicy.RangerPolicyItemCondition condition :
> policyItem.getConditions()) {
> if(condition.getType() == "ipaddress") {
> {code}
> equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2238) String comparison should not use ‘==’ in ServiceUtil.java
[
https://issues.apache.org/jira/browse/RANGER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang updated RANGER-2238:
Attachment: 0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch
> String comparison should not use ‘==’ in ServiceUtil.java
> -
>
> Key: RANGER-2238
> URL: https://issues.apache.org/jira/browse/RANGER-2238
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Attachments:
> 0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch
>
>
> Here is related code:
> {code:java}
> for(RangerPolicy.RangerPolicyItemCondition condition :
> policyItem.getConditions()) {
> if(condition.getType() == "ipaddress") {
> {code}
> equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2237) Upgrade Kylin version to 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2237: Attachment: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > Upgrade Kylin version to 2.5.0 > -- > > Key: RANGER-2237 > URL: https://issues.apache.org/jira/browse/RANGER-2237 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > > > Upgrade kylin version to 2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2237) Upgrade Kylin version to 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2237: Attachment: (was: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch) > Upgrade Kylin version to 2.5.0 > -- > > Key: RANGER-2237 > URL: https://issues.apache.org/jira/browse/RANGER-2237 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > > > Upgrade kylin version to 2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2238) String comparison should not use ‘==’ in ServiceUtil.java
[
https://issues.apache.org/jira/browse/RANGER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631299#comment-16631299
]
Qiang Zhang commented on RANGER-2238:
-
Review request available at:
https://reviews.apache.org/r/68871/
> String comparison should not use ‘==’ in ServiceUtil.java
> -
>
> Key: RANGER-2238
> URL: https://issues.apache.org/jira/browse/RANGER-2238
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Attachments:
> 0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch
>
>
> Here is related code:
> {code:java}
> for(RangerPolicy.RangerPolicyItemCondition condition :
> policyItem.getConditions()) {
> if(condition.getType() == "ipaddress") {
> {code}
> equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2238) String comparison should not use ‘==’ in ServiceUtil.java
[
https://issues.apache.org/jira/browse/RANGER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang updated RANGER-2238:
Attachment: 0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch
> String comparison should not use ‘==’ in ServiceUtil.java
> -
>
> Key: RANGER-2238
> URL: https://issues.apache.org/jira/browse/RANGER-2238
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Attachments:
> 0001-RANGER-2238-String-comparison-should-not-use-in-Serv.patch
>
>
> Here is related code:
> {code:java}
> for(RangerPolicy.RangerPolicyItemCondition condition :
> policyItem.getConditions()) {
> if(condition.getType() == "ipaddress") {
> {code}
> equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2238) String comparison should not use ‘==’ in ServiceUtil.java
Qiang Zhang created RANGER-2238:
---
Summary: String comparison should not use ‘==’ in ServiceUtil.java
Key: RANGER-2238
URL: https://issues.apache.org/jira/browse/RANGER-2238
Project: Ranger
Issue Type: Bug
Components: admin
Affects Versions: master
Reporter: Qiang Zhang
Assignee: Qiang Zhang
Here is related code:
{code:java}
for(RangerPolicy.RangerPolicyItemCondition condition :
policyItem.getConditions()) {
if(condition.getType() == "ipaddress") {
{code}
equals() should be used to compare Strings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2237) Upgrade Kylin version to 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2237: Priority: Major (was: Minor) > Upgrade Kylin version to 2.5.0 > -- > > Key: RANGER-2237 > URL: https://issues.apache.org/jira/browse/RANGER-2237 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > > > Upgrade kylin version to 2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2237) Upgrade Kylin version to 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16629856#comment-16629856 ] Qiang Zhang commented on RANGER-2237: - Review request available at: https://reviews.apache.org/r/68864/ > Upgrade Kylin version to 2.5.0 > -- > > Key: RANGER-2237 > URL: https://issues.apache.org/jira/browse/RANGER-2237 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > > > Upgrade kylin version to 2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2237) Upgrade Kylin version to 2.5.0
[ https://issues.apache.org/jira/browse/RANGER-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2237: Attachment: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > Upgrade Kylin version to 2.5.0 > -- > > Key: RANGER-2237 > URL: https://issues.apache.org/jira/browse/RANGER-2237 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2237-Upgrade-Kylin-version-to-2.5.0.patch > > > Upgrade kylin version to 2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2237) Upgrade Kylin version to 2.5.0
Qiang Zhang created RANGER-2237: --- Summary: Upgrade Kylin version to 2.5.0 Key: RANGER-2237 URL: https://issues.apache.org/jira/browse/RANGER-2237 Project: Ranger Issue Type: Task Components: plugins Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Upgrade kylin version to 2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2235) Modify the login session detail page as a modal.
[ https://issues.apache.org/jira/browse/RANGER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16628454#comment-16628454 ] Qiang Zhang commented on RANGER-2235: - Review request available at: https://reviews.apache.org/r/68849/ > Modify the login session detail page as a modal. > > > Key: RANGER-2235 > URL: https://issues.apache.org/jira/browse/RANGER-2235 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2235-Modify-the-login-session-detail-page-as-.patch, Audit Admin > tab.PNG, Login Session Detail Modal.PNG > > > On the Audit Admin tab page, if the user clicks to view the session details, > it will jump to a new page, user cannot return to previous page. We need to > click again to enter the Audit Admin tab page, and reselect the filter > condition and the page number. > Audit Login Sessions tab page has the same problem. > Modify the login session detail page as a modal，the user can continue to view > the current page after close the modal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2235) Modify the login session detail page as a modal.
[ https://issues.apache.org/jira/browse/RANGER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2235: Attachment: 0001-RANGER-2235-Modify-the-login-session-detail-page-as-.patch > Modify the login session detail page as a modal. > > > Key: RANGER-2235 > URL: https://issues.apache.org/jira/browse/RANGER-2235 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2235-Modify-the-login-session-detail-page-as-.patch, Audit Admin > tab.PNG, Login Session Detail Modal.PNG > > > On the Audit Admin tab page, if the user clicks to view the session details, > it will jump to a new page, user cannot return to previous page. We need to > click again to enter the Audit Admin tab page, and reselect the filter > condition and the page number. > Audit Login Sessions tab page has the same problem. > Modify the login session detail page as a modal，the user can continue to view > the current page after close the modal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2235) Modify the login session detail page as a modal.
[ https://issues.apache.org/jira/browse/RANGER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2235: Description: On the Audit Admin tab page, if the user clicks to view the session details, it will jump to a new page, user cannot return to previous page. We need to click again to enter the Audit Admin tab page, and reselect the filter condition and the page number. Audit Login Sessions tab page has the same problem. Modify the login session detail page as a modal，the user can continue to view the current page after close the modal. was: On the Audit Admin tab page, if the user clicks to view the session details, it will jump to a new page, user cannot return to previous page. We need to click again to enter the Audit Admin tab page, and reselect the filter condition and the page number. Modify the login session detail page as a modal，the user can continue to view the current page after close the modal. > Modify the login session detail page as a modal. > > > Key: RANGER-2235 > URL: https://issues.apache.org/jira/browse/RANGER-2235 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2235-Modify-the-login-session-detail-page-as-.patch, Audit Admin > tab.PNG, Login Session Detail Modal.PNG > > > On the Audit Admin tab page, if the user clicks to view the session details, > it will jump to a new page, user cannot return to previous page. We need to > click again to enter the Audit Admin tab page, and reselect the filter > condition and the page number. > Audit Login Sessions tab page has the same problem. > Modify the login session detail page as a modal，the user can continue to view > the current page after close the modal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2235) Modify the login session detail page as a modal.
[ https://issues.apache.org/jira/browse/RANGER-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2235: Attachment: Login Session Detail Modal.PNG Audit Admin tab.PNG > Modify the login session detail page as a modal. > > > Key: RANGER-2235 > URL: https://issues.apache.org/jira/browse/RANGER-2235 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: Audit Admin tab.PNG, Login Session Detail Modal.PNG > > > On the Audit Admin tab page, if the user clicks to view the session details, > it will jump to a new page, user cannot return to previous page. We need to > click again to enter the Audit Admin tab page, and reselect the filter > condition and the page number. > Modify the login session detail page as a modal，the user can continue to view > the current page after close the modal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2235) Modify the login session detail page as a modal.
Qiang Zhang created RANGER-2235: --- Summary: Modify the login session detail page as a modal. Key: RANGER-2235 URL: https://issues.apache.org/jira/browse/RANGER-2235 Project: Ranger Issue Type: Bug Components: admin Affects Versions: 1.1.0 Reporter: Qiang Zhang Assignee: Qiang Zhang On the Audit Admin tab page, if the user clicks to view the session details, it will jump to a new page, user cannot return to previous page. We need to click again to enter the Audit Admin tab page, and reselect the filter condition and the page number. Modify the login session detail page as a modal，the user can continue to view the current page after close the modal. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2213) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.90.
[ https://issues.apache.org/jira/browse/RANGER-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2213. - Resolution: Fixed > Tomcat Security Vulnerability Alert. The version of the tomcat for ranger > should upgrade to 7.0.90. > --- > > Key: RANGER-2213 > URL: https://issues.apache.org/jira/browse/RANGER-2213 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: 2.0.0, 1.2.0 > > Attachments: > 0001-RANGER-2213-Tomcat-Security-Vulnerability-Alert.-The.patch > > > [SECURITY] CVE-2018-1336 > Severity: High > Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.7, 8.5.0 to 8.5.30, > 8.0.0.RC1 to 8.0.51, and 7.0.28 to 7.0.86. > Description: An improper handing of overflow in the UTF-8 decoder with > supplementary characters can lead to an infinite loop in the decoder causing > a Denial of Service. > CVE-2018-8014 > Description: The defaults settings for the CORS filter provided in Apache > Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to > 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is > expected that users of the CORS filter will have configured it appropriately > for their environment rather than using it in the default configuration. > Therefore, it is expected that most users will not be impacted by this issue. > CVE-2018-8034 > Description: The host name verification when using TLS with the WebSocket > client was missing. It is now enabled by default. > Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, > 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2212) Add multiple urls tips for the ‘Kylin URL’ configuration item when creating the kylin-plugin service
[ https://issues.apache.org/jira/browse/RANGER-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2212. - Resolution: Fixed Fix Version/s: master > Add multiple urls tips for the ‘Kylin URL’ configuration item when creating > the kylin-plugin service > > > Key: RANGER-2212 > URL: https://issues.apache.org/jira/browse/RANGER-2212 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Fix For: master > > Attachments: > 0001-RANGER-2212-Add-multiple-urls-tips-for-the-Kylin-URL.patch > > > Add multiple urls tips for the ‘Kylin URL’ configuration item: > 1.For one url, eg. > 'http://:7070' > 2.For multiple urls (use , or ; delimiter), eg. > 'http://:7070,http://:7070' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2214) Do some code improvement for the error message for KylinClient.java
[ https://issues.apache.org/jira/browse/RANGER-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2214. - Resolution: Fixed Fix Version/s: master > Do some code improvement for the error message for KylinClient.java > --- > > Key: RANGER-2214 > URL: https://issues.apache.org/jira/browse/RANGER-2214 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: master > > Attachments: > 0001-RANGER-2214-Do-some-code-improvement-for-the-error-m.patch > > > Now the test connection get an error return, such as 401, the error message > always show 'got null response' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2214) Do some code improvement for the error message for KylinClient.java
[ https://issues.apache.org/jira/browse/RANGER-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2214: Attachment: 0001-RANGER-2214-Do-some-code-improvement-for-the-error-m.patch > Do some code improvement for the error message for KylinClient.java > --- > > Key: RANGER-2214 > URL: https://issues.apache.org/jira/browse/RANGER-2214 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2214-Do-some-code-improvement-for-the-error-m.patch > > > Now the test connection get an error return, such as 401, the error message > always show 'got null response' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2214) Do some code improvement for the error message for KylinClient.java
Qiang Zhang created RANGER-2214: --- Summary: Do some code improvement for the error message for KylinClient.java Key: RANGER-2214 URL: https://issues.apache.org/jira/browse/RANGER-2214 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Now the test connection get an error return, such as 401, the error message always show 'got null response' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2213) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.90.
[ https://issues.apache.org/jira/browse/RANGER-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2213: Attachment: 0001-RANGER-2213-Tomcat-Security-Vulnerability-Alert.-The.patch > Tomcat Security Vulnerability Alert. The version of the tomcat for ranger > should upgrade to 7.0.90. > --- > > Key: RANGER-2213 > URL: https://issues.apache.org/jira/browse/RANGER-2213 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2213-Tomcat-Security-Vulnerability-Alert.-The.patch > > > [SECURITY] CVE-2018-1336 > Severity: High > Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.7, 8.5.0 to 8.5.30, > 8.0.0.RC1 to 8.0.51, and 7.0.28 to 7.0.86. > Description: An improper handing of overflow in the UTF-8 decoder with > supplementary characters can lead to an infinite loop in the decoder causing > a Denial of Service. > CVE-2018-8014 > Description: The defaults settings for the CORS filter provided in Apache > Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to > 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is > expected that users of the CORS filter will have configured it appropriately > for their environment rather than using it in the default configuration. > Therefore, it is expected that most users will not be impacted by this issue. > CVE-2018-8034 > Description: The host name verification when using TLS with the WebSocket > client was missing. It is now enabled by default. > Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, > 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2213) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.90.
Qiang Zhang created RANGER-2213: --- Summary: Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.90. Key: RANGER-2213 URL: https://issues.apache.org/jira/browse/RANGER-2213 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang [SECURITY] CVE-2018-1336 Severity: High Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.7, 8.5.0 to 8.5.30, 8.0.0.RC1 to 8.0.51, and 7.0.28 to 7.0.86. Description: An improper handing of overflow in the UTF-8 decoder with supplementary characters can lead to an infinite loop in the decoder causing a Denial of Service. CVE-2018-8014 Description: The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue. CVE-2018-8034 Description: The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2212) Add multiple urls tips for the ‘Kylin URL’ configuration item when creating the kylin-plugin service
[ https://issues.apache.org/jira/browse/RANGER-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2212: Attachment: 0001-RANGER-2212-Add-multiple-urls-tips-for-the-Kylin-URL.patch > Add multiple urls tips for the ‘Kylin URL’ configuration item when creating > the kylin-plugin service > > > Key: RANGER-2212 > URL: https://issues.apache.org/jira/browse/RANGER-2212 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Attachments: > 0001-RANGER-2212-Add-multiple-urls-tips-for-the-Kylin-URL.patch > > > Add multiple urls tips for the ‘Kylin URL’ configuration item: > 1.For one url, eg. > 'http://:7070' > 2.For multiple urls (use , or ; delimiter), eg. > 'http://:7070,http://:7070' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2212) Add multiple urls tips for the ‘Kylin URL’ configuration item when creating the kylin-plugin service
Qiang Zhang created RANGER-2212: --- Summary: Add multiple urls tips for the ‘Kylin URL’ configuration item when creating the kylin-plugin service Key: RANGER-2212 URL: https://issues.apache.org/jira/browse/RANGER-2212 Project: Ranger Issue Type: Improvement Components: admin Affects Versions: master Reporter: Qiang Zhang Assignee: Qiang Zhang Add multiple urls tips for the ‘Kylin URL’ configuration item: 1.For one url, eg. 'http://:7070' 2.For multiple urls (use , or ; delimiter), eg. 'http://:7070,http://:7070' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2193) Form validation during testconnection should be consistent with service creation/editing
[ https://issues.apache.org/jira/browse/RANGER-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2193: Attachment: 0001-RANGER-2193-Form-validation-during-testconnection-sh.patch > Form validation during testconnection should be consistent with service > creation/editing > > > Key: RANGER-2193 > URL: https://issues.apache.org/jira/browse/RANGER-2193 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2193-Form-validation-during-testconnection-sh.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2170) Ranger supports plugin to enable, monitor and manage Elasticsearch
[ https://issues.apache.org/jira/browse/RANGER-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16563379#comment-16563379 ] Qiang Zhang edited comment on RANGER-2170 at 8/14/18 8:47 AM: -- 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] was (Author: zhangqiang2): Review Requet: https://reviews.apache.org/r/68128/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12933727/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: > 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: 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] [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=16574495#comment-16574495
]
Qiang Zhang commented on RANGER-2170:
-
Test Steps:
1.Intall
Ranger Elasticsearch Plugin Installation Guide
https://cwiki.apache.org/confluence/display/RANGER/Elasticsearch+Plugin
Include install Elasticsearch and Ranger Elasticsearch Plugin,
and verify install result.
2.Create policy in Ranger Admin
User "elasticsearch" has all permissions on all indices.
User "yuwen" has permission "read" on index "twitter".
3.Test permission
3.1 successful:
curl -u elasticsearch:xxx -X GET "localhost:9200/twitter/_stats?pretty"
curl -u elasticsearch:xxx -X GET "localhost:9200/twitter2/_stats?pretty"
curl -u yuwen:xxx -X GET "localhost:9200/twitter/_stats?pretty"
3.2 failed:
curl -X GET "localhost:9200/twitter/_stats?pretty"
{
"error" : {
"root_cause" : [
{
"type" : "status_exception",
"reason" : "Error: User is null, the request requires user
authentication."
}
],
"type" : "status_exception",
"reason" : "Error: User is null, the request requires user authentication."
},
"status" : 401
}
curl -u yuwen:xxx -X GET "localhost:9200/twitter2/_stats?pretty"
{
"error" : {
"root_cause" : [
{
"type" : "status_exception",
"reason" : "Error: User[yuwen] could not do
action[indices:monitor/stats] on index[twitter2]"
}
],
"type" : "status_exception",
"reason" : "Error: User[yuwen] could not do action[indices:monitor/stats]
on index[twitter2]"
},
"status" : 403
}
> 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-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: (was: 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch) > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > no-resolved-button.png, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > no-resolved-button.png, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > no-resolved-button.png, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: (was: 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch) > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > no-resolved-button.png, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > 0002-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, > no-resolved-button.png, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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:comment-tabpanel=16564843#comment-16564843 ] Qiang Zhang commented on RANGER-2175: - Plugin Installation Guide https://cwiki.apache.org/confluence/display/RANGER/Elasticsearch+Plugin Include install Elasticsearch and Ranger Elasticsearch Plugin, and verify install result. > 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 > > Write install guide for Ranger Elasticsearch plugin RANGER-2170 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (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:comment-tabpanel=16564843#comment-16564843 ] Qiang Zhang edited comment on RANGER-2175 at 8/1/18 6:52 AM: - Ranger Elasticsearch Plugin Installation Guide https://cwiki.apache.org/confluence/display/RANGER/Elasticsearch+Plugin Include install Elasticsearch and Ranger Elasticsearch Plugin, and verify install result. was (Author: zhangqiang2): Plugin Installation Guide https://cwiki.apache.org/confluence/display/RANGER/Elasticsearch+Plugin Include install Elasticsearch and Ranger Elasticsearch Plugin, and verify install result. > 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 > > Write install guide for Ranger Elasticsearch plugin RANGER-2170 -- 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: 1_ElasticSearchServiceEntry.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: 7_ElasticSearchPluginStatus.jpg 6_ElasticSearchPlugins.jpg 5_ElasticSearchAuditLog.jpg 4_EditElasticSearchPolicy.jpg 3_ElasticSearchPolicies.jpg 2_EditElasticSearchService.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: 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 > > > 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] [Created] (RANGER-2175) Write install guide for Ranger Elasticsearch plugin RANGER-2170
Qiang Zhang created RANGER-2175: --- Summary: 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 Write install guide for Ranger Elasticsearch plugin RANGER-2170 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2170) Ranger supports plugin to enable, monitor and manage Elasticsearch
Qiang Zhang created RANGER-2170: --- Summary: 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 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-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: (was: 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch) > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Attachment: ranger-01.PNG > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch, ranger-01.PNG > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Affects Version/s: (was: 1.0.0) master > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Fix Version/s: 2.0.0 > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2153-Supply-the-function-of-reverting-policy-.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2153) Supply the function of reverting policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2153: Issue Type: New Feature (was: Bug) > Supply the function of reverting policy history version. > > > Key: RANGER-2153 > URL: https://issues.apache.org/jira/browse/RANGER-2153 > Project: Ranger > Issue Type: New Feature > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2153) Supply the function of reverting policy history version.
Qiang Zhang created RANGER-2153: --- Summary: Supply the function of reverting policy history version. Key: RANGER-2153 URL: https://issues.apache.org/jira/browse/RANGER-2153 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0 Reporter: Qiang Zhang Assignee: Qiang Zhang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2068) Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error.
[ https://issues.apache.org/jira/browse/RANGER-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2068. - Resolution: Fixed Fix Version/s: 1.0.1 1.1.0 master > Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error. > > > Key: RANGER-2068 > URL: https://issues.apache.org/jira/browse/RANGER-2068 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: master, 1.1.0, 1.0.1 > > Attachments: > 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch > > > 1. Set configuration items. > COMPONENT_INSTALL_DIR_NAME=/usr/local/hbase > POLICY_MGR_URL=https://sslrangerserver:6182 > 2. Install hbase plugin. > 3. Execute 'hbase-daemon.sh start master' command. > error log: > 2018-04-12 08:38:47,495 ERROR [sslmaster:16000.activeMasterManager] > util.PolicyRefresher: PolicyRefresher(serviceName=hbasedev): failed to > refresh policies. Will continue to use last known version of policies (-1) > com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: > Unexpected end of file from server > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149) > at com.sun.jersey.api.client.Client.handle(Client.java:648) > at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670) > at > com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) > at > com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:503) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:131) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:264) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:202) > at > org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:149) > at > org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:170) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1032) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1072) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup(CoprocessorHost.java:414) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:255) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:161) > at > org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:87) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:721) > at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) > at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) > at java.lang.Thread.run(Thread.java:748) > 4. error reason: the ranger.plugin.hbase.policy.rest.ssl.config.file was set > to /etc/hbase/conf/ranger-policymgr-ssl.xml. But the ranger-policymgr-ssl.xml > file is located under the /usr/local/hbase/conf path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2067) Supply the function of viewing policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2067. - Resolution: Fixed Fix Version/s: 1.1.0 master > Supply the function of viewing policy history version. > > > Key: RANGER-2067 > URL: https://issues.apache.org/jira/browse/RANGER-2067 > Project: Ranger > Issue Type: Task > Components: admin >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Fix For: master, 1.1.0 > > Attachments: > 0001-RANGER-2067-Supply-the-function-of-viewing-policy-hi.patch, > RANGER-2067.png > > > Supply the function of viewing policy history version. > We don't have view version history of the policy option except access audit > log. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2068) Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error.
[ https://issues.apache.org/jira/browse/RANGER-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2068: Attachment: 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch > Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error. > > > Key: RANGER-2068 > URL: https://issues.apache.org/jira/browse/RANGER-2068 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch > > > 1. Set configuration items. > COMPONENT_INSTALL_DIR_NAME=/usr/local/hbase > POLICY_MGR_URL=https://sslrangerserver:6182 > 2. Install hbase plugin. > 3. Execute 'hbase-daemon.sh start master' command. > error log: > 2018-04-12 08:38:47,495 ERROR [sslmaster:16000.activeMasterManager] > util.PolicyRefresher: PolicyRefresher(serviceName=hbasedev): failed to > refresh policies. Will continue to use last known version of policies (-1) > com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: > Unexpected end of file from server > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149) > at com.sun.jersey.api.client.Client.handle(Client.java:648) > at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670) > at > com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) > at > com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:503) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:131) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:264) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:202) > at > org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:149) > at > org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:170) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1032) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1072) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup(CoprocessorHost.java:414) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:255) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:161) > at > org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:87) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:721) > at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) > at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) > at java.lang.Thread.run(Thread.java:748) > 4. error reason: the ranger.plugin.hbase.policy.rest.ssl.config.file was set > to /etc/hbase/conf/ranger-policymgr-ssl.xml. But the ranger-policymgr-ssl.xml > file is located under the /usr/local/hbase/conf path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2068) Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error.
[ https://issues.apache.org/jira/browse/RANGER-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2068: Attachment: (was: 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch) > Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error. > > > Key: RANGER-2068 > URL: https://issues.apache.org/jira/browse/RANGER-2068 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch > > > 1. Set configuration items. > COMPONENT_INSTALL_DIR_NAME=/usr/local/hbase > POLICY_MGR_URL=https://sslrangerserver:6182 > 2. Install hbase plugin. > 3. Execute 'hbase-daemon.sh start master' command. > error log: > 2018-04-12 08:38:47,495 ERROR [sslmaster:16000.activeMasterManager] > util.PolicyRefresher: PolicyRefresher(serviceName=hbasedev): failed to > refresh policies. Will continue to use last known version of policies (-1) > com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: > Unexpected end of file from server > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149) > at com.sun.jersey.api.client.Client.handle(Client.java:648) > at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670) > at > com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) > at > com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:503) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:131) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:264) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:202) > at > org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:149) > at > org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:170) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1032) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1072) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup(CoprocessorHost.java:414) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:255) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:161) > at > org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:87) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:721) > at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) > at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) > at java.lang.Thread.run(Thread.java:748) > 4. error reason: the ranger.plugin.hbase.policy.rest.ssl.config.file was set > to /etc/hbase/conf/ranger-policymgr-ssl.xml. But the ranger-policymgr-ssl.xml > file is located under the /usr/local/hbase/conf path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2068) Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error.
[ https://issues.apache.org/jira/browse/RANGER-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2068: Attachment: 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch > Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error. > > > Key: RANGER-2068 > URL: https://issues.apache.org/jira/browse/RANGER-2068 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2068-Fix-ranger.plugin.hbase.policy.rest.ssl..patch > > > 1. Set configuration items. > COMPONENT_INSTALL_DIR_NAME=/usr/local/hbase > POLICY_MGR_URL=https://sslrangerserver:6182 > 2. Install hbase plugin. > 3. Execute 'hbase-daemon.sh start master' command. > error log: > 2018-04-12 08:38:47,495 ERROR [sslmaster:16000.activeMasterManager] > util.PolicyRefresher: PolicyRefresher(serviceName=hbasedev): failed to > refresh policies. Will continue to use last known version of policies (-1) > com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: > Unexpected end of file from server > at > com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149) > at com.sun.jersey.api.client.Client.handle(Client.java:648) > at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670) > at > com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) > at > com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:503) > at > org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:131) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:264) > at > org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:202) > at > org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:149) > at > org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:170) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1032) > at > org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1072) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup(CoprocessorHost.java:414) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:255) > at > org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:161) > at > org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:87) > at > org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:721) > at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) > at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) > at java.lang.Thread.run(Thread.java:748) > 4. error reason: the ranger.plugin.hbase.policy.rest.ssl.config.file was set > to /etc/hbase/conf/ranger-policymgr-ssl.xml. But the ranger-policymgr-ssl.xml > file is located under the /usr/local/hbase/conf path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2068) Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error.
Qiang Zhang created RANGER-2068: --- Summary: Fix ranger.plugin.hbase.policy.rest.ssl.config.file parameter error. Key: RANGER-2068 URL: https://issues.apache.org/jira/browse/RANGER-2068 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: master, 1.1.0, 1.0.1 Reporter: Qiang Zhang Assignee: Qiang Zhang 1. Set configuration items. COMPONENT_INSTALL_DIR_NAME=/usr/local/hbase POLICY_MGR_URL=https://sslrangerserver:6182 2. Install hbase plugin. 3. Execute 'hbase-daemon.sh start master' command. error log: 2018-04-12 08:38:47,495 ERROR [sslmaster:16000.activeMasterManager] util.PolicyRefresher: PolicyRefresher(serviceName=hbasedev): failed to refresh policies. Will continue to use last known version of policies (-1) com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: Unexpected end of file from server at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:149) at com.sun.jersey.api.client.Client.handle(Client.java:648) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670) at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:503) at org.apache.ranger.admin.client.RangerAdminRESTClient.getServicePoliciesIfUpdated(RangerAdminRESTClient.java:131) at org.apache.ranger.plugin.util.PolicyRefresher.loadPolicyfromPolicyAdmin(PolicyRefresher.java:264) at org.apache.ranger.plugin.util.PolicyRefresher.loadPolicy(PolicyRefresher.java:202) at org.apache.ranger.plugin.util.PolicyRefresher.startRefresher(PolicyRefresher.java:149) at org.apache.ranger.plugin.service.RangerBasePlugin.init(RangerBasePlugin.java:170) at org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1032) at org.apache.ranger.authorization.hbase.RangerAuthorizationCoprocessor.start(RangerAuthorizationCoprocessor.java:1072) at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$Environment.startup(CoprocessorHost.java:414) at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:255) at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadSystemCoprocessors(CoprocessorHost.java:161) at org.apache.hadoop.hbase.master.MasterCoprocessorHost.(MasterCoprocessorHost.java:87) at org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:721) at org.apache.hadoop.hbase.master.HMaster.access$600(HMaster.java:189) at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1803) at java.lang.Thread.run(Thread.java:748) 4. error reason: the ranger.plugin.hbase.policy.rest.ssl.config.file was set to /etc/hbase/conf/ranger-policymgr-ssl.xml. But the ranger-policymgr-ssl.xml file is located under the /usr/local/hbase/conf path. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2067) Supply the function of viewing policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2067: Attachment: RANGER-2067.png > Supply the function of viewing policy history version. > > > Key: RANGER-2067 > URL: https://issues.apache.org/jira/browse/RANGER-2067 > Project: Ranger > Issue Type: Task > Components: admin >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2067-Supply-the-function-of-viewing-policy-hi.patch, > RANGER-2067.png > > > Supply the function of viewing policy history version. > We don't can view the policy history version if without access allowed log. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2067) Supply the function of viewing policy history version.
[ https://issues.apache.org/jira/browse/RANGER-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2067: Attachment: 0001-RANGER-2067-Supply-the-function-of-viewing-policy-hi.patch > Supply the function of viewing policy history version. > > > Key: RANGER-2067 > URL: https://issues.apache.org/jira/browse/RANGER-2067 > Project: Ranger > Issue Type: Task > Components: admin >Affects Versions: master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-2067-Supply-the-function-of-viewing-policy-hi.patch > > > Supply the function of viewing policy history version. > We don't can view the policy history version if without access allowed log. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2067) Supply the function of viewing policy history version.
Qiang Zhang created RANGER-2067: --- Summary: Supply the function of viewing policy history version. Key: RANGER-2067 URL: https://issues.apache.org/jira/browse/RANGER-2067 Project: Ranger Issue Type: Task Components: admin Affects Versions: master, 1.1.0, 1.0.1 Reporter: Qiang Zhang Assignee: Qiang Zhang Supply the function of viewing policy history version. We don't can view the policy history version if without access allowed log. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2054) Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
[
https://issues.apache.org/jira/browse/RANGER-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang updated RANGER-2054:
Affects Version/s: master
> Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
>
>
> Key: RANGER-2054
> URL: https://issues.apache.org/jira/browse/RANGER-2054
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: master, 1.1.0
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Fix For: 1.1.0
>
> Attachments:
> 0001-RANGER-2054-Fix-new-findBugs-in-RangerAdminClientImp.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
>
> *** CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> /plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java:
> 68 in
> org.apache.ranger.authorization.kylin.authorizer.RangerAdminClientImpl.getServicePoliciesIfUpdated(long,
> long)()
> 62 }
> 63
> 64 java.nio.file.Path cachePath = FileSystems.getDefault()
> 65 .getPath(basedir, "/src/test/resources/" +
> cacheFilename);
> 66 byte[] cacheBytes = Files.readAllBytes(cachePath);
> 67
> >>> CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> >>> Found reliance on default encoding: new String(byte[]).
> 68 return gson.fromJson(new String(cacheBytes),
> ServicePolicies.class);
> 69 }
> 70
> 71 @Override
> 72 public void grantAccess(GrantRevokeRequest request) throws
> Exception {
> 73
> To view the defects in Coverity Scan visit,
> https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRZSbhom32dlDl11LWEm9nX11zsOWMf5dv3Q9Mogo-2FGua3FsLRTFft2V-2FOFC9o0P2e0-3D_d04ZgyDzSjlwpjXIuOFYDNE6R93Lal83MDClQK32PZsnIXFWgRi957MYBuy-2FlDkytlroFFT4DodK8yWwhtaHLaX8VDTgQexZ1KpM2ghdONIK2s05PzHFJPHt35agqZ9nM-2FaTS-2BwGKR0yiHd9VqwUDlZAGDFlrUyAnUh6f6i-2B3anlkbZqOzVnGOBWkfRi-2BewYxNrjphgpV2suFoBTWVzO0g-3D-3D
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-2054) Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
[
https://issues.apache.org/jira/browse/RANGER-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421989#comment-16421989
]
Qiang Zhang commented on RANGER-2054:
-
Review Requet:
https://reviews.apache.org/r/66389/
Solution patch, please see attachment:
[patch|https://issues.apache.org/jira/secure/attachment/12917167/0001-RANGER-2054-Fix-new-findBugs-in-RangerAdminClientImp.patch]
> Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
>
>
> Key: RANGER-2054
> URL: https://issues.apache.org/jira/browse/RANGER-2054
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 1.1.0
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Fix For: 1.1.0
>
> Attachments:
> 0001-RANGER-2054-Fix-new-findBugs-in-RangerAdminClientImp.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
>
> *** CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> /plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java:
> 68 in
> org.apache.ranger.authorization.kylin.authorizer.RangerAdminClientImpl.getServicePoliciesIfUpdated(long,
> long)()
> 62 }
> 63
> 64 java.nio.file.Path cachePath = FileSystems.getDefault()
> 65 .getPath(basedir, "/src/test/resources/" +
> cacheFilename);
> 66 byte[] cacheBytes = Files.readAllBytes(cachePath);
> 67
> >>> CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> >>> Found reliance on default encoding: new String(byte[]).
> 68 return gson.fromJson(new String(cacheBytes),
> ServicePolicies.class);
> 69 }
> 70
> 71 @Override
> 72 public void grantAccess(GrantRevokeRequest request) throws
> Exception {
> 73
> To view the defects in Coverity Scan visit,
> https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRZSbhom32dlDl11LWEm9nX11zsOWMf5dv3Q9Mogo-2FGua3FsLRTFft2V-2FOFC9o0P2e0-3D_d04ZgyDzSjlwpjXIuOFYDNE6R93Lal83MDClQK32PZsnIXFWgRi957MYBuy-2FlDkytlroFFT4DodK8yWwhtaHLaX8VDTgQexZ1KpM2ghdONIK2s05PzHFJPHt35agqZ9nM-2FaTS-2BwGKR0yiHd9VqwUDlZAGDFlrUyAnUh6f6i-2B3anlkbZqOzVnGOBWkfRi-2BewYxNrjphgpV2suFoBTWVzO0g-3D-3D
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2054) Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
[
https://issues.apache.org/jira/browse/RANGER-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang updated RANGER-2054:
Attachment: 0001-RANGER-2054-Fix-new-findBugs-in-RangerAdminClientImp.patch
> Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
>
>
> Key: RANGER-2054
> URL: https://issues.apache.org/jira/browse/RANGER-2054
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 1.1.0
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Fix For: 1.1.0
>
> Attachments:
> 0001-RANGER-2054-Fix-new-findBugs-in-RangerAdminClientImp.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
>
> *** CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> /plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java:
> 68 in
> org.apache.ranger.authorization.kylin.authorizer.RangerAdminClientImpl.getServicePoliciesIfUpdated(long,
> long)()
> 62 }
> 63
> 64 java.nio.file.Path cachePath = FileSystems.getDefault()
> 65 .getPath(basedir, "/src/test/resources/" +
> cacheFilename);
> 66 byte[] cacheBytes = Files.readAllBytes(cachePath);
> 67
> >>> CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
> >>> Found reliance on default encoding: new String(byte[]).
> 68 return gson.fromJson(new String(cacheBytes),
> ServicePolicies.class);
> 69 }
> 70
> 71 @Override
> 72 public void grantAccess(GrantRevokeRequest request) throws
> Exception {
> 73
> To view the defects in Coverity Scan visit,
> https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRZSbhom32dlDl11LWEm9nX11zsOWMf5dv3Q9Mogo-2FGua3FsLRTFft2V-2FOFC9o0P2e0-3D_d04ZgyDzSjlwpjXIuOFYDNE6R93Lal83MDClQK32PZsnIXFWgRi957MYBuy-2FlDkytlroFFT4DodK8yWwhtaHLaX8VDTgQexZ1KpM2ghdONIK2s05PzHFJPHt35agqZ9nM-2FaTS-2BwGKR0yiHd9VqwUDlZAGDFlrUyAnUh6f6i-2B3anlkbZqOzVnGOBWkfRi-2BewYxNrjphgpV2suFoBTWVzO0g-3D-3D
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2054) Fix new findBugs in RangerAdminClientImpl.java for kylin plugin test
Qiang Zhang created RANGER-2054:
---
Summary: Fix new findBugs in RangerAdminClientImpl.java for kylin
plugin test
Key: RANGER-2054
URL: https://issues.apache.org/jira/browse/RANGER-2054
Project: Ranger
Issue Type: Bug
Components: plugins
Affects Versions: 1.1.0
Reporter: Qiang Zhang
Assignee: Qiang Zhang
Fix For: 1.1.0
*** CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
/plugin-kylin/src/test/java/org/apache/ranger/authorization/kylin/authorizer/RangerAdminClientImpl.java:
68 in
org.apache.ranger.authorization.kylin.authorizer.RangerAdminClientImpl.getServicePoliciesIfUpdated(long,
long)()
62 }
63
64 java.nio.file.Path cachePath = FileSystems.getDefault()
65 .getPath(basedir, "/src/test/resources/" +
cacheFilename);
66 byte[] cacheBytes = Files.readAllBytes(cachePath);
67
>>> CID 175091: FindBugs: Internationalization (FB.DM_DEFAULT_ENCODING)
>>> Found reliance on default encoding: new String(byte[]).
68 return gson.fromJson(new String(cacheBytes),
ServicePolicies.class);
69 }
70
71 @Override
72 public void grantAccess(GrantRevokeRequest request) throws Exception
{
73
To view the defects in Coverity Scan visit,
https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRZSbhom32dlDl11LWEm9nX11zsOWMf5dv3Q9Mogo-2FGua3FsLRTFft2V-2FOFC9o0P2e0-3D_d04ZgyDzSjlwpjXIuOFYDNE6R93Lal83MDClQK32PZsnIXFWgRi957MYBuy-2FlDkytlroFFT4DodK8yWwhtaHLaX8VDTgQexZ1KpM2ghdONIK2s05PzHFJPHt35agqZ9nM-2FaTS-2BwGKR0yiHd9VqwUDlZAGDFlrUyAnUh6f6i-2B3anlkbZqOzVnGOBWkfRi-2BewYxNrjphgpV2suFoBTWVzO0g-3D-3D
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (RANGER-1809) Write install guide for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-1809. - Resolution: Fixed Fix Version/s: 1.1.0 master > Write install guide for RANGER-1672 > --- > > Key: RANGER-1809 > URL: https://issues.apache.org/jira/browse/RANGER-1809 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: 1.0.0, master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Fix For: master, 1.1.0 > > > Write install guide for RANGER-1672 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2052) The Ranger admin supports high availability
Qiang Zhang created RANGER-2052: --- Summary: The Ranger admin supports high availability Key: RANGER-2052 URL: https://issues.apache.org/jira/browse/RANGER-2052 Project: Ranger Issue Type: New Feature Components: admin Reporter: Qiang Zhang Assignee: Qiang Zhang In real business environment, such as banks application and so on, we should use other Ranger service to continuely supply service once a Ranger service exits abnormally. We call the feature as high availability. The Ranger high availability includes: 1. The Ranger admin is high availability; 2. The mysql service that saves meta data is high availability. For the Ranger admin high availability our scheme is as following: 1. Add a configuration item in plugin. The configuration item includes two the address of the Ranger admin service. 2. The plugin refreshed policy from other Ranger admin service once it refresh policy from a Ranger admin service fail. For the mysql service that saves meta data admin high availability, our scheme is as following: 1. Add a configuration item in the Ranger admin. The configuration item includes two the address of the mysql service. 2. Build two jdbc connection pools. The other will be used once a jdbc connection fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2044) Fix execute sql failure in db_setup.py file of the admin.
[ https://issues.apache.org/jira/browse/RANGER-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2044. - Resolution: Fixed Fix Version/s: 1.1.0 master > Fix execute sql failure in db_setup.py file of the admin. > - > > Key: RANGER-2044 > URL: https://issues.apache.org/jira/browse/RANGER-2044 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.0.0, master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Fix For: master, 1.1.0 > > Attachments: > 0001-RANGER-2044-Fix-execute-sql-failure-in-db_setup.py-f.patch > > > Fix execute sql failure in db_setup.py file. > The reason is that the contributors copied the code and did not modify the > related variables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2042) Fix error variable and remove invalid import package in upgrade_admin.py file of the security admin.
[ https://issues.apache.org/jira/browse/RANGER-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2042. - Resolution: Fixed Fix Version/s: 1.0.1 1.1.0 master > Fix error variable and remove invalid import package in upgrade_admin.py file > of the security admin. > > > Key: RANGER-2042 > URL: https://issues.apache.org/jira/browse/RANGER-2042 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.0.0, master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: master, 1.1.0, 1.0.1 > > Attachments: > 0001-RANGER-2042-Fix-error-variable-and-remove-invalid-im.patch > > > Fix error variable and remove invalid import package in upgrade_admin.py file > of the security admin. > The variable tokens was written token. So the script was executed fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2033) Add hbase policy and click the 'Test Connection' button. Connection Failed.
[ https://issues.apache.org/jira/browse/RANGER-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang resolved RANGER-2033. - Resolution: Fixed > Add hbase policy and click the 'Test Connection' button. Connection Failed. > --- > > Key: RANGER-2033 > URL: https://issues.apache.org/jira/browse/RANGER-2033 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 1.0.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: master, 1.1.0 > > Attachments: > 0001-RANGER-2033-Add-hbase-policy-and-click-the-Test-Conn.patch > > > Clone the lastest code from > https://git-wip-us.apache.org/repos/asf/ranger.git. Build the source and > install Ranger. Then do as follows: > 1. Add hbase policy; > 2. Input right parameter; > 3. Click the 'Test Connection' button. > The error information is as follows: > Unable to retrieve any files using given parameters, You can still save the > repository and start creating policies, but you would not be able to use > autocomplete for resource names. Check ranger_admin.log for more info. > java.lang.NoClassDefFoundError: > org/apache/hadoop/hbase/ZooKeeperConnectionException. > org/apache/hadoop/hbase/ZooKeeperConnectionException. > org.apache.hadoop.hbase.ZooKeeperConnectionException. > The reason for the error is that the hbase-client-1.2.6.jar file loss under > ./ews/webapp/WEB-INF/classes/ranger-plugins/hbase directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1636#comment-1636 ] Qiang Zhang edited comment on RANGER-1808 at 3/28/18 8:49 AM: -- Review Requet: https://reviews.apache.org/r/66079/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12916570/0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch] Reference: [kylin-policies.json|https://issues.apache.org/jira/secure/attachment/12914646/kylin-policies.json] was (Author: zhangqiang2): Review Requet: https://reviews.apache.org/r/66079/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12915083/0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch] Reference: [kylin-policies.json|https://issues.apache.org/jira/secure/attachment/12914646/kylin-policies.json] > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1808: Attachment: (was: 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch) > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1808: Attachment: 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2044) Fix execute sql failure in db_setup.py file of the admin.
[ https://issues.apache.org/jira/browse/RANGER-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2044: Attachment: 0001-RANGER-2044-Fix-execute-sql-failure-in-db_setup.py-f.patch > Fix execute sql failure in db_setup.py file of the admin. > - > > Key: RANGER-2044 > URL: https://issues.apache.org/jira/browse/RANGER-2044 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.0.0, master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Attachments: > 0001-RANGER-2044-Fix-execute-sql-failure-in-db_setup.py-f.patch > > > Fix execute sql failure in db_setup.py file. > The reason is that the contributors copied the code and did not modify the > related variables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2044) Fix execute sql failure in db_setup.py file of the admin.
[ https://issues.apache.org/jira/browse/RANGER-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2044: Summary: Fix execute sql failure in db_setup.py file of the admin. (was: Fix execute sql failure in db_setup.py file.) > Fix execute sql failure in db_setup.py file of the admin. > - > > Key: RANGER-2044 > URL: https://issues.apache.org/jira/browse/RANGER-2044 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.0.0, master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > > Fix execute sql failure in db_setup.py file. > The reason is that the contributors copied the code and did not modify the > related variables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2044) Fix execute sql failure in db_setup.py file.
Qiang Zhang created RANGER-2044: --- Summary: Fix execute sql failure in db_setup.py file. Key: RANGER-2044 URL: https://issues.apache.org/jira/browse/RANGER-2044 Project: Ranger Issue Type: Bug Components: admin Affects Versions: 1.0.0, master, 1.1.0 Reporter: Qiang Zhang Assignee: Qiang Zhang Fix execute sql failure in db_setup.py file. The reason is that the contributors copied the code and did not modify the related variables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2042) Fix error variable and remove invalid import package in upgrade_admin.py file of the security admin.
[ https://issues.apache.org/jira/browse/RANGER-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2042: Attachment: 0001-RANGER-2042-Fix-error-variable-and-remove-invalid-im.patch > Fix error variable and remove invalid import package in upgrade_admin.py file > of the security admin. > > > Key: RANGER-2042 > URL: https://issues.apache.org/jira/browse/RANGER-2042 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.0.0, master, 1.1.0, 1.0.1 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Attachments: > 0001-RANGER-2042-Fix-error-variable-and-remove-invalid-im.patch > > > Fix error variable and remove invalid import package in upgrade_admin.py file > of the security admin. > The variable tokens was written token. So the script was executed fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2042) Fix error variable and remove invalid import package in upgrade_admin.py file of the security admin.
Qiang Zhang created RANGER-2042: --- Summary: Fix error variable and remove invalid import package in upgrade_admin.py file of the security admin. Key: RANGER-2042 URL: https://issues.apache.org/jira/browse/RANGER-2042 Project: Ranger Issue Type: Bug Components: admin Affects Versions: 1.0.0, master, 1.1.0, 1.0.1 Reporter: Qiang Zhang Assignee: Qiang Zhang Fix error variable and remove invalid import package in upgrade_admin.py file of the security admin. The variable tokens was written token. So the script was executed fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-1989) Ranger Admin may fail to start after enabling SSLHadoop GroupMapping
[
https://issues.apache.org/jira/browse/RANGER-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang reassigned RANGER-1989:
---
Assignee: Qiang Zhang
> Ranger Admin may fail to start after enabling SSLHadoop GroupMapping
>
>
> Key: RANGER-1989
> URL: https://issues.apache.org/jira/browse/RANGER-1989
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.7.0
>Reporter: Hajime Osako
>Assignee: Qiang Zhang
>Priority: Major
>
> Opening this Jira to request Ranger community to add commons-io-x.y.jar in
> the classpath with default installation.
> Thank you.
>
> After setting up Hadoop GroupMapping with
> "hadoop.security.group.mapping.provider.ldap.bind.password.*file*" for HDFS
> and YARN, Ranger Admin may fail to start if SSL is enabled.
> The following error is in catalina.out:
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/io/Charsets
> at
> org.apache.hadoop.security.LdapGroupsMapping.extractPassword(LdapGroupsMapping.java:667)
> at
> org.apache.hadoop.security.LdapGroupsMapping.setConf(LdapGroupsMapping.java:588)
> ...{noformat}
> This is because, in LdapGroupsMapping.setConf() above, if ".bind.password" is
> empty, it tries to extract from ".bind.password.file" with extractPassword(),
> and inside of this method org.apache.commons.io.Charsets is used, however,
> commons-io.jar doesn't seem to be in the Ranger Admin classpath.
> h3. WORKAROUND:
> An example of workarounds is simply copying commons-io-x.y.jar, like below:
> cp -p /usr/hdp/current/ranger-admin/ews/webapp/WEB-INF/lib/commons-io-2.4.jar
> /usr/hdp/current/ranger-admin/ews/lib/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (RANGER-1992) Ranger HDFS PermissionCheck logic issue
[
https://issues.apache.org/jira/browse/RANGER-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang reassigned RANGER-1992:
---
Assignee: Qiang Zhang
> Ranger HDFS PermissionCheck logic issue
> ---
>
> Key: RANGER-1992
> URL: https://issues.apache.org/jira/browse/RANGER-1992
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: chuanjie.duan
>Assignee: Qiang Zhang
>Priority: Major
>
> user 'cim_beta_db' create directory in user 'dataswap' parent directory as
> below
> hdfs dfs -ls /user/hive/warehouse/dataswap.db/
> drwxrwx- -- - cim_beta_db dataswap 0 2018-02-26 09:49
> /user/hive/warehouse/dataswap.db/test
> drwxrwx- -- - dataswap dataswap
> /user/hive/warehouse/dataswap.db
> drwxrwx- -x- dataswap dataswap /user/hive/warehouse
>
> I add hdfs policy, user 'cim_beta_db' ‘’execute‘’ permission to path
> /user/hive/warehouse/dataswap.db
>
> hdfs dfs -ls /user/hive/warehouse/dataswap.db/test
> ls: Permission denied: user=cim_beta_db, access=EXECUTE,
> inode="/user/hive/warehouse/dataswap.db/test":{color:#ff}dataswap{color}:dataswap:drwxrwx---
>
> there are two issue.
> # exception information should
> inode="/user/hive/warehouse/dataswap.db":{color:#ff}dataswap{color}:dataswap:drwxrwx---
> # policy cannot combine use, policy match failed, would check default
> permission only, even if parent directory give a 'execute' permission
>
> // checkINodeAccess
> if(authzStatus == AuthzStatus.ALLOW && access != null && inode != null) {
> LOG.info("checkINodeAccess");
> INodeAttributes inodeAttribs = inodeAttrs.length > 0 ?
> inodeAttrs[inodeAttrs.length - 1] : null;
> authzStatus = isAccessAllowed(inode, inodeAttribs, access, user, groups,
> plugin, auditHandler);
> if (authzStatus == AuthzStatus.NOT_DETERMINED) {
> authzStatus = {color:#FF}checkDefaultEnforcer{color}(fsOwner,
> superGroup, ugi, inodeAttrs, inodes,
> pathByNameArr, snapshotId, path, ancestorIndex, doCheckOwner,
> FsAction.NONE, FsAction.NONE, access, FsAction.NONE, ignoreEmptyDir,
> isTraverseOnlyCheck, ancestor, parent, inode, auditHandler);
> }
> }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (RANGER-2034) When ranger.ks.masterkey.password mismatch with DB store hash it outputs into catalina.out
[
https://issues.apache.org/jira/browse/RANGER-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang reassigned RANGER-2034:
---
Assignee: Qiang Zhang
> When ranger.ks.masterkey.password mismatch with DB store hash it outputs into
> catalina.out
> --
>
> Key: RANGER-2034
> URL: https://issues.apache.org/jira/browse/RANGER-2034
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.2
> Environment: HDP-2.6.3 - Apache Ranger 0.7.0
>Reporter: Ernani Pereira de Mattos Junior
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: easyfix
> Fix For: 1.1.0
>
>
> After unsuccessful migration of Ranger KMS from DB to HSM, the
> ranger.ks.masterkey.password mismatched and thrown the following stack trace;
>
> {code:java}
> java.io.IOException: Keystore was tampered with, or password was incorrect
> at
> org.apache.hadoop.crypto.key.RangerKeyStore.engineLoad(RangerKeyStore.java:393)
>
> at
> org.apache.hadoop.crypto.key.RangerKeyStoreProvider.loadKeys(RangerKeyStoreProvider.java:151)
>
> at
> org.apache.hadoop.crypto.key.RangerKeyStoreProvider.reloadKeys(RangerKeyStoreProvider.java:382)
>
> at
> org.apache.hadoop.crypto.key.RangerKeyStoreProvider.(RangerKeyStoreProvider.java:111)
>
> at
> org.apache.hadoop.crypto.key.RangerKeyStoreProvider$Factory.createProvider(RangerKeyStoreProvider.java:399)
>
> at
> org.apache.hadoop.crypto.key.KeyProviderFactory.get(KeyProviderFactory.java:95)
>
> at
> org.apache.hadoop.crypto.key.kms.server.KMSWebApp.contextInitialized(KMSWebApp.java:177)
>
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5110)
>
> at
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5633)
>
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1694)
>
> at
> org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1684)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.security.UnrecoverableKeyException: Password verification
> failed
> at
> org.apache.hadoop.crypto.key.RangerKeyStore.engineLoad(RangerKeyStore.java:391)
>
> ... 15 more
> ERROR: Hadoop KMS could not be started
> {code}
>
>
> The problem that I am bringing to your attention is clearly this is an
> Application Exception. This exception is being output to catalina.out, and
> the kms.log does not indicate any trace of what happen, even with DEBUG
> enabled.
> My request is to copy or redirect this Application UnrecoverableKeyException
> to the configured Application logging, in this case the kms.log.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2033) Add hbase policy and click the 'Test Connection' button. Connection Failed.
[ https://issues.apache.org/jira/browse/RANGER-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-2033: Attachment: 0001-RANGER-2033-Add-hbase-policy-and-click-the-Test-Conn.patch > Add hbase policy and click the 'Test Connection' button. Connection Failed. > --- > > Key: RANGER-2033 > URL: https://issues.apache.org/jira/browse/RANGER-2033 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 1.0.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: patch > Fix For: master, 1.1.0 > > Attachments: > 0001-RANGER-2033-Add-hbase-policy-and-click-the-Test-Conn.patch > > > Clone the lastest code from > https://git-wip-us.apache.org/repos/asf/ranger.git. Build the source and > install Ranger. Then do as follows: > 1. Add hbase policy; > 2. Input right parameter; > 3. Click the 'Test Connection' button. > The error information is as follows: > Unable to retrieve any files using given parameters, You can still save the > repository and start creating policies, but you would not be able to use > autocomplete for resource names. Check ranger_admin.log for more info. > java.lang.NoClassDefFoundError: > org/apache/hadoop/hbase/ZooKeeperConnectionException. > org/apache/hadoop/hbase/ZooKeeperConnectionException. > org.apache.hadoop.hbase.ZooKeeperConnectionException. > The reason for the error is that the hbase-client-1.2.6.jar file loss under > ./ews/webapp/WEB-INF/classes/ranger-plugins/hbase directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2033) Add hbase policy and click the 'Test Connection' button. Connection Failed.
Qiang Zhang created RANGER-2033: --- Summary: Add hbase policy and click the 'Test Connection' button. Connection Failed. Key: RANGER-2033 URL: https://issues.apache.org/jira/browse/RANGER-2033 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 1.0.0 Reporter: Qiang Zhang Assignee: Qiang Zhang Fix For: master, 1.1.0 Clone the lastest code from https://git-wip-us.apache.org/repos/asf/ranger.git. Build the source and install Ranger. Then do as follows: 1. Add hbase policy; 2. Input right parameter; 3. Click the 'Test Connection' button. The error information is as follows: Unable to retrieve any files using given parameters, You can still save the repository and start creating policies, but you would not be able to use autocomplete for resource names. Check ranger_admin.log for more info. java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/ZooKeeperConnectionException. org/apache/hadoop/hbase/ZooKeeperConnectionException. org.apache.hadoop.hbase.ZooKeeperConnectionException. The reason for the error is that the hbase-client-1.2.6.jar file loss under ./ews/webapp/WEB-INF/classes/ranger-plugins/hbase directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1636#comment-1636 ] Qiang Zhang edited comment on RANGER-1808 at 3/19/18 3:33 AM: -- Review Requet: https://reviews.apache.org/r/66079/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12915083/0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch] Reference: [kylin-policies.json|https://issues.apache.org/jira/secure/attachment/12914646/kylin-policies.json] was (Author: zhangqiang2): Review Requet: https://reviews.apache.org/r/66079/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12914645/0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch] Reference: [kylin-policies.json|https://issues.apache.org/jira/secure/attachment/12914646/kylin-policies.json] > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1808: Attachment: 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1808: Attachment: (was: 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch) > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
