You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jaimin D Jetly (JIRA)" <ji...@apache.org> on 2016/07/18 20:04:20 UTC
[jira] [Updated] (AMBARI-17763) Create seperate Identity for Atlas
Jaas Kafka client
[ https://issues.apache.org/jira/browse/AMBARI-17763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jaimin D Jetly updated AMBARI-17763:
------------------------------------
Summary: Create seperate Identity for Atlas Jaas Kafka client (was: Populating Ranger Tagsync principal/keytab using stack advisor)
> Create seperate Identity for Atlas Jaas Kafka client
> ----------------------------------------------------
>
> Key: AMBARI-17763
> URL: https://issues.apache.org/jira/browse/AMBARI-17763
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Mugdha Varadkar
> Assignee: Mugdha Varadkar
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17763.1.patch, AMBARI-17763.patch
>
>
> {{atlas.jaas.KafkaClient.option.keyTab}} and {{atlas.jaas.KafkaClient.option.principal}} properties are needed in tagsync-application-properties.xml when kerberos is enabled.
> To achieve this changing the implementation from macro to stack advisor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)