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/06/21 07:05:57 UTC

[jira] [Created] (AMBARI-17330) Ambari changes to support kerberized tagsync

Mugdha Varadkar created AMBARI-17330:
----------------------------------------

             Summary: Ambari changes to support kerberized tagsync
                 Key: AMBARI-17330
                 URL: https://issues.apache.org/jira/browse/AMBARI-17330
             Project: Ambari
          Issue Type: Improvement
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Mugdha Varadkar
            Assignee: Mugdha Varadkar
            Priority: Critical
             Fix For: 2.4.0


Remove below properties from ranger-tagsync-site.xml:
- ranger.tagsync.atlas.to.ranger.service.mapping
- ranger.tagsync.atlas.custom.resource.mappers

Add below property in ranger-tagsync-site.xml:
- ranger.tagsync.source.atlasrest.username (default - empty)

Add below properties in tagsync-application-properties.xml only if cluster is kerberized:
- atlas.jaas.KafkaClient.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
- atlas.jaas.KafkaClient.loginModuleControlFlag=required
atlas.jaas.KafkaClient.option.useKeyTab=true
- atlas.jaas.KafkaClient.option.storeKey=true
- atlas.jaas.KafkaClient.option.serviceName=kafka
- atlas.jaas.KafkaClient.option.keyTab=tagsync_keytab_path
- atlas.jaas.KafkaClient.option.principal=tagsync_jaas_principal
- atlas.kafka.sasl.kerberos.service.name=kafka
- atlas.kafka.security.protocol=SASL_PLAINTEXT



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)