[jira] [Commented] (RANGER-1830) Write unit test for RANGER-1810
[ https://issues.apache.org/jira/browse/RANGER-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241618#comment-16241618 ] Qiang Zhang commented on RANGER-1830: - Review Requet: https://reviews.apache.org/r/63608/ Solution patch, please see attachment: [patch|https://issues.apache.org/jira/secure/attachment/12896349/0001-RANGER-1830-Write-unit-test-for-RANGER-1810-sqoop-pl.patch] Reference: [sqoop-policies.jpg|https://issues.apache.org/jira/secure/attachment/12896352/sqoop-policies.jpg] [sqoop-policies.json|https://issues.apache.org/jira/secure/attachment/12896350/sqoop-policies.json] > Write unit test for RANGER-1810 > --- > > Key: RANGER-1830 > URL: https://issues.apache.org/jira/browse/RANGER-1830 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: 1.0.0, master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: newbie, patch > Attachments: > 0001-RANGER-1830-Write-unit-test-for-RANGER-1810-sqoop-pl.patch, > sqoop-policies.jpg, sqoop-policies.json > > > Write unit test for RANGER-1810 sqoop plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1830) Write unit test for RANGER-1810
[ https://issues.apache.org/jira/browse/RANGER-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1830: Attachment: sqoop-policies.jpg > Write unit test for RANGER-1810 > --- > > Key: RANGER-1830 > URL: https://issues.apache.org/jira/browse/RANGER-1830 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: 1.0.0, master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: newbie, patch > Attachments: > 0001-RANGER-1830-Write-unit-test-for-RANGER-1810-sqoop-pl.patch, > sqoop-policies.jpg, sqoop-policies.json > > > Write unit test for RANGER-1810 sqoop plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1830) Write unit test for RANGER-1810
[ https://issues.apache.org/jira/browse/RANGER-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1830: Attachment: sqoop-policies.json > Write unit test for RANGER-1810 > --- > > Key: RANGER-1830 > URL: https://issues.apache.org/jira/browse/RANGER-1830 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: 1.0.0, master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: newbie, patch > Attachments: > 0001-RANGER-1830-Write-unit-test-for-RANGER-1810-sqoop-pl.patch, > sqoop-policies.json > > > Write unit test for RANGER-1810 sqoop plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1830) Write unit test for RANGER-1810
[ https://issues.apache.org/jira/browse/RANGER-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1830: Attachment: 0001-RANGER-1830-Write-unit-test-for-RANGER-1810-sqoop-pl.patch > Write unit test for RANGER-1810 > --- > > Key: RANGER-1830 > URL: https://issues.apache.org/jira/browse/RANGER-1830 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: 1.0.0, master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: newbie, patch > Attachments: > 0001-RANGER-1830-Write-unit-test-for-RANGER-1810-sqoop-pl.patch > > > Write unit test for RANGER-1810 sqoop plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Review Request 63608: RANGER-1830:Write unit test for RANGER-1810 sqoop plugin
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63608/ --- Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, sam rome, Venkat Ranganathan, and Velmurugan Periasamy. Bugs: RANGER-1830 https://issues.apache.org/jira/browse/RANGER-1830 Repository: ranger Description --- Write unit test for RANGER-1810 sqoop plugin Diffs - plugin-sqoop/pom.xml 0c52e66 plugin-sqoop/src/test/java/org/apache/ranger/authorization/sqoop/authorizer/RangerAdminClientImpl.java PRE-CREATION plugin-sqoop/src/test/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizerTest.java PRE-CREATION plugin-sqoop/src/test/resources/log4j.properties PRE-CREATION plugin-sqoop/src/test/resources/ranger-sqoop-security.xml PRE-CREATION plugin-sqoop/src/test/resources/sqoop-policies.json PRE-CREATION plugin-sqoop/src/test/resources/sqoop.properties PRE-CREATION plugin-sqoop/src/test/resources/sqoop_bootstrap.properties PRE-CREATION Diff: https://reviews.apache.org/r/63608/diff/1/ Testing --- Tested Thanks, Qiang Zhang
[jira] [Updated] (RANGER-1830) Write unit test for RANGER-1810
[ https://issues.apache.org/jira/browse/RANGER-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qiang Zhang updated RANGER-1830: Description: Write unit test for RANGER-1810 sqoop plugin > Write unit test for RANGER-1810 > --- > > Key: RANGER-1830 > URL: https://issues.apache.org/jira/browse/RANGER-1830 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: 1.0.0, master >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Minor > Labels: newbie, patch > > Write unit test for RANGER-1810 sqoop plugin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Review Request 63607: RANGER-1875:The installer of the kms should not repeatedly add a user to the same group.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63607/ --- Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan Neethiraj, Velmurugan Periasamy, and Qiang Zhang. Bugs: RANGER-1875 https://issues.apache.org/jira/browse/RANGER-1875 Repository: ranger Description --- The installer of the kms will repeatedly add a user to the same group if the user exists and the user belongs to the group. The installer should check whether the user belongs to the group before adding user to group. Diffs - kms/scripts/setup.sh 6e4b7e22 Diff: https://reviews.apache.org/r/63607/diff/1/ Testing --- Thanks, pengjianhua
[jira] [Updated] (RANGER-1875) The installer of the kms should not repeatedly add a user to the same group.
[ https://issues.apache.org/jira/browse/RANGER-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua updated RANGER-1875: - Attachment: 0001-RANGER-1875-The-installer-of-the-kms-should-not-repe.patch > The installer of the kms should not repeatedly add a user to the same group. > > > Key: RANGER-1875 > URL: https://issues.apache.org/jira/browse/RANGER-1875 > Project: Ranger > Issue Type: Bug > Components: kms >Affects Versions: 0.7.1 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Labels: patch > Attachments: > 0001-RANGER-1875-The-installer-of-the-kms-should-not-repe.patch > > > The installer of the kms will repeatedly add a user to the same group if the > user exists and the user belongs to the group. The installer should check > whether the user belongs to the group before adding user to group. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1875) The installer of the kms should not repeatedly add a user to the same group.
peng.jianhua created RANGER-1875: Summary: The installer of the kms should not repeatedly add a user to the same group. Key: RANGER-1875 URL: https://issues.apache.org/jira/browse/RANGER-1875 Project: Ranger Issue Type: Bug Components: kms Affects Versions: 0.7.1 Reporter: peng.jianhua Assignee: peng.jianhua Priority: Minor The installer of the kms will repeatedly add a user to the same group if the user exists and the user belongs to the group. The installer should check whether the user belongs to the group before adding user to group. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (RANGER-1871) Optimize code and keep log output consistent in some classes
[ https://issues.apache.org/jira/browse/RANGER-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] peng.jianhua resolved RANGER-1871. -- Resolution: Not A Bug > Optimize code and keep log output consistent in some classes > > > Key: RANGER-1871 > URL: https://issues.apache.org/jira/browse/RANGER-1871 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: peng.jianhua >Assignee: peng.jianhua > Labels: patch > > We should optimize code and keep log output consistent in following class. > org.apache.ranger.services.hdfs.client.HdfsClient > org.apache.ranger.services.hive.client.HiveClient > org.apache.ranger.authentication.unix.jaas.RemoteUnixLoginModule > org.apache.ranger.services.knox.client.KnoxClient -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1874) ranger README.txt should be add tar and sqoop-plugin desc
[ https://issues.apache.org/jira/browse/RANGER-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangYuan updated RANGER-1874: - Description: ranger README.txt should be add tar and sqoop-plugin desc ==add tar desc: ranger--atlas-plugin.tar.gz ranger--ranger-tools.tar.gz ranger--sqoop-plugin.tar.gz ranger--tagsync.tar.gz ==add pulgin desc: (h) Sqoop plugin needs to be installed on Sqoop2 hosts was: ranger README.txt should be add tar and sqoop-plugin desc ==add tar desc: ranger--atlas-plugin.tar.gz ranger--ranger-tools.tar.gz ranger--sqoop-plugin.tar.gz ranger--tagsync.tar.gz ==add pulgin desc: (i) SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts > ranger README.txt should be add tar and sqoop-plugin desc > - > > Key: RANGER-1874 > URL: https://issues.apache.org/jira/browse/RANGER-1874 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: WangYuan >Assignee: WangYuan >Priority: Minor > Attachments: > 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch, > 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch > > > ranger README.txt should be add tar and sqoop-plugin desc > ==add tar desc: >ranger--atlas-plugin.tar.gz >ranger--ranger-tools.tar.gz >ranger--sqoop-plugin.tar.gz >ranger--tagsync.tar.gz > ==add pulgin desc: > (h) Sqoop plugin needs to be installed on Sqoop2 hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1874) ranger README.txt should be add tar and sqoop-plugin desc
[ https://issues.apache.org/jira/browse/RANGER-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangYuan updated RANGER-1874: - Attachment: 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch > ranger README.txt should be add tar and sqoop-plugin desc > - > > Key: RANGER-1874 > URL: https://issues.apache.org/jira/browse/RANGER-1874 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: WangYuan >Assignee: WangYuan >Priority: Minor > Attachments: > 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch, > 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch > > > ranger README.txt should be add tar and sqoop-plugin desc > ==add tar desc: >ranger--atlas-plugin.tar.gz >ranger--ranger-tools.tar.gz >ranger--sqoop-plugin.tar.gz >ranger--tagsync.tar.gz > ==add pulgin desc: > (h) Sqoop plugin needs to be installed on Sqoop2 hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Review Request 63578: anger README.txt should be add tar and sqoop-plugin desc
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63578/ --- (Updated εδΈζ 7, 2017, 1:26 a.m.) Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, Velmurugan Periasamy, and Qiang Zhang. Bugs: RANGER-1874 https://issues.apache.org/jira/browse/RANGER-1874 Repository: ranger Description --- ranger README.txt should be add tar and sqoop-plugin desc ==add tar desc: ranger--atlas-plugin.tar.gz ranger--ranger-tools.tar.gz ranger--sqoop-plugin.tar.gz ranger--tagsync.tar.gz ==add pulgin desc: SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts Diffs (updated) - README.txt 536d3986 Diff: https://reviews.apache.org/r/63578/diff/2/ Changes: https://reviews.apache.org/r/63578/diff/1-2/ Testing --- Thanks, wang yuan
[jira] [Commented] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.
[ https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241180#comment-16241180 ] Don Bosco Durai commented on RANGER-1644: - [~ekovacs], thanks for clarifying. A couple of more questions: 1. Does this affect how user passwords are encrypted and stored in Ranger DB? 2. If so, what happens to those users who are already in the Ranger system? 3. Are there any other locations we might have issues decrypting/validating the password? Thanks Bosco > Change the default Crypt Algo to use stronger cryptographic algo. > -- > > Key: RANGER-1644 > URL: https://issues.apache.org/jira/browse/RANGER-1644 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Selvamohan Neethiraj >Assignee: Endre Kovacs >Priority: Critical > Attachments: > 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch > > > Change the default crypt algorithm to use a stronger cipher algorithm -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Review Request 63461: Good coding practice in Ranger recommended by static code analysis
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63461/#review190192 --- Ship it! Ship It! - Alejandro Fernandez On Nov. 1, 2017, 12:16 p.m., Nikhil P wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/63461/ > --- > > (Updated Nov. 1, 2017, 12:16 p.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay > Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan > Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-1868 > https://issues.apache.org/jira/browse/RANGER-1868 > > > Repository: ranger > > > Description > --- > > Good coding practice in Ranger recommended by static code analysis > > > Diffs > - > > > agents-common/src/main/java/org/apache/hadoop/security/SecureClientLogin.java > e4d6a39 > > storm-agent/src/main/java/org/apache/ranger/services/storm/client/StormClient.java > 46e370e > > > Diff: https://reviews.apache.org/r/63461/diff/1/ > > > Testing > --- > > Verified CRUD of services,policies,users. > Verified if ranger plugins are communating properly. > > > Thanks, > > Nikhil P > >
[jira] [Updated] (RANGER-1700) gaiandb: Integrate with ranger libraries - plugin builds, initializes
[ https://issues.apache.org/jira/browse/RANGER-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Wang updated RANGER-1700: - Attachment: 0001-adding-gaianDB-connection-and-resource-manage.patch This patch adds GaianClient, GaianConnectionMgr, GaianResourceMgr, which take care of GaianDB connection and getting resources from GaianDB. Currently it is initial code, needs more testing and polish. And currently by running addGaianService.sh, the GaianDB plugin can be registered successfully and shown on Ranger Admin UI > gaiandb: Integrate with ranger libraries - plugin builds, initializes > - > > Key: RANGER-1700 > URL: https://issues.apache.org/jira/browse/RANGER-1700 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Reporter: Nigel Jones > Attachments: 0001-adding-gaianDB-connection-and-resource-manage.patch > > > Get the plugin to a state where it will initialize with a simple > configuration and can be deployed to gaianDB. It may not actually action any > policies at this state -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Review Request 63461: Good coding practice in Ranger recommended by static code analysis
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63461/#review190178 --- Ship it! Ship It! - Velmurugan Periasamy On Nov. 1, 2017, 12:16 p.m., Nikhil P wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/63461/ > --- > > (Updated Nov. 1, 2017, 12:16 p.m.) > > > Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay > Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan > Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy. > > > Bugs: RANGER-1868 > https://issues.apache.org/jira/browse/RANGER-1868 > > > Repository: ranger > > > Description > --- > > Good coding practice in Ranger recommended by static code analysis > > > Diffs > - > > > agents-common/src/main/java/org/apache/hadoop/security/SecureClientLogin.java > e4d6a39 > > storm-agent/src/main/java/org/apache/ranger/services/storm/client/StormClient.java > 46e370e > > > Diff: https://reviews.apache.org/r/63461/diff/1/ > > > Testing > --- > > Verified CRUD of services,policies,users. > Verified if ranger plugins are communating properly. > > > Thanks, > > Nikhil P > >
Re: Review Request 63578: anger README.txt should be add tar and sqoop-plugin desc
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63578/#review190167 --- Change (i) to (h). Also it should be "needs" and not "need" (also change this for the Yarn plugin). - Colm O hEigeartaigh On Nov. 6, 2017, 12:11 p.m., wang yuan wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/63578/ > --- > > (Updated Nov. 6, 2017, 12:11 p.m.) > > > Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O > hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, > Selvamohan Neethiraj, Velmurugan Periasamy, and Qiang Zhang. > > > Bugs: RANGER-1874 > https://issues.apache.org/jira/browse/RANGER-1874 > > > Repository: ranger > > > Description > --- > > ranger README.txt should be add tar and sqoop-plugin desc > ==add tar desc: > ranger--atlas-plugin.tar.gz > ranger--ranger-tools.tar.gz > ranger--sqoop-plugin.tar.gz > ranger--tagsync.tar.gz > ==add pulgin desc: > SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts > > > Diffs > - > > README.txt 536d3986 > > > Diff: https://reviews.apache.org/r/63578/diff/1/ > > > Testing > --- > > > Thanks, > > wang yuan > >
[jira] [Resolved] (RANGER-1870) Modify the logic for buildUnixUserList and parseMembers method in UnixUserGroupBuilder class
[
https://issues.apache.org/jira/browse/RANGER-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang resolved RANGER-1870.
-
Resolution: Fixed
Fix Version/s: master
1.0.0
> Modify the logic for buildUnixUserList and parseMembers method in
> UnixUserGroupBuilder class
> --
>
> Key: RANGER-1870
> URL: https://issues.apache.org/jira/browse/RANGER-1870
> Project: Ranger
> Issue Type: Bug
> Components: usersync
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Fix For: 1.0.0, master
>
>
> Modify the logic for buildUnixUserList and parseMembers method in
> UnixUserGroupBuilder class
> 1.In the buildUnixUserList method:
> int len = tokens.length;
> if (len = 3) groupId = tokens [3]; case ArrayIndexOutOfBoundsException.
> 2.Another similar error in the parseMembers method:
> String[] tokens = line.split(":");
> if (tokens.length = 2) String groupId = tokens [2]; case
> ArrayIndexOutOfBoundsException.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (RANGER-1874) ranger README.txt should be add tar and sqoop-plugin desc
[ https://issues.apache.org/jira/browse/RANGER-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangYuan updated RANGER-1874: - Attachment: 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch > ranger README.txt should be add tar and sqoop-plugin desc > - > > Key: RANGER-1874 > URL: https://issues.apache.org/jira/browse/RANGER-1874 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: WangYuan >Assignee: WangYuan >Priority: Minor > Attachments: > 0001-RANGER-1874-ranger-README.txt-should-be-add-tar-and-.patch > > > ranger README.txt should be add tar and sqoop-plugin desc > ==add tar desc: >ranger--atlas-plugin.tar.gz >ranger--ranger-tools.tar.gz >ranger--sqoop-plugin.tar.gz >ranger--tagsync.tar.gz > ==add pulgin desc: > (i) SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1874) ranger README.txt should be add tar and sqoop-plugin desc
[ https://issues.apache.org/jira/browse/RANGER-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] WangYuan updated RANGER-1874: - Summary: ranger README.txt should be add tar and sqoop-plugin desc (was: ranger README.txt should be add tar and sqoop-plugin infomation) > ranger README.txt should be add tar and sqoop-plugin desc > - > > Key: RANGER-1874 > URL: https://issues.apache.org/jira/browse/RANGER-1874 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: WangYuan >Assignee: WangYuan >Priority: Minor > > ranger README.txt should be add tar and sqoop-plugin desc > ==add tar desc: >ranger--atlas-plugin.tar.gz >ranger--ranger-tools.tar.gz >ranger--sqoop-plugin.tar.gz >ranger--tagsync.tar.gz > ==add pulgin desc: > (i) SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Review Request 63578: anger README.txt should be add tar and sqoop-plugin desc
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63578/ --- Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, Velmurugan Periasamy, and Qiang Zhang. Bugs: RANGER-1874 https://issues.apache.org/jira/browse/RANGER-1874 Repository: ranger Description --- ranger README.txt should be add tar and sqoop-plugin desc ==add tar desc: ranger--atlas-plugin.tar.gz ranger--ranger-tools.tar.gz ranger--sqoop-plugin.tar.gz ranger--tagsync.tar.gz ==add pulgin desc: SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts Diffs - README.txt 536d3986 Diff: https://reviews.apache.org/r/63578/diff/1/ Testing --- Thanks, wang yuan
[jira] [Created] (RANGER-1874) ranger README.txt should be add tar and sqoop-plugin infomation
WangYuan created RANGER-1874: Summary: ranger README.txt should be add tar and sqoop-plugin infomation Key: RANGER-1874 URL: https://issues.apache.org/jira/browse/RANGER-1874 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: WangYuan Assignee: WangYuan Priority: Minor ranger README.txt should be add tar and sqoop-plugin desc ==add tar desc: ranger--atlas-plugin.tar.gz ranger--ranger-tools.tar.gz ranger--sqoop-plugin.tar.gz ranger--tagsync.tar.gz ==add pulgin desc: (i) SQOOP plugin need to be installed on SQOOP2 Resource Manager hosts -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.
[
https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240145#comment-16240145
]
Endre Kovacs edited comment on RANGER-1644 at 11/6/17 11:30 AM:
hi [~bosco]
this patch is created in a way that:
* when *new service* is *created* through the Ranger UI
* when an *existing service* is *updated*
then it will use the new updated algo from:
`ranger-admin-default-site.xml`
{code}
ranger.password.encryption.algorithm
PBEWITHHMACSHA512ANDAES_128
{code}
first decoding value with the previously configured algorithm, then encoding
and sanity checking with the new algorithm.
* in such cases, when the service is not created or updated, just simply
*READ*, it does not update the encrypt algo. it uses the stored, coma separated
algorithm information for encrypting and decrypting. If no such coma separated
algorithm info is present, then encryption&decryption is done with
`PasswordUtils.DEFAULT_CRYPT_ALGO = "PBEWithMD5AndDES";` which did not change.
Making it backward compatible.
Please let me know if you have any specific concerns / use cases / steps in
mind needing to be tested on a live cluster.
Best regards,
Endre
was (Author: andrewsmith87):
hi [~bosco]
this patch is created in a way that:
* when *new service* is *created* through the Ranger UI
* when an *existing service* is *updated*
then it will use the new updated algo from:
`ranger-admin-default-site.xml`
{code}
ranger.password.encryption.algorithm
PBEWITHHMACSHA512ANDAES_128
{code}
first decoding value with the previously configured algorithm, then encoding
and sanity checking with the new algorithm.
* in such cases, when the service is not created or updated, just simply
*READ*, it does not update the encrypt algo. it uses the stored, coma separated
algorithm information for encrypting and decrypting. If no such coma separated
algorithm info is present, then encryption&decryption is done with
`PasswordUtils.DEFAULT_CRYPT_ALGO = "PBEWithMD5AndDES";` which did not change.
Making it backward compatible.
Please let me know if you have any specific use cases / steps in mind needing
to be tested on a live cluster.
Best regards,
Endre
> Change the default Crypt Algo to use stronger cryptographic algo.
> --
>
> Key: RANGER-1644
> URL: https://issues.apache.org/jira/browse/RANGER-1644
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Selvamohan Neethiraj
>Assignee: Endre Kovacs
>Priority: Critical
> Attachments:
> 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch
>
>
> Change the default crypt algorithm to use a stronger cipher algorithm
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.
[
https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240145#comment-16240145
]
Endre Kovacs edited comment on RANGER-1644 at 11/6/17 11:08 AM:
hi [~bosco]
this patch is created in a way that:
* when *new service* is *created* through the Ranger UI
* when an *existing service* is *updated*
then it will use the new updated algo from:
`ranger-admin-default-site.xml`
{code}
ranger.password.encryption.algorithm
PBEWITHHMACSHA512ANDAES_128
{code}
first decoding value with the previously configured algorithm, then encoding
and sanity checking with the new algorithm.
* in such cases, when the service is not created or updated, just simply
*READ*, it does not update the encrypt algo. it uses the stored, coma separated
algorithm information for encrypting and decrypting. If no such coma separated
algorithm info is present, then encryption&decryption is done with
`PasswordUtils.DEFAULT_CRYPT_ALGO = "PBEWithMD5AndDES";` which did not change.
Making it backward compatible.
Please let me know if you have any specific use cases / steps in mind needing
to be tested on a live cluster.
Best regards,
Endre
was (Author: andrewsmith87):
hi [~bosco]
this patch is created in a way that:
* when *new service* is *created* through the Ranger UI
* when an *existing service* is *updated*
then it will use the new updated algo from:
`ranger-admin-default-site.xml`
{code}
ranger.password.encryption.algorithm
PBEWITHHMACSHA512ANDAES_128
{code}
first decoding value with the previously configured algorithm, then encoding
and sanity checking with the new algorithm.
* in such cases, when the service is not created or updated, just simply
*READ*, it does not update the encrypt algo. it uses the stored, coma separated
algorithm information for encrypting and decrypting. If no such coma separated
algorithm info is present, then encryption&decryption is done with
`PasswordUtils.DEFAULT_CRYPT_ALGO = "PBEWithMD5AndDES";` which did not change.
Making it backward compatible.
Please let me know if you have any specific use cases / steps in mind needing
to be tested on a live cluster.
Best regards,
Endre
> Change the default Crypt Algo to use stronger cryptographic algo.
> --
>
> Key: RANGER-1644
> URL: https://issues.apache.org/jira/browse/RANGER-1644
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Selvamohan Neethiraj
>Assignee: Endre Kovacs
>Priority: Critical
> Attachments:
> 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch
>
>
> Change the default crypt algorithm to use a stronger cipher algorithm
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (RANGER-1644) Change the default Crypt Algo to use stronger cryptographic algo.
[
https://issues.apache.org/jira/browse/RANGER-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240145#comment-16240145
]
Endre Kovacs commented on RANGER-1644:
--
hi [~bosco]
this patch is created in a way that:
* when *new service* is *created* through the Ranger UI
* when an *existing service* is *updated*
then it will use the new updated algo from:
`ranger-admin-default-site.xml`
{code}
ranger.password.encryption.algorithm
PBEWITHHMACSHA512ANDAES_128
{code}
first decoding value with the previously configured algorithm, then encoding
and sanity checking with the new algorithm.
* in such cases, when the service is not created or updated, just simply
*READ*, it does not update the encrypt algo. it uses the stored, coma separated
algorithm information for encrypting and decrypting. If no such coma separated
algorithm info is present, then encryption&decryption is done with
`PasswordUtils.DEFAULT_CRYPT_ALGO = "PBEWithMD5AndDES";` which did not change.
Making it backward compatible.
Please let me know if you have any specific use cases / steps in mind needing
to be tested on a live cluster.
Best regards,
Endre
> Change the default Crypt Algo to use stronger cryptographic algo.
> --
>
> Key: RANGER-1644
> URL: https://issues.apache.org/jira/browse/RANGER-1644
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Selvamohan Neethiraj
>Assignee: Endre Kovacs
>Priority: Critical
> Attachments:
> 0001-RANGER-1644-replacing-MD5-DES-with-SHA512-AES128.patch
>
>
> Change the default crypt algorithm to use a stronger cipher algorithm
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Review Request 63575: RANGER-1873: Fix property handling in RangerKMSDB
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63575/ --- Review request for ranger. Bugs: RANGER-1873 https://issues.apache.org/jira/browse/RANGER-1873 Repository: ranger Description --- In RangerKMSDB, the updateDBSSLURL function is never called, because getDBFlavor always return DB_FLAVOR_UNKNOWN, because it tries to read from DB_PROPERTIES, instead of the configuration. The DB_PROPERTIES only contains - at that point values for the keys: PROPERTY_PREFIX+DB_DIALECT,PROPERTY_PREFIX+DB_DRIVER,PROPERTY_PREFIX+DB_URL. Fixed this issue, moved the DB_PROPERTIES static variable to an instance variable, and simplified the string manipulation code a bit Diffs - kms/src/main/java/org/apache/hadoop/crypto/key/RangerKMSDB.java 649da30c5 Diff: https://reviews.apache.org/r/63575/diff/1/ Testing --- https://travis-ci.org/gzsombor/ranger/builds/297898874 Thanks, Zsombor Gegesy
[jira] [Updated] (RANGER-1873) Fix property handling in RangerKMSDB
[ https://issues.apache.org/jira/browse/RANGER-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zsombor Gegesy updated RANGER-1873: --- Attachment: RANGER-1873.patch > Fix property handling in RangerKMSDB > - > > Key: RANGER-1873 > URL: https://issues.apache.org/jira/browse/RANGER-1873 > Project: Ranger > Issue Type: Bug > Components: kms >Affects Versions: 0.7.1 >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy > Labels: kms > Attachments: RANGER-1873.patch > > > In RangerKMSDB, the updateDBSSLURL function is never called, because > getDBFlavor always return DB_FLAVOR_UNKNOWN, because it tries to read from > DB_PROPERTIES, instead of the configuration. The DB_PROPERTIES only contains > - at that point values for the keys: > PROPERTY_PREFIX+DB_DIALECT,PROPERTY_PREFIX+DB_DRIVER,PROPERTY_PREFIX+DB_URL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1873) Fix property handling in RangerKMSDB
Zsombor Gegesy created RANGER-1873: -- Summary: Fix property handling in RangerKMSDB Key: RANGER-1873 URL: https://issues.apache.org/jira/browse/RANGER-1873 Project: Ranger Issue Type: Bug Components: kms Affects Versions: 0.7.1 Reporter: Zsombor Gegesy Assignee: Zsombor Gegesy In RangerKMSDB, the updateDBSSLURL function is never called, because getDBFlavor always return DB_FLAVOR_UNKNOWN, because it tries to read from DB_PROPERTIES, instead of the configuration. The DB_PROPERTIES only contains - at that point values for the keys: PROPERTY_PREFIX+DB_DIALECT,PROPERTY_PREFIX+DB_DRIVER,PROPERTY_PREFIX+DB_URL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
