You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "rangerqa (JIRA)" <ji...@apache.org> on 2016/02/04 04:08:39 UTC
[jira] [Commented] (RANGER-801) Enable tagsync to run in secure
mode.
[ https://issues.apache.org/jira/browse/RANGER-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131637#comment-15131637 ]
rangerqa commented on RANGER-801:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12780884/801.0.patch
against master revision ee496c1.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-RANGER-Build/29//console
This message is automatically generated.
> Enable tagsync to run in secure mode.
> -------------------------------------
>
> Key: RANGER-801
> URL: https://issues.apache.org/jira/browse/RANGER-801
> Project: Ranger
> Issue Type: Bug
> Components: tagsync
> Affects Versions: 0.6.0
> Reporter: Alok Lal
> Assignee: Alok Lal
> Fix For: 0.6.0
>
> Attachments: 801.0.patch
>
>
> This change has three parts:
> - Being able to run the process under configured kerberos identity.
> - Use that identity to listen for updates from Atlas (kafka)
> - Able to play the tag updates to ranger admin (as and when ranger admin runs in secure mode).
> This jira for now addresses the 1st issue. Subsequent items are to be addressed in time as the other pieces fall in place.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)