ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alok Lal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-801) Enable tagsync to run in secure mode.
Date Fri, 08 Jan 2016 08:25:39 GMT

    [ https://issues.apache.org/jira/browse/RANGER-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088878#comment-15088878

Alok Lal commented on RANGER-801:

[New/different review|https://reviews.apache.org/r/42063/] created to do auth using jass config,
since tagsync would need to have a secure kafka client which can *only* work with a jass config.
 This method future avoid duplicate configuration -- one for kafka and one for talking to
ranger admin.  As prior tested by writing to hdfs and testing identity in ranger audit logs.

> 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
>         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
> 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

View raw message