[jira] [Resolved] (AMBARI-6397) Ambari 1.6.0 customized zookeeper keytab file not passed to zookeeper_jass.conf

["Andrew Onischuk (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Onischuk resolved AMBARI-6397.
-------------------------------------

    Resolution: Fixed

Committed to trunk

> Ambari 1.6.0 customized zookeeper keytab file not passed to zookeeper_jass.conf
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-6397
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6397
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.7.0
>
>
> PROBLEM:
> Ambari 1.5.1
> In Kerberos wizard, if set keytab file for zookeeper to be a different file
> other than zk.service.keytab, zookeeper_jaas.conf file not get updated with
> the user defined keytab file name.
> For example, if user chooses to use keytab file name aaaa.keytab, the
> zookeeper_jaas.conf file is always set to zk.service.keytab
> etc/zookeeper/conf/zookeeper_jaas.conf
> Server
> { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true
> storeKey=true useTicketCache=false
> keyTab="/etc/security/keytabs/zk.service.keytab"
> principal="sc_zookeeper/va.neustar.com@KRBPROD.NEUSTAR.COM"; }
> ;



--
This message was sent by Atlassian JIRA
(v6.2#6252)