You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Velmurugan Periasamy (JIRA)" <ji...@apache.org> on 2016/07/09 03:36:10 UTC
[jira] [Commented] (RANGER-1057) Ambari configuration for
ranger-tagsync needs to support
ranger.tagsync.source.atlasrest.keystore.filename property
[ https://issues.apache.org/jira/browse/RANGER-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15368917#comment-15368917 ]
Velmurugan Periasamy commented on RANGER-1057:
----------------------------------------------
[~kulkabhay] - If this issue is addressed by AMBARI-17415, can you close this JIRA?
> Ambari configuration for ranger-tagsync needs to support ranger.tagsync.source.atlasrest.keystore.filename property
> -------------------------------------------------------------------------------------------------------------------
>
> Key: RANGER-1057
> URL: https://issues.apache.org/jira/browse/RANGER-1057
> Project: Ranger
> Issue Type: Bug
> Components: tagsync
> Affects Versions: 0.6.0
> Reporter: Abhay Kulkarni
> Fix For: 0.6.0
>
>
> In Ranger-Tagsync configuration using Ambari, the following improvements need to be made.
> 1. If Atlasrest is selected as tag-source, then Atlas Endpoint (from the Atlas URL) and Atlas source download interval (default:60000) need to populated.
> 2. In Advanced->Advanced ranger-tagsync-site tab, ranger.tagsync.source.atlasrest.keystore.filename property needs to be added and auto-populated to a reasonable default (such as /usr/hdp/current/ranger-tagsync/conf/atlasuser.jceks). If this property is not specified or has no value, then updatetagadminpassword.py script fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)