You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Mugdha Varadkar (JIRA)" <ji...@apache.org> on 2016/05/06 09:28:12 UTC
[jira] [Updated] (AMBARI-16285) Ranger Tagsync stack changes to
sync tags from Atlas
[ https://issues.apache.org/jira/browse/AMBARI-16285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mugdha Varadkar updated AMBARI-16285:
-------------------------------------
Description:
Following changes need to be done on top of current tagsync implementation.
* Do not show tagsync user password in Ambari. Need to update default password tagsync in jceks. This will make tagsync similar to usersync.
* For communication from tagsync to ranger admin will use tagsync user.
* Derive tag source as ATLAS, if ATLAS is installed.
was:
Following changes need to be done on top of current tagsync implementation.
* Do not show tagsync user password in Ambari. Need to update default password tagsync in jceks. This will make tagsync similar to usersync.
* Fo communication from tagsync to ranger admin will use tagsync user.
* Derive tag source as ATLAS, if ATLAS is installed.
> Ranger Tagsync stack changes to sync tags from Atlas
> ----------------------------------------------------
>
> Key: AMBARI-16285
> URL: https://issues.apache.org/jira/browse/AMBARI-16285
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Mugdha Varadkar
> Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
>
> Following changes need to be done on top of current tagsync implementation.
> * Do not show tagsync user password in Ambari. Need to update default password tagsync in jceks. This will make tagsync similar to usersync.
> * For communication from tagsync to ranger admin will use tagsync user.
> * Derive tag source as ATLAS, if ATLAS is installed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)