[jira] [Commented] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776884#comment-16776884 ] Gautam Borad commented on RANGER-2331: -- Patch committed for master branch Link: https://github.com/apache/ranger/commit/fc4289222718d0c02ba65a994299d45ea1f4d97b > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.patch, RANGER-2331-02.patch, > RANGER-2331-ranger-0.7-01.patch, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776873#comment-16776873 ] Gautam Borad commented on RANGER-2331: -- Patch committed for ranger-0.7 branch Link: https://github.com/apache/ranger/commit/df1eb588465b4a8d31cfb04f5a62d8f9444e9cec > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.patch, RANGER-2331-ranger-0.7-01.patch, > RANGER-2331-ranger-0.7.patch, RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-2331: - Attachment: RANGER-2331-02.patch > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.patch, RANGER-2331-02.patch, > RANGER-2331-ranger-0.7-01.patch, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768046#comment-16768046 ] Gautam Borad commented on RANGER-2331: -- Review Request for master branch : [https://reviews.apache.org/r/69984/] Review Request for ranger-0.7 branch : https://reviews.apache.org/r/69985/ > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.patch, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-2331: - Attachment: (was: RANGER-2331-01.path) > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.patch, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-2331: - Attachment: RANGER-2331-01.patch > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.patch, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2331) Ranger-KMS - KeySecure HSM Integration
[ https://issues.apache.org/jira/browse/RANGER-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-2331: - Attachment: RANGER-2331-01.path > Ranger-KMS - KeySecure HSM Integration > -- > > Key: RANGER-2331 > URL: https://issues.apache.org/jira/browse/RANGER-2331 > Project: Ranger > Issue Type: New Feature > Components: kms, Ranger >Reporter: Velmurugan Periasamy >Assignee: Gautam Borad >Priority: Major > Fix For: 0.7.2, 2.0.0 > > Attachments: RANGER-2331-01.path, RANGER-2331-ranger-0.7.patch, > RANGER-2331.patch > > > This JIRA is to support Ranger KMS integration with Gemalto KeySecure HSM to > manage master keys. > Similar to Luna integration - https://issues.apache.org/jira/browse/RANGER-868 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1326) Fix remaining licensing issues
[ https://issues.apache.org/jira/browse/RANGER-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391047#comment-16391047 ] Gautam Borad commented on RANGER-1326: -- +1 > Fix remaining licensing issues > -- > > Key: RANGER-1326 > URL: https://issues.apache.org/jira/browse/RANGER-1326 > Project: Ranger > Issue Type: Bug >Affects Versions: 0.6.2 >Reporter: Colm O hEigeartaigh >Assignee: Velmurugan Periasamy >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1326-Removed-dependency-from-NOTICE-as-it-is-.patch > > > We need to fix the remaining licensing issues as raised by Jusin: > For items not fixed please see [1][2][3]. > Also note that with json2.js license it seems a little unclear to me and may > be under the JSON license. It does have “public domain” in the code so it may > be OK, it still however needs to be added to LICENSE. Just be careful as the > JSON license no longer allowed in Apache software and it is considered > category X. [4] In this case you do have a few months grace to remove this > [5] but you need to call it out in NOTICE and it still needs to be removed by > end of April. [5] > 1. > https://lists.apache.org/thread.html/6949e2f048b07478c861a675ad8e98d750e0f786b272a6afc69df78e@%3Cgeneral.incubator.apache.org%3E > 2. > https://lists.apache.org/thread.html/9552c63b71a38ed75cd252463e788408aa4a9a05abeba36168df5a12@%3Cgeneral.incubator.apache.org%3E > 3. > https://lists.apache.org/thread.html/de169a09f7527fbc3549518f0227ba40ee8524c6e60ba8105d82479b@%3Cgeneral.incubator.apache.org%3E > 4. https://www.apache.org/legal/resolved#category-x > 5. > https://lists.apache.org/thread.html/bb18f942ce7eb83c11438303c818b885810fb76385979490366720d5@%3Clegal-discuss.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1651) Improve Ranger and Ranger KMS REST Api documentation
[ https://issues.apache.org/jira/browse/RANGER-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16167795#comment-16167795 ] Gautam Borad commented on RANGER-1651: -- +1 for new patch. > Improve Ranger and Ranger KMS REST Api documentation > > > Key: RANGER-1651 > URL: https://issues.apache.org/jira/browse/RANGER-1651 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Mehul Parikh >Assignee: Mehul Parikh > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1651.2.patch, RANGER-1651.patch, > RANGER-1651-ranger-0.7.patch > > > Improve the existing Ranger and Ranger KMS API documentation that is > published on the Apache Ranger website (http://ranger.apache.org/) > This can be automated using some tool like Enunciate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16081936#comment-16081936 ] Gautam Borad commented on RANGER-1638: -- Committed to Master : https://github.com/apache/ranger/commit/8d32649f935fc0ade400db94c20d909fa1f767e1 Committed to ranger-0.7 : https://github.com/apache/ranger/commit/98da92207ba78a640d4ddce8f02cb2de8657040f > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Gautam Borad > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1638.1.patch, RANGER-1638.patch > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1667) Range Audit Access Logs is struck
[ https://issues.apache.org/jira/browse/RANGER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062872#comment-16062872 ] Gautam Borad commented on RANGER-1667: -- Audit to DB has been deprecated since release 0.6. Please consider Audit to Solr as an option. More information here : https://cwiki.apache.org/confluence/display/RANGER/DB+Audit+Removal > Range Audit Access Logs is struck > - > > Key: RANGER-1667 > URL: https://issues.apache.org/jira/browse/RANGER-1667 > Project: Ranger > Issue Type: Bug > Components: admin, audit >Affects Versions: 0.7.1 > Environment: Centos 7.0 > 16 GB Memory > 8 CPU >Reporter: Joseph Aliase > Attachments: screenshot-1.png > > > I'm using Apache Ranger to authorize access to Kafka Topic. Kafka Plugin and > Admin are in sync and are working fine. > I'm using mysql for storing Audit logs. Access Log tab is frozen and it > doesnt show any rows. Other Tab's are working and I'm able to filter records. > PFA Access log frozen screen -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-1638: - Attachment: RANGER-1638.1.patch > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Gautam Borad > Fix For: 1.0.0, 0.7.2 > > Attachments: RANGER-1638.1.patch, RANGER-1638.patch > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1638) Improve the password validation from Ranger API
[ https://issues.apache.org/jira/browse/RANGER-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-1638: - Fix Version/s: 1.0.0 > Improve the password validation from Ranger API > --- > > Key: RANGER-1638 > URL: https://issues.apache.org/jira/browse/RANGER-1638 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Gautam Borad > Fix For: 1.0.0, 0.7.1 > > > Ranger API should apply password validation in sync with what UI is applying > for all users. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1620) Fix kafka-ranger-env.sh script to not throw error when it is sourced from bash
[
https://issues.apache.org/jira/browse/RANGER-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gautam Borad updated RANGER-1620:
-
Attachment: RANGER-1620.patch
> Fix kafka-ranger-env.sh script to not throw error when it is sourced from bash
> --
>
> Key: RANGER-1620
> URL: https://issues.apache.org/jira/browse/RANGER-1620
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Gautam Borad
>Assignee: Gautam Borad
>Priority: Critical
> Fix For: 0.7.0, 1.0.0
>
> Attachments: RANGER-1620.patch
>
>
> Current implementation of kafka-ranger-env.sh relies on the $0 bash variable,
> However, when the script is sourced using the {{source}} or the {{.}}
> command, the {{$0}} variable expands to text {{-bash}} which gives an error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1620) Fix kafka-ranger-env.sh script to not throw error when it is sourced from bash
[
https://issues.apache.org/jira/browse/RANGER-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gautam Borad updated RANGER-1620:
-
Priority: Critical (was: Major)
> Fix kafka-ranger-env.sh script to not throw error when it is sourced from bash
> --
>
> Key: RANGER-1620
> URL: https://issues.apache.org/jira/browse/RANGER-1620
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Gautam Borad
>Assignee: Gautam Borad
>Priority: Critical
> Fix For: 0.7.0, 1.0.0
>
>
> Current implementation of kafka-ranger-env.sh relies on the $0 bash variable,
> However, when the script is sourced using the {{source}} or the {{.}}
> command, the {{$0}} variable expands to text {{-bash}} which gives an error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RANGER-1620) Fix kafka-ranger-env.sh script to not throw error when it is sourced from bash
Gautam Borad created RANGER-1620:
Summary: Fix kafka-ranger-env.sh script to not throw error when it
is sourced from bash
Key: RANGER-1620
URL: https://issues.apache.org/jira/browse/RANGER-1620
Project: Ranger
Issue Type: Bug
Components: plugins
Reporter: Gautam Borad
Assignee: Gautam Borad
Fix For: 1.0.0, 0.7.0
Current implementation of kafka-ranger-env.sh relies on the $0 bash variable,
However, when the script is sourced using the {{source}} or the {{.}} command,
the {{$0}} variable expands to text {{-bash}} which gives an error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1602) Include / Exclude toggle not working for same level resources
[ https://issues.apache.org/jira/browse/RANGER-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16020976#comment-16020976 ] Gautam Borad commented on RANGER-1602: -- Committed to master : 56e28489607eb7e7da68a76edf98c5f8ca78eb6c Committed to ranger-0.7 : 69bb80df27bc49e1544a3b3bbe87c3d00cd921da > Include / Exclude toggle not working for same level resources > - > > Key: RANGER-1602 > URL: https://issues.apache.org/jira/browse/RANGER-1602 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger >Affects Versions: 0.7.0, 1.0.0 >Reporter: Gautam Borad >Assignee: Nitin Galave > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1602.patch > > > Include / Exclude toggle is shown on the UI even if one of the resource at > the same level contains excludesSupported flag as true in service def. > Ideally, it should honor the flag and show the toggle only if its set to true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1602) Include / Exclude toggle not working for same level resources
Gautam Borad created RANGER-1602: Summary: Include / Exclude toggle not working for same level resources Key: RANGER-1602 URL: https://issues.apache.org/jira/browse/RANGER-1602 Project: Ranger Issue Type: Bug Components: admin, Ranger Affects Versions: 0.7.0, 1.0.0 Reporter: Gautam Borad Assignee: Gautam Borad Include / Exclude toggle is shown on the UI even if one of the resource at the same level contains isExclude as true. Ideally, it should honor the flag and shoe the toggle only if its set to true. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1583) Test connections are failing for plugins after upgrade
[ https://issues.apache.org/jira/browse/RANGER-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017648#comment-16017648 ] Gautam Borad commented on RANGER-1583: -- Committed to master : 69204867d4bba0d7094ea5963971baf403af2fe4 Committed to ranger-0.7 : 0765c215d6fa1a70734a32e6f37f6fc77dc718d5 > Test connections are failing for plugins after upgrade > -- > > Key: RANGER-1583 > URL: https://issues.apache.org/jira/browse/RANGER-1583 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1583-07-01.patch, RANGER-1583-07.patch, > RANGER-1583-master-01.patch, RANGER-1583-master.patch > > > After upgrade from ranger-0.6 to ranger-0.7 all test connections are failing > for plugins. > Below error is shown in xa_portal.log: > ERROR org.apache.ranger.plugin.util.PasswordUtils (PasswordUtils.java:129) - > Unable to decrypt password due to error -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1579) WASB policy edit page is not opening
[ https://issues.apache.org/jira/browse/RANGER-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16010643#comment-16010643 ] Gautam Borad commented on RANGER-1579: -- Committed to master : e05276f05a615590f7bb737bd6bcc8e4763822f1 Committed to ranger-0.7 : e281a2e50d1def8e1773c5463709be03921aa94a > WASB policy edit page is not opening > > > Key: RANGER-1579 > URL: https://issues.apache.org/jira/browse/RANGER-1579 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Deepak Sharma >Assignee: Nitin Galave > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1579.patch > > > Policy Edit page is not opening for wasb(works for other repos), it keeps on > loading for long time but does not open. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1576) Show attribute values to tags column in audit log
[ https://issues.apache.org/jira/browse/RANGER-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-1576: - Attachment: RANGER-1576.patch > Show attribute values to tags column in audit log > - > > Key: RANGER-1576 > URL: https://issues.apache.org/jira/browse/RANGER-1576 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger >Affects Versions: 0.7.0 >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1576.patch > > > Currently in the access audit log record (Audit Menu-> admin tab), the tags > column is populated when the accessed resource has any tags associated with > it. > However, if the tag has any attributes, their values are not shown in the > audit log record. As authorization decision may be based on the > attribute-value(s) as well as tag-type (such as in the case of expiry_date > attribute’s value for EXPIRES_ON tag-type), they too need to be populated and > displayed on audit log record. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1576) Show attribute values to tags column in audit log
Gautam Borad created RANGER-1576: Summary: Show attribute values to tags column in audit log Key: RANGER-1576 URL: https://issues.apache.org/jira/browse/RANGER-1576 Project: Ranger Issue Type: Bug Components: admin, Ranger Affects Versions: 0.7.0 Reporter: Gautam Borad Assignee: Gautam Borad Fix For: 1.0.0, 0.7.1 Currently in the access audit log record (Audit Menu-> admin tab), the tags column is populated when the accessed resource has any tags associated with it. However, if the tag has any attributes, their values are not shown in the audit log record. As authorization decision may be based on the attribute-value(s) as well as tag-type (such as in the case of expiry_date attribute’s value for EXPIRES_ON tag-type), they too need to be populated and displayed on audit log record. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1571) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/RANGER-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007824#comment-16007824 ] Gautam Borad commented on RANGER-1571: -- Committed to master : fa38ed737d8696519d39b0cc53c128141e29edc6 Committed to ranger-0.7 : 3999d5b6a2f93ef72bdf1deea45d7abbe4268652 > Code Improvement To Follow Best Practices > - > > Key: RANGER-1571 > URL: https://issues.apache.org/jira/browse/RANGER-1571 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1571-07-01.patch, RANGER-1571-07-02.patch, > RANGER-1571-master-01.patch, RANGER-1571-master.patch > > > Code Improvement To Follow Best Practices -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1571) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/RANGER-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-1571: - Fix Version/s: 1.0.0 > Code Improvement To Follow Best Practices > - > > Key: RANGER-1571 > URL: https://issues.apache.org/jira/browse/RANGER-1571 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1571-07-01.patch, RANGER-1571-07-02.patch, > RANGER-1571-master-01.patch, RANGER-1571-master.patch > > > Code Improvement To Follow Best Practices -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1560) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/RANGER-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998708#comment-15998708 ] Gautam Borad commented on RANGER-1560: -- Committed to master : a5ab9a34d3c8a66d3119f9bd552bd35ce68b03ed Committed to ranger-0.7 : ca69b58ca9b634dcc90b49fe6f4a580df3c49213 > Code Improvement To Follow Best Practices > - > > Key: RANGER-1560 > URL: https://issues.apache.org/jira/browse/RANGER-1560 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1560.patch > > > Code Improvement To Follow Best Practices -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1500) Add support to exclude/disable SSL protocols.
[ https://issues.apache.org/jira/browse/RANGER-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15998686#comment-15998686 ] Gautam Borad commented on RANGER-1500: -- Committed to master : 58116e0118909b7ef495c3721575ba866a919c3a Committed to ranger-0.7 : 07fc810408d1b5772925357413795dd7d93bdc8e > Add support to exclude/disable SSL protocols. > - > > Key: RANGER-1500 > URL: https://issues.apache.org/jira/browse/RANGER-1500 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Ayub Pathan >Assignee: bhavik patel >Priority: Critical > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1500-1.patch, RANGER-1500-2.patch, > RANGER-1500-3.patch, RANGER-1500.patch > > > Add support to disable/exclude weaker SSL protocols like TLSv1, TLSv1.1 for > ranger. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1556) Provide keyadmin user with privileges to read ranger kms audits
[ https://issues.apache.org/jira/browse/RANGER-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15996028#comment-15996028 ] Gautam Borad commented on RANGER-1556: -- Committed to master : 93ccc5237384a378416489d68e9e7d4234d07f73 Committed to ranger-0.7 : 6fa851ddc6f83bc056829f9b5738726573262028 > Provide keyadmin user with privileges to read ranger kms audits > --- > > Key: RANGER-1556 > URL: https://issues.apache.org/jira/browse/RANGER-1556 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1556.patch > > > *Actual* : > To provide keyadmin user privileges for Ranger KMS Audit folder, manually > policy need to be created giving all access rights in HDFS repo > *Expected* : > Need to handle default policy creation in HDFS for keyadmin user to have > access to all access rights for Ranger KMS Audits folder (/ranger/audit/kms) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1548) Display detailed error messages in Ranger for Audit store issues
[ https://issues.apache.org/jira/browse/RANGER-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991385#comment-15991385 ] Gautam Borad commented on RANGER-1548: -- Committed to master : 501e05f1a1225dfbcc16bf4d2c0d86e55d4a928e Committed to ranger-0.7 : ce7169f8f62fbadba516ea7af89a9ab9f9b5fb76 > Display detailed error messages in Ranger for Audit store issues > > > Key: RANGER-1548 > URL: https://issues.apache.org/jira/browse/RANGER-1548 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 0.7.1 >Reporter: Ankita Sinha >Assignee: Ankita Sinha > Fix For: 0.7.1 > > Attachments: RANGER-1548_07.patch, RANGER-1548_master.patch > > > Actual : > When audit store is not configured properly or if audit store is down, Ranger > UI shows > "Unable to connect to Audit store !!" > Expected : > To show more informative message if audit store has some issues. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1499) Upgrade Tomcat version
[ https://issues.apache.org/jira/browse/RANGER-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987531#comment-15987531 ] Gautam Borad commented on RANGER-1499: -- Committed to master: 45f30336fd885a7bda5bb3700821ea237fb13b31 Committed to 0.7: 0a5265a54a0c12aaa5c399a3c3153b5e794783b7 > Upgrade Tomcat version > -- > > Key: RANGER-1499 > URL: https://issues.apache.org/jira/browse/RANGER-1499 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy >Assignee: bhavik patel > Fix For: 0.6.4, 1.0.0, 0.7.1 > > Attachments: RANGER-1499.patch > > > Tomcat version used by Ranger & Ranger KMS is 7.0.68. > Need to upgrade to 7.0.73 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1546) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/RANGER-1546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-1546: - Fix Version/s: 1.0.0 > Code Improvement To Follow Best Practices > - > > Key: RANGER-1546 > URL: https://issues.apache.org/jira/browse/RANGER-1546 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1546-07-1.patch, RANGER-1546-master-1.patch, > RANGER-1546-master.patch > > > Code improvement to follow best practices. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1522) Update consolidated db schema script for SQLServer DB flavor to reduce execution time
[ https://issues.apache.org/jira/browse/RANGER-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987454#comment-15987454 ] Gautam Borad commented on RANGER-1522: -- Committed to master : c01d01f54622286de7ef17b302ae0a734664a9d1 Committed to 0.7 : a7bb8e732b840bbcdcf48c49b21a8e17ea97293c > Update consolidated db schema script for SQLServer DB flavor to reduce > execution time > - > > Key: RANGER-1522 > URL: https://issues.apache.org/jira/browse/RANGER-1522 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0, 0.7.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal > Fix For: 1.0.0, 0.7.1 > > Attachments: RANGER-1522-0.7-branch.patch, > RANGER-1522-master-branch.patch > > > Modify the schema file to exclude the GO statements or use the minimum number > of GO Statement. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1471) Remember filters on all tabs of Ranger Audits page
[ https://issues.apache.org/jira/browse/RANGER-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad updated RANGER-1471: - Fix Version/s: master > Remember filters on all tabs of Ranger Audits page > -- > > Key: RANGER-1471 > URL: https://issues.apache.org/jira/browse/RANGER-1471 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 0.7.1 >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: master, 0.7.1 > > Attachments: RANGER-1471-07.patch, RANGER-1471-1.patch, > RANGER-1471-2.patch, RANGER-1471-master.patch, RANGER-1471.patch > > > Currently, when we apply filter for anything in Ranger Audit page for any of > the tabs. It resets the filter on change of tab or if we move to any other > page in Ranger. > Planning to add feature of remembering latest filters on all Tabs of Audits > page. That will help users to stay focused on what they are looking for in > audits tab and users will not have to apply for filters again and again to > check audit events of a particular service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1471) Remember filters on all tabs of Ranger Audits page
[ https://issues.apache.org/jira/browse/RANGER-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15987094#comment-15987094 ] Gautam Borad commented on RANGER-1471: -- Committed to master : c7784876173bc9eafd1c47def7f45bad3b5010ac Committed to 0.7 : 1a461ecfb7b4c0e8005d06e8d9d2dfb7c65a1497 > Remember filters on all tabs of Ranger Audits page > -- > > Key: RANGER-1471 > URL: https://issues.apache.org/jira/browse/RANGER-1471 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 0.7.1 >Reporter: bhavik patel >Assignee: bhavik patel > Fix For: 0.7.1 > > Attachments: RANGER-1471-07.patch, RANGER-1471-1.patch, > RANGER-1471-2.patch, RANGER-1471-master.patch, RANGER-1471.patch > > > Currently, when we apply filter for anything in Ranger Audit page for any of > the tabs. It resets the filter on change of tab or if we move to any other > page in Ranger. > Planning to add feature of remembering latest filters on all Tabs of Audits > page. That will help users to stay focused on what they are looking for in > audits tab and users will not have to apply for filters again and again to > check audit events of a particular service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1544) Misaligned input boxes and cleanup on Reports Search
[ https://issues.apache.org/jira/browse/RANGER-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985325#comment-15985325 ] Gautam Borad commented on RANGER-1544: -- [~arpsian] Ranger follows Review Request based method for contributions. Please follow the steps listed [here|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55151244] (specifically the 8th point) to file a Review Request. Thanks. > Misaligned input boxes and cleanup on Reports Search > > > Key: RANGER-1544 > URL: https://issues.apache.org/jira/browse/RANGER-1544 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Anna Shaverdian >Assignee: Anna Shaverdian >Priority: Trivial > Labels: newbie, patch > Fix For: 0.7.1 > > Attachments: 0001-RANGER-1544-Misaligned-input-boxes.patch, Screen > Shot 2017-04-25 at 8.58.31 PM.png > > > On the Ranger Admin > User Access Report page, the input boxes for Policy > Type and Resource will overlap the other text boxes when resizing the window. > Also UserAccessLayout_tmpl.html has some typos (ie searchInfoUserAccss) and > needs to reformat the indentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1484) RangerUI: Escape of policy condition text entered in the policy form.
[
https://issues.apache.org/jira/browse/RANGER-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954604#comment-15954604
]
Gautam Borad commented on RANGER-1484:
--
Committed to master: bdf0b61c0f6e109c2f4e0459676dda71f0265aeb
Committed to ranger-0.7 : ba664e1b310ae65b674ff28e0772d208d3b20464
> RangerUI: Escape of policy condition text entered in the policy form.
> -
>
> Key: RANGER-1484
> URL: https://issues.apache.org/jira/browse/RANGER-1484
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.0
>Reporter: Madhan Neethiraj
>Assignee: Nitin Galave
> Fix For: 1.0.0, 0.7.1
>
> Attachments: image001.png, image002.png, RANGER-1484.patch
>
>
> The text entered in policy condition UI comes back with escape characters
> after saving the policy.
> {code}
> For example:
> 1.create policy with policy condition as “tag.attributes['type']=='ccn'” .
> 2.Now open that policy in edit mode you will see policy condition
> becomes "tag.attributes[type]==ccn".
> {code}
> Another issue is that UI displays policy conditions that don’t have any
> value.Only the condition edit popup would list all the conditions; the policy
> view would only list the conditions that have non-empty value.
> See attachments for more info: image001.png, image002.png.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1459) Ranger update policy API is failing on Postgres / Oracle for case sensitive ACLs
[
https://issues.apache.org/jira/browse/RANGER-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15928387#comment-15928387
]
Gautam Borad commented on RANGER-1459:
--
Committed to ranger-0.7 : a44c04e436caadbe391cad957e9f4d70f66eb51e
Committed to master : f310aaf6bb7b81825ce2886ba4f16c13a09c603a
> Ranger update policy API is failing on Postgres / Oracle for case sensitive
> ACLs
>
>
> Key: RANGER-1459
> URL: https://issues.apache.org/jira/browse/RANGER-1459
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.7.0
>Reporter: Mehul Parikh
>Assignee: Gautam Borad
> Fix For: 0.7.1
>
> Attachments: RANGER-1459.patch
>
>
> When user tries to disable a ranger policy via REST API with postgres DB,
> then it gives this error, it works on MySQL though :
> {code}
> {u'msgDesc': u"Create: is not a valid access-type.
> policy='cl1_hive-87808627-ac26-499a-bea8-e99677a41889' service='cl1_hive'",
> u'statusCode': 1}
> {code}
> Mainly : This is a case sensitive issue on postgres / Oracle for ACLs, need
> to keep it consistent for GET and PUT calls for policies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (RANGER-1459) Ranger update policy API is failing on Postgres / Oracle for case sensitive ACLs
[
https://issues.apache.org/jira/browse/RANGER-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gautam Borad reassigned RANGER-1459:
Assignee: Gautam Borad
> Ranger update policy API is failing on Postgres / Oracle for case sensitive
> ACLs
>
>
> Key: RANGER-1459
> URL: https://issues.apache.org/jira/browse/RANGER-1459
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.7.0
>Reporter: Mehul Parikh
>Assignee: Gautam Borad
> Fix For: 0.7.1
>
>
> When user tries to disable a ranger policy via REST API with postgres DB,
> then it gives this error, it works on MySQL though :
> {code}
> {u'msgDesc': u"Create: is not a valid access-type.
> policy='cl1_hive-87808627-ac26-499a-bea8-e99677a41889' service='cl1_hive'",
> u'statusCode': 1}
> {code}
> Mainly : This is a case sensitive issue on postgres / Oracle for ACLs, need
> to keep it consistent for GET and PUT calls for policies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (RANGER-1448) Change of import / export icons on Ranger UI
[ https://issues.apache.org/jira/browse/RANGER-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Borad reassigned RANGER-1448: Assignee: Gautam Borad > Change of import / export icons on Ranger UI > > > Key: RANGER-1448 > URL: https://issues.apache.org/jira/browse/RANGER-1448 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: Mehul Parikh >Assignee: Gautam Borad > Fix For: 0.7.1 > > > To make it more intuitive for end users, need to change icons used for import > / export feature in landing page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1317) There are two defects in install scripts for ranger usersync process
[ https://issues.apache.org/jira/browse/RANGER-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851072#comment-15851072 ] Gautam Borad commented on RANGER-1317: -- [~zhangqiang2], I think my "Ship It" was before the RR was Closed. Anyways, are you planning to provide another patch for this? > There are two defects in install scripts for ranger usersync process > > > Key: RANGER-1317 > URL: https://issues.apache.org/jira/browse/RANGER-1317 > Project: Ranger > Issue Type: Bug > Components: usersync >Reporter: Qiang Zhang >Assignee: Qiang Zhang > Labels: patch > Attachments: > 0001-RANGER-1317-There-are-two-defects-in-install-scripts.patch > > > There are two defects in install scripts for ranger usersync process: > 1. The rangerBaseDirName variable equals to /etc/ranger when we install the > ranger usersync process. So the usersync can only be installed in > /etc/ranger. As a result, the installer can't plan the installation path > according to their needs.In some system environment, it is not reasonable. > There is a configuration attribute to resolve the issue in ranger-admin. > Similarly, the install scripts for ranger usersync process should also > provide configuration attributes to solve this issue. > 2. The usersyncBaseDirName variable equals to usersync. The install program > uses following code to create directorys. > dirList = [ rangerBaseDirName, usersyncBaseDirName, confFolderName, > certFolderName ] > In above list other variables are absolute value of the path, but > usersyncBaseDirName is not. Above list should be modified as following: > dirList = [ rangerBaseDirName, usersyncBaseDirFullName, confFolderName, > certFolderName ] > The following code should be modified also. > fixPermList = [ ".", usersyncBaseDirName, confFolderName, certFolderName ] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
