[jira] [Commented] (RANGER-3695) Ranger Keystore alias should be configurable
[ https://issues.apache.org/jira/browse/RANGER-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751505#comment-17751505 ] Vishal Suvagia commented on RANGER-3695: Hi Team, request to kindly review and help merge the fix. > Ranger Keystore alias should be configurable > > > Key: RANGER-3695 > URL: https://issues.apache.org/jira/browse/RANGER-3695 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3695.patch > > > Ranger keystore alias is currently hard-coded, it should be configurable to > allow user to provide a custom alias -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-2704) Support browser login using kerberized authentication
[ https://issues.apache.org/jira/browse/RANGER-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751473#comment-17751473 ] Vishal Suvagia commented on RANGER-2704: Hi [~dineshkumar-yadav], kindly use [^RANGER-2704.01.patch] to be merged in the required branch as the same has been used to be merged in the master branch. > Support browser login using kerberized authentication > - > > Key: RANGER-2704 > URL: https://issues.apache.org/jira/browse/RANGER-2704 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.3.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Minor > Fix For: 3.0.0, 2.3.0 > > Attachments: RANGER-2704.01.patch, RANGER-2704.02.patch, > RANGER-2704.03.patch, RANGER-2704.patch > > > Need to support browser login using kerberos authentication. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3669) Connection to DB fails for MySQL version above 8.0
[
https://issues.apache.org/jira/browse/RANGER-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522179#comment-17522179
]
Vishal Suvagia commented on RANGER-3669:
[~gomesnayagam] , lets say we have jdbc with some additional flags which we
need to configure, in cases where need to add unicode and character-encoding
support for the jdbc url.
in that case we can set the below in install.properties.
{noformat}
is_override_db_connection_string=true
db_override_connection_string=jdbc:mysql://localhost:3306/test?autoReconnect=trueuseUnicode=truecharacterEncoding=UTF-8
{noformat}
This jdbc url should now be used during setup for communication with DB
> Connection to DB fails for MySQL version above 8.0
> --
>
> Key: RANGER-3669
> URL: https://issues.apache.org/jira/browse/RANGER-3669
> Project: Ranger
> Issue Type: Improvement
> Components: kms
>Affects Versions: 3.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3669.01.patch, RANGER-3669.patch
>
>
> Observed that Ranger KMS DB setup fails when using with MySQL version above
> 8.0.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (RANGER-3669) Connection to DB fails for MySQL version above 8.0
[ https://issues.apache.org/jira/browse/RANGER-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3669: --- Attachment: RANGER-3669.01.patch > Connection to DB fails for MySQL version above 8.0 > -- > > Key: RANGER-3669 > URL: https://issues.apache.org/jira/browse/RANGER-3669 > Project: Ranger > Issue Type: Improvement > Components: kms >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3669.01.patch, RANGER-3669.patch > > > Observed that Ranger KMS DB setup fails when using with MySQL version above > 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3695) Ranger Keystore alias should be configurable
[ https://issues.apache.org/jira/browse/RANGER-3695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3695: --- Attachment: RANGER-3695.patch > Ranger Keystore alias should be configurable > > > Key: RANGER-3695 > URL: https://issues.apache.org/jira/browse/RANGER-3695 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3695.patch > > > Ranger keystore alias is currently hard-coded, it should be configurable to > allow user to provide a custom alias -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3669) Connection to DB fails for MySQL version above 8.0
[ https://issues.apache.org/jira/browse/RANGER-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3669: --- Attachment: RANGER-3669.patch > Connection to DB fails for MySQL version above 8.0 > -- > > Key: RANGER-3669 > URL: https://issues.apache.org/jira/browse/RANGER-3669 > Project: Ranger > Issue Type: Improvement > Components: kms >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3669.patch > > > Observed that Ranger KMS DB setup fails when using with MySQL version above > 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-2704) Support browser login using kerberized authentication
[ https://issues.apache.org/jira/browse/RANGER-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2704: --- Attachment: RANGER-2704.03.patch > Support browser login using kerberized authentication > - > > Key: RANGER-2704 > URL: https://issues.apache.org/jira/browse/RANGER-2704 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Minor > Attachments: RANGER-2704.01.patch, RANGER-2704.02.patch, > RANGER-2704.03.patch, RANGER-2704.patch > > > Need to support browser login using kerberos authentication. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3695) Ranger Keystore alias should be configurable
Vishal Suvagia created RANGER-3695: -- Summary: Ranger Keystore alias should be configurable Key: RANGER-3695 URL: https://issues.apache.org/jira/browse/RANGER-3695 Project: Ranger Issue Type: Improvement Components: admin Affects Versions: 3.0.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Ranger keystore alias is currently hard-coded, it should be configurable to allow user to provide a custom alias -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-2704) Support browser login using kerberized authentication
[ https://issues.apache.org/jira/browse/RANGER-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2704: --- Attachment: RANGER-2704.02.patch > Support browser login using kerberized authentication > - > > Key: RANGER-2704 > URL: https://issues.apache.org/jira/browse/RANGER-2704 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Minor > Attachments: RANGER-2704.01.patch, RANGER-2704.02.patch, > RANGER-2704.patch > > > Need to support browser login using kerberos authentication. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3647) Connection to DB fails for MySQL version above 8.0
[ https://issues.apache.org/jira/browse/RANGER-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3647: --- Fix Version/s: 3.0.0 > Connection to DB fails for MySQL version above 8.0 > -- > > Key: RANGER-3647 > URL: https://issues.apache.org/jira/browse/RANGER-3647 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-3647-01.patch, RANGER-3647.patch > > > Observed that Ranger DB setup fails when using with MySQL version above 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (RANGER-3673) Need to enable cipher configuration for Usersync
[ https://issues.apache.org/jira/browse/RANGER-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved RANGER-3673. Fix Version/s: 3.0.0 2.3.0 Resolution: Fixed Commited to master branch : https://github.com/apache/ranger/commit/f66c5593ba43d7206df3043add90e967a2f5586d ranger-2.3 branch : https://github.com/apache/ranger/commit/55496d57776ed0417d66733780371ac29c26b67c > Need to enable cipher configuration for Usersync > - > > Key: RANGER-3673 > URL: https://issues.apache.org/jira/browse/RANGER-3673 > Project: Ranger > Issue Type: Improvement > Components: usersync >Affects Versions: 3.0.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: RANGER-3673.patch > > > Ranger Usersync supports enabling for TLS, need to enable cipher suite > configuration for same. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3673) Need to enable cipher configuration for Usersync
[ https://issues.apache.org/jira/browse/RANGER-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3673: --- Attachment: RANGER-3673.patch > Need to enable cipher configuration for Usersync > - > > Key: RANGER-3673 > URL: https://issues.apache.org/jira/browse/RANGER-3673 > Project: Ranger > Issue Type: Improvement > Components: usersync >Affects Versions: 3.0.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3673.patch > > > Ranger Usersync supports enabling for TLS, need to enable cipher suite > configuration for same. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3673) Need to enable cipher configuration for Usersync
Vishal Suvagia created RANGER-3673: -- Summary: Need to enable cipher configuration for Usersync Key: RANGER-3673 URL: https://issues.apache.org/jira/browse/RANGER-3673 Project: Ranger Issue Type: Improvement Components: usersync Affects Versions: 2.2.0, 3.0.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Ranger Usersync supports enabling for TLS, need to enable cipher suite configuration for same. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3669) Connection to DB fails for MySQL version above 8.0
Vishal Suvagia created RANGER-3669: -- Summary: Connection to DB fails for MySQL version above 8.0 Key: RANGER-3669 URL: https://issues.apache.org/jira/browse/RANGER-3669 Project: Ranger Issue Type: Improvement Components: kms Affects Versions: 3.0.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Observed that Ranger KMS DB setup fails when using with MySQL version above 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3647) Connection to DB fails for MySQL version above 8.0
[ https://issues.apache.org/jira/browse/RANGER-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3647: --- Attachment: RANGER-3647-01.patch > Connection to DB fails for MySQL version above 8.0 > -- > > Key: RANGER-3647 > URL: https://issues.apache.org/jira/browse/RANGER-3647 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3647-01.patch, RANGER-3647.patch > > > Observed that Ranger DB setup fails when using with MySQL version above 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3647) Connection to DB fails for MySQL version above 8.0
[ https://issues.apache.org/jira/browse/RANGER-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3647: --- Attachment: RANGER-3647.patch > Connection to DB fails for MySQL version above 8.0 > -- > > Key: RANGER-3647 > URL: https://issues.apache.org/jira/browse/RANGER-3647 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3647.patch > > > Observed that Ranger DB setup fails when using with MySQL version above 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-2704) Support browser login using kerberized authentication
[ https://issues.apache.org/jira/browse/RANGER-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2704: --- Attachment: RANGER-2704.01.patch > Support browser login using kerberized authentication > - > > Key: RANGER-2704 > URL: https://issues.apache.org/jira/browse/RANGER-2704 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Minor > Attachments: RANGER-2704.01.patch, RANGER-2704.patch > > > Need to support browser login using kerberos authentication. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (RANGER-3647) Connection to DB fails for MySQL version above 8.0
Vishal Suvagia created RANGER-3647: -- Summary: Connection to DB fails for MySQL version above 8.0 Key: RANGER-3647 URL: https://issues.apache.org/jira/browse/RANGER-3647 Project: Ranger Issue Type: Improvement Components: admin Affects Versions: 3.0.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Observed that Ranger DB setup fails when using with MySQL version above 8.0. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (RANGER-3418) Rotated Ranger admin access logs aren't getting removed
[
https://issues.apache.org/jira/browse/RANGER-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated RANGER-3418:
---
Attachment: RANGER-3418.patch
> Rotated Ranger admin access logs aren't getting removed
> ---
>
> Key: RANGER-3418
> URL: https://issues.apache.org/jira/browse/RANGER-3418
> Project: Ranger
> Issue Type: Improvement
> Components: admin, Ranger
>Affects Versions: 3.0.0, 2.1.1
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3418.patch
>
>
> {color:#172b4d}Ranger admin access logs in the configured log directory
> aren't removed and keeps up utilizing unused space. Need to have access logs
> configurable to have older logs purged.
> {color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3418) Rotated Ranger admin access logs aren't getting removed
Vishal Suvagia created RANGER-3418:
--
Summary: Rotated Ranger admin access logs aren't getting removed
Key: RANGER-3418
URL: https://issues.apache.org/jira/browse/RANGER-3418
Project: Ranger
Issue Type: Improvement
Components: admin, Ranger
Affects Versions: 3.0.0, 2.1.1
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
{color:#172b4d}Ranger admin access logs in the configured log directory aren't
removed and keeps up utilizing unused space. Need to have access logs
configurable to have older logs purged.
{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-3342) Need to make the Ranger embedded server work directory configurable
[ https://issues.apache.org/jira/browse/RANGER-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3342: --- Attachment: RANGER-3342.02.patch > Need to make the Ranger embedded server work directory configurable > --- > > Key: RANGER-3342 > URL: https://issues.apache.org/jira/browse/RANGER-3342 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 2.1.0, 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3342.01.patch, RANGER-3342.02.patch, > RANGER-3342.patch > > > Currently the work directory for Ranger embedded server is not configurable. > Need to make the work directory configurable to a custom location so that > user can customize if required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (RANGER-3342) Need to make the Ranger embedded server work directory configurable
[ https://issues.apache.org/jira/browse/RANGER-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia reopened RANGER-3342: An addendum fix is required, hence re-opening the ticket. > Need to make the Ranger embedded server work directory configurable > --- > > Key: RANGER-3342 > URL: https://issues.apache.org/jira/browse/RANGER-3342 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 2.1.0, 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3342.01.patch, RANGER-3342.patch > > > Currently the work directory for Ranger embedded server is not configurable. > Need to make the work directory configurable to a custom location so that > user can customize if required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3342) Need to make the Ranger embedded server work directory configurable
[ https://issues.apache.org/jira/browse/RANGER-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3342: --- Attachment: RANGER-3342.01.patch > Need to make the Ranger embedded server work directory configurable > --- > > Key: RANGER-3342 > URL: https://issues.apache.org/jira/browse/RANGER-3342 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 2.1.0, 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3342.01.patch, RANGER-3342.patch > > > Currently the work directory for Ranger embedded server is not configurable. > Need to make the work directory configurable to a custom location so that > user can customize if required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3342) Need to make the Ranger embedded server work directory configurable
[ https://issues.apache.org/jira/browse/RANGER-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3342: --- Attachment: RANGER-3342.patch > Need to make the Ranger embedded server work directory configurable > --- > > Key: RANGER-3342 > URL: https://issues.apache.org/jira/browse/RANGER-3342 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 2.1.0, 3.0.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3342.patch > > > Currently the work directory for Ranger embedded server is not configurable. > Need to make the work directory configurable to a custom location so that > user can customize if required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3342) Need to make the Ranger embedded server work directory configurable
Vishal Suvagia created RANGER-3342: -- Summary: Need to make the Ranger embedded server work directory configurable Key: RANGER-3342 URL: https://issues.apache.org/jira/browse/RANGER-3342 Project: Ranger Issue Type: Improvement Components: admin Affects Versions: 2.1.0, 3.0.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Currently the work directory for Ranger embedded server is not configurable. Need to make the work directory configurable to a custom location so that user can customize if required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3287) Implement best practices for logging
[ https://issues.apache.org/jira/browse/RANGER-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3287: --- Attachment: RANGER-3287.01.patch > Implement best practices for logging > > > Key: RANGER-3287 > URL: https://issues.apache.org/jira/browse/RANGER-3287 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3287.01.patch, RANGER-3287.patch > > > Implement best practice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3287) Implement best practices for logging
[ https://issues.apache.org/jira/browse/RANGER-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3287: --- Attachment: RANGER-3287.patch > Implement best practices for logging > > > Key: RANGER-3287 > URL: https://issues.apache.org/jira/browse/RANGER-3287 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Attachments: RANGER-3287.patch > > > Implement best practice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3287) implement best practices for logging
[ https://issues.apache.org/jira/browse/RANGER-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3287: --- Summary: implement best practices for logging (was: implement best practices) > implement best practices for logging > > > Key: RANGER-3287 > URL: https://issues.apache.org/jira/browse/RANGER-3287 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > > Implement best practice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3287) Implement best practices for logging
[ https://issues.apache.org/jira/browse/RANGER-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3287: --- Summary: Implement best practices for logging (was: implement best practices for logging) > Implement best practices for logging > > > Key: RANGER-3287 > URL: https://issues.apache.org/jira/browse/RANGER-3287 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 3.0.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > > Implement best practice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3287) implement best practices
Vishal Suvagia created RANGER-3287: -- Summary: implement best practices Key: RANGER-3287 URL: https://issues.apache.org/jira/browse/RANGER-3287 Project: Ranger Issue Type: Bug Components: admin Affects Versions: 3.0.0, 2.2.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Implement best practice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3275) Need to update solr-config.xml in the ranger-audits collection config-set
[
https://issues.apache.org/jira/browse/RANGER-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated RANGER-3275:
---
Attachment: RANGER-3275.patch
> Need to update solr-config.xml in the ranger-audits collection config-set
> -
>
> Key: RANGER-3275
> URL: https://issues.apache.org/jira/browse/RANGER-3275
> Project: Ranger
> Issue Type: Bug
> Components: admin, Ranger
>Affects Versions: 3.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3275.patch
>
>
> {color:#172b4d}The solrconfig.xml in the config-set for Ranger needs to be
> updated in correct order to use the ttl configuration properly, without which
> the documents will not expire or purge out even after the ttl is set.
> {color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3275) Need to update solr-config.xml in the ranger-audits collection config-set
Vishal Suvagia created RANGER-3275:
--
Summary: Need to update solr-config.xml in the ranger-audits
collection config-set
Key: RANGER-3275
URL: https://issues.apache.org/jira/browse/RANGER-3275
Project: Ranger
Issue Type: Bug
Components: admin, Ranger
Affects Versions: 3.0.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
{color:#172b4d}The solrconfig.xml in the config-set for Ranger needs to be
updated in correct order to use the ttl configuration properly, without which
the documents will not expire or purge out even after the ttl is set.
{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2704) Support browser login using kerberized authentication
[ https://issues.apache.org/jira/browse/RANGER-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2704: --- Attachment: RANGER-2704.patch > Support browser login using kerberized authentication > - > > Key: RANGER-2704 > URL: https://issues.apache.org/jira/browse/RANGER-2704 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Minor > Attachments: RANGER-2704.patch > > > Need to support browser login using kerberos authentication. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3242) Need feature to make the access log file name configurable for user
[ https://issues.apache.org/jira/browse/RANGER-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-3242: --- Attachment: RANGER-3242.patch > Need feature to make the access log file name configurable for user > --- > > Key: RANGER-3242 > URL: https://issues.apache.org/jira/browse/RANGER-3242 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.2.0, 2.1.1, 2.10 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Minor > Attachments: RANGER-3242.patch > > > Currently the access log file name is set as default, need feature to have it > customizable for the user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-3241) Need feature to make the access log file name configurable
[ https://issues.apache.org/jira/browse/RANGER-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved RANGER-3241. Resolution: Won't Fix Fix will be tracked in RANGER-3242. > Need feature to make the access log file name configurable > -- > > Key: RANGER-3241 > URL: https://issues.apache.org/jira/browse/RANGER-3241 > Project: Ranger > Issue Type: Improvement > Components: admin, Ranger >Affects Versions: 2.1.0, 2.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > > Currently the access log file name is set as default, need feature to have it > customizable for the user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3242) Need feature to make the access log file name configurable for user
Vishal Suvagia created RANGER-3242: -- Summary: Need feature to make the access log file name configurable for user Key: RANGER-3242 URL: https://issues.apache.org/jira/browse/RANGER-3242 Project: Ranger Issue Type: Improvement Components: Ranger Affects Versions: 2.2.0, 2.1.1, 2.10 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Currently the access log file name is set as default, need feature to have it customizable for the user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-3241) Need feature to make the access log file name configurable
Vishal Suvagia created RANGER-3241: -- Summary: Need feature to make the access log file name configurable Key: RANGER-3241 URL: https://issues.apache.org/jira/browse/RANGER-3241 Project: Ranger Issue Type: Improvement Components: admin, Ranger Affects Versions: 2.1.0, 2.2.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Currently the access log file name is set as default, need feature to have it customizable for the user. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-3087) Making db_setup.py fool-proof and robust
[
https://issues.apache.org/jira/browse/RANGER-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated RANGER-3087:
---
Attachment: RANGER-3087.patch
> Making db_setup.py fool-proof and robust
>
>
> Key: RANGER-3087
> URL: https://issues.apache.org/jira/browse/RANGER-3087
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Affects Versions: 3.0.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Attachments: RANGER-3087.patch
>
>
> When a user configures a small heap size in install.properties, vm creation
> in db_setup.py fails to apply the java patches with below error.
> {code:none}
> Error occurred during initialization of VM
> Initial heap size set to a larger value than the maximum heap size
> {code}
> Need to make db_setup.py more fool-proof and robust to wrongly configured
> heap-size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-3087) Making db_setup.py fool-proof and robust
Vishal Suvagia created RANGER-3087:
--
Summary: Making db_setup.py fool-proof and robust
Key: RANGER-3087
URL: https://issues.apache.org/jira/browse/RANGER-3087
Project: Ranger
Issue Type: Improvement
Components: Ranger
Affects Versions: 3.0.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
When a user configures a small heap size in install.properties, vm creation in
db_setup.py fails to apply the java patches with below error.
{code:none}
Error occurred during initialization of VM
Initial heap size set to a larger value than the maximum heap size
{code}
Need to make db_setup.py more fool-proof and robust to wrongly configured
heap-size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-2304) Need to add property dfs.permissions.ContentSummary.subAccess when enabling Ranger HDFS plugin manually
[
https://issues.apache.org/jira/browse/RANGER-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated RANGER-2304:
---
Attachment: RANGER-2304.patch
> Need to add property dfs.permissions.ContentSummary.subAccess when enabling
> Ranger HDFS plugin manually
> ---
>
> Key: RANGER-2304
> URL: https://issues.apache.org/jira/browse/RANGER-2304
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 1.2.0
>Reporter: Vishal Suvagia
>Assignee: Vishal Suvagia
>Priority: Major
> Fix For: 2.0.0, 1.2.1
>
> Attachments: RANGER-2304.patch
>
>
> As part of fixes in HDFS-14112 and RANGER-2297, need to update the script
> that handles setting up HDFS authorizer when Ranger HDFS plugin is
> enabled/disabled, as below:
> * set the property {{dfs.permissions.ContentSummary.subAccess}} in
> hdfs-site.xml to ‘true’ when Ranger plugin is enabled.
> * remove the property {{dfs.permissions.ContentSummary.subAccess}} in
> hdfs-site.xml or set to ‘false’ when Ranger plugin is disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2304) Need to add property dfs.permissions.ContentSummary.subAccess when enabling Ranger HDFS plugin manually
Vishal Suvagia created RANGER-2304:
--
Summary: Need to add property
dfs.permissions.ContentSummary.subAccess when enabling Ranger HDFS plugin
manually
Key: RANGER-2304
URL: https://issues.apache.org/jira/browse/RANGER-2304
Project: Ranger
Issue Type: Bug
Components: Ranger
Affects Versions: 1.2.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
Fix For: 2.0.0, 1.2.1
As part of fixes in HDFS-14112 and RANGER-2297, need to update the script that
handles setting up HDFS authorizer when Ranger HDFS plugin is enabled/disabled,
as below:
* set the property {{dfs.permissions.ContentSummary.subAccess}} in
hdfs-site.xml to ‘true’ when Ranger plugin is enabled.
* remove the property {{dfs.permissions.ContentSummary.subAccess}} in
hdfs-site.xml or set to ‘false’ when Ranger plugin is disabled.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16660662#comment-16660662 ] Vishal Suvagia commented on RANGER-2251: Committed in ranger-0.7 branch: https://github.com/apache/ranger/commit/61b69730225687508123dae489b542bc86bfbd60 > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch, RANGER-2251-ranger-0.7.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: RANGER-2251-ranger-0.7.patch > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch, RANGER-2251-ranger-0.7.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2259) Need to provide appropriate permisssions for unix-auth files
[ https://issues.apache.org/jira/browse/RANGER-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2259: --- Attachment: RANGER-2259-master.patch > Need to provide appropriate permisssions for unix-auth files > > > Key: RANGER-2259 > URL: https://issues.apache.org/jira/browse/RANGER-2259 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 1.2.1 > > Attachments: RANGER-2259-master.patch > > > Need to provide appropriate file level permissions for unix-auth files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: RANGER-2251-master.patch > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: (was: WIP-RANGER-2251-master.patch) > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2259) Need to provide appropriate permisssions for unix-auth files
Vishal Suvagia created RANGER-2259: -- Summary: Need to provide appropriate permisssions for unix-auth files Key: RANGER-2259 URL: https://issues.apache.org/jira/browse/RANGER-2259 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.2.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 1.2.1 Need to provide appropriate file level permissions for unix-auth files. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: WIP-RANGER-2251-master.patch > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: WIP-RANGER-2251-master.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: (was: RANGER-2251-master.patch) > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: WIP-RANGER-2251-master.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16653234#comment-16653234 ] Vishal Suvagia commented on RANGER-2251: The attached patch is a work in progress patch. > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
[ https://issues.apache.org/jira/browse/RANGER-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2251: --- Attachment: RANGER-2251-master.patch > Need to provide options for making java heap size memory configurable in > Ranger services > > > Key: RANGER-2251 > URL: https://issues.apache.org/jira/browse/RANGER-2251 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.2.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > Attachments: RANGER-2251-master.patch > > > Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services
Vishal Suvagia created RANGER-2251: -- Summary: Need to provide options for making java heap size memory configurable in Ranger services Key: RANGER-2251 URL: https://issues.apache.org/jira/browse/RANGER-2251 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.2.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.0.0 Need to make java heap size memory configurable for Ranger services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2181) Code Improvement To Follow Best Practices
[ https://issues.apache.org/jira/browse/RANGER-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631924#comment-16631924 ] Vishal Suvagia commented on RANGER-2181: commited to Apache Ranger ranger-0.7 branch: https://github.com/apache/ranger/commit/b050618aeb094234a3fb535eae3a27e0d2724519 > Code Improvement To Follow Best Practices > - > > Key: RANGER-2181 > URL: https://issues.apache.org/jira/browse/RANGER-2181 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 1.1.0 >Reporter: Mehul Parikh >Assignee: bhavik patel >Priority: Major > Fix For: 2.0.0, 1.2.0 > > Attachments: > 0001-RANGER-2181-Code-Improvement-To-Follow-Best-Practice.patch, > RANGER-2181-01.patch, RANGER-2181-02.patch > > > Code Improvement To Follow Best Practices for saving services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2168) Add service admin user through service config
[ https://issues.apache.org/jira/browse/RANGER-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16631921#comment-16631921 ] Vishal Suvagia commented on RANGER-2168: committed to Apache Ranger ranger-0.7 branch: https://github.com/apache/ranger/commit/46c6cf878026b1c2d7e76f838c95733271e1497b > Add service admin user through service config > - > > Key: RANGER-2168 > URL: https://issues.apache.org/jira/browse/RANGER-2168 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 1.0.1, 2.0.0, 1.1.1, 1.2.0 > > Attachments: RANGER-2168-2.patch, RANGER-2168-3.patch > > > Allow admin user to add a custom service config property > 'service.admin.users' through service page. Users listed for this property > should able to create/update/delete the ranger policy of that service. > Currently only user with admin role or a delegated admin user can create the > policy. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2166) A ClassNotFound exception is thrown with atlasrest as a tag source
[ https://issues.apache.org/jira/browse/RANGER-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565476#comment-16565476 ] Vishal Suvagia commented on RANGER-2166: [~abhayk], an addendum patch is required for this change and attached herewith, request to kindly review attached patch and commit the same. > A ClassNotFound exception is thrown with atlasrest as a tag source > -- > > Key: RANGER-2166 > URL: https://issues.apache.org/jira/browse/RANGER-2166 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 1.1.0 >Reporter: Vishal Suvagia >Assignee: Abhay Kulkarni >Priority: Major > Fix For: master > > Attachments: RANGER-2166-Addendum.patch > > > tagsync throws ClassNotFound exception when using REST API to download tags > from Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2166) A ClassNotFound exception is thrown with atlasrest as a tag source
[ https://issues.apache.org/jira/browse/RANGER-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2166: --- Attachment: RANGER-2166-Addendum.patch > A ClassNotFound exception is thrown with atlasrest as a tag source > -- > > Key: RANGER-2166 > URL: https://issues.apache.org/jira/browse/RANGER-2166 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 1.1.0 >Reporter: Vishal Suvagia >Assignee: Abhay Kulkarni >Priority: Major > Fix For: master > > Attachments: RANGER-2166-Addendum.patch > > > tagsync throws ClassNotFound exception when using REST API to download tags > from Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (RANGER-2166) A ClassNotFound exception is thrown with atlasrest as a tag source
[ https://issues.apache.org/jira/browse/RANGER-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia reopened RANGER-2166: Re-opening this as the jackson-module-jaxb-annotations jar is available under com.fasterxml.jackson.module. > A ClassNotFound exception is thrown with atlasrest as a tag source > -- > > Key: RANGER-2166 > URL: https://issues.apache.org/jira/browse/RANGER-2166 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 1.1.0 >Reporter: Vishal Suvagia >Assignee: Abhay Kulkarni >Priority: Major > Fix For: master > > > tagsync throws ClassNotFound exception when using REST API to download tags > from Atlas. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-2155) Ranger Tagsync fails to Authenticate to Atlas when Tag Source set to AtlasRest in Kerberos environment
[ https://issues.apache.org/jira/browse/RANGER-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved RANGER-2155. Resolution: Fixed Resolving the issue as it is now fixed by RANGER-2166, ATLAS-2793, ATLAS-2793. > Ranger Tagsync fails to Authenticate to Atlas when Tag Source set to > AtlasRest in Kerberos environment > -- > > Key: RANGER-2155 > URL: https://issues.apache.org/jira/browse/RANGER-2155 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.0.0 > > > When setting Tag source as Atlas Rest for Ranger Tagsync in a Kerberized > environment, Tagsync fails to authenticate to Atlas throwing 401 Exception in > a Kerberos environment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2155) Ranger Tagsync fails to Authenticate to Atlas when Tag Source set to AtlasRest in Kerberos environment
Vishal Suvagia created RANGER-2155: -- Summary: Ranger Tagsync fails to Authenticate to Atlas when Tag Source set to AtlasRest in Kerberos environment Key: RANGER-2155 URL: https://issues.apache.org/jira/browse/RANGER-2155 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.1.0 Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: 2.0.0 When setting Tag source as Atlas Rest for Ranger Tagsync in a Kerberized environment, Tagsync fails to authenticate to Atlas throwing 401 Exception in a Kerberos environment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2076) Handle proxy users for Kerberos based authentication.
Vishal Suvagia created RANGER-2076: -- Summary: Handle proxy users for Kerberos based authentication. Key: RANGER-2076 URL: https://issues.apache.org/jira/browse/RANGER-2076 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: master Reporter: Vishal Suvagia Assignee: Vishal Suvagia Fix For: master Need to handle proxy users when authenticated by Kerberos. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-2060) Knox proxy with knox-sso is not working for ranger
[ https://issues.apache.org/jira/browse/RANGER-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia reassigned RANGER-2060: -- Assignee: Vishal Suvagia > Knox proxy with knox-sso is not working for ranger > -- > > Key: RANGER-2060 > URL: https://issues.apache.org/jira/browse/RANGER-2060 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Deepak Sharma >Assignee: Vishal Suvagia >Priority: Major > Fix For: 1.1.0, 1.0.1 > > Attachments: RANGER-2060.patch > > > Knox proxy with Knox-SSO is not working in a case when HA is enabled for both > Ranger and Knox. > If Ranger-HA url is rangerha.abc.com:6080 with individual Ranger hosts as > ranger1.abc.com:6080 and ranger2.abc.com:6080 with Knox hosted on > knoxha.abc.com:8443 and individual knox hosts as knox1.abc.com and > knox2.abc.com. > If Ranger load-balancer URL is used in the knox topology for knox-proxy > ui.xml, redirected url gets corrupted as: > knoxha.abc.com:8443/gateway/?originalUrl=https://knoxha.abc.com:8443,%20knox1.abc.com:8443/gateway//ranger > Additionally: Individually enabling Knox-SSO gives 401-Unauthorized error for > Ranger to login. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2060) Knox proxy with knox-sso is not working for ranger
[ https://issues.apache.org/jira/browse/RANGER-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430376#comment-16430376 ] Vishal Suvagia commented on RANGER-2060: Request to kindly review the attached patch. > Knox proxy with knox-sso is not working for ranger > -- > > Key: RANGER-2060 > URL: https://issues.apache.org/jira/browse/RANGER-2060 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Vishal Suvagia >Priority: Major > Fix For: 1.1.0, 1.0.1 > > Attachments: RANGER-2060.patch > > > Knox proxy with Knox-SSO is not working in a case when HA is enabled for both > Ranger and Knox. > If Ranger-HA url is rangerha.abc.com:6080 with individual Ranger hosts as > ranger1.abc.com:6080 and ranger2.abc.com:6080 with Knox hosted on > knoxha.abc.com:8443 and individual knox hosts as knox1.abc.com and > knox2.abc.com. > If Ranger load-balancer URL is used in the knox topology for knox-proxy > ui.xml, redirected url gets corrupted as: > knoxha.abc.com:8443/gateway/?originalUrl=https://knoxha.abc.com:8443,%20knox1.abc.com:8443/gateway//ranger > Additionally: Individually enabling Knox-SSO gives 401-Unauthorized error for > Ranger to login. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2060) Knox proxy with knox-sso is not working for ranger
[ https://issues.apache.org/jira/browse/RANGER-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia updated RANGER-2060: --- Attachment: RANGER-2060.patch > Knox proxy with knox-sso is not working for ranger > -- > > Key: RANGER-2060 > URL: https://issues.apache.org/jira/browse/RANGER-2060 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Vishal Suvagia >Priority: Major > Fix For: 1.1.0, 1.0.1 > > Attachments: RANGER-2060.patch > > > Knox proxy with Knox-SSO is not working in a case when HA is enabled for both > Ranger and Knox. > If Ranger-HA url is rangerha.abc.com:6080 with individual Ranger hosts as > ranger1.abc.com:6080 and ranger2.abc.com:6080 with Knox hosted on > knoxha.abc.com:8443 and individual knox hosts as knox1.abc.com and > knox2.abc.com. > If Ranger load-balancer URL is used in the knox topology for knox-proxy > ui.xml, redirected url gets corrupted as: > knoxha.abc.com:8443/gateway/?originalUrl=https://knoxha.abc.com:8443,%20knox1.abc.com:8443/gateway//ranger > Additionally: Individually enabling Knox-SSO gives 401-Unauthorized error for > Ranger to login. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2060) Knox proxy with knox-sso is not working for ranger
Vishal Suvagia created RANGER-2060: -- Summary: Knox proxy with knox-sso is not working for ranger Key: RANGER-2060 URL: https://issues.apache.org/jira/browse/RANGER-2060 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 1.0.0 Reporter: Vishal Suvagia Fix For: 1.1.0, 1.0.1 Knox proxy with Knox-SSO is not working in a case when HA is enabled for both Ranger and Knox. If Ranger-HA url is rangerha.abc.com:6080 with individual Ranger hosts as ranger1.abc.com:6080 and ranger2.abc.com:6080 with Knox hosted on knoxha.abc.com:8443 and individual knox hosts as knox1.abc.com and knox2.abc.com. If Ranger load-balancer URL is used in the knox topology for knox-proxy ui.xml, redirected url gets corrupted as: knoxha.abc.com:8443/gateway/?originalUrl=https://knoxha.abc.com:8443,%20knox1.abc.com:8443/gateway//ranger Additionally: Individually enabling Knox-SSO gives 401-Unauthorized error for Ranger to login. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties
[ https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316181#comment-16316181 ] Vishal Suvagia commented on RANGER-689: --- Tested and verified the above patch.Looks good to me +1. > For Solr plugin, use resources folders for adding Ranger properties > --- > > Key: RANGER-689 > URL: https://issues.apache.org/jira/browse/RANGER-689 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 0.5.0 >Reporter: Don Bosco Durai >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch > > > Currently, the jars required by Ranger are added to WEB-INF/lib and > WEB-INF/classes folders. However, Solr recommends to put all extension jars > in server/lib/ext and properties in server/resources > We should update out plugin installer code to use the new location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1797) Tomcat Security Vulnerability Alert. The version of the tomcat for ranger should upgrade to 7.0.82.
[
https://issues.apache.org/jira/browse/RANGER-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated RANGER-1797:
---
Attachment: catalina.out
Attaching [^catalina.out], as per info shared on review request.
> Tomcat Security Vulnerability Alert. The version of the tomcat for ranger
> should upgrade to 7.0.82.
> ---
>
> Key: RANGER-1797
> URL: https://issues.apache.org/jira/browse/RANGER-1797
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 1.0.0, master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Labels: patch
> Attachments:
> 0001-RANGER-1797-Tomcat-Security-Vulnerability-Alert.-The.patch, catalina.out
>
>
> 【Security Vulnerability Alert】Tomcat Information leakage and remote code
> execution vulnerabilities.
> CVE ID:
> {code}
> CVE-2017-12615\CVE-2017-12616
> {code}
> Description
> {code}
> CVE-2017-12615:When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with
> HTTP PUTs enabled, it was possible to upload a JSP file to the server via a
> specially crafted request. This JSP could then be requested and any code it
> contained would be executed by the server.
> CVE-2017-12616:When using a VirtualDirContext with Apache Tomcat 7.0.0 to
> 7.0.80, it was possible to use a specially crafted request, bypass security
> constraints, or get the source code of JSPs for resources served by the
> VirtualDirContext, thereby cased code disclosure.
> {code}
> Scope
> {code}
> CVE-2017-12615:Apache Tomcat 7.0.0 - 7.0.79
> CVE-2017-12616:Apache Tomcat 7.0.0 - 7.0.80
> {code}
> Solution
> {code}
> The official release of the Apache Tomcat 7.0.81 version has fixed the two
> vulnerabilities and recommends upgrading to the latest version.
> {code}
> Reference
> {code}
> https://tomcat.apache.org/security-7.html
> http://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.81
> https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.82
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
