You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Steven Willis (JIRA)" <ji...@apache.org> on 2014/03/12 16:35:43 UTC
[jira] [Commented] (ZOOKEEPER-1422) Support _HOST substitution in
JAAS configuration
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931873#comment-13931873 ]
Steven Willis commented on ZOOKEEPER-1422:
------------------------------------------
[~phunt], I believe the functionality in HADOOP-8381 was what [~thw] was referencing. However, last time I checked, (which was a while ago) this functionality was not available in the zookeeper jaas configuration, only in the hadoop '*-site.xml' configuration files. Did the change introduced in HADOOP-8381 make the _HOST substitution more widely available?
> Support _HOST substitution in JAAS configuration
> -------------------------------------------------
>
> Key: ZOOKEEPER-1422
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1422
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.4.0
> Reporter: Thomas Weise
>
> At the moment a JAAS configuration file needs to be created with the Kerberos principal specified as user/host. It would be much easier for deployment automation if the host portion could be resolved at startup time, as supported in Hadoop (something like user/_HOST instead of user/hostname). A configuration alternative to global JAAS conf would be even better (via direct properties in zoo.cfg?).
--
This message was sent by Atlassian JIRA
(v6.2#6252)