Re: zookeeper SASL issue

[Michael Han]

'No key to store' implies the keytab file is either not present or is
invalid. I'd suggest validate the keytab file out of the context of
zookeeper (for example using kinit) and check if it's valid.

On Thu, Jul 21, 2016 at 10:13 AM, Aneela Saleem <ane...@platalytics.com>
wrote:

> Hi,
>
> I have configured zookeeper to work with kerberos. I have added following
> principal.
> zkcli/hadoop-master@platalyticsrealm
>
> Here are contents of my jaas.conf
>
> Server {
>   com.sun.security.auth.module.Krb5LoginModule required
>   useKeyTab=true
>   keyTab="/etc/hadoop/conf/zk.keytab"
>   storeKey=true
>   useTicketCache=false
>   principal="zookeeper/hadoop-master@platalyticsrealm";
> };
> Client {
>   com.sun.security.auth.module.Krb5LoginModule required
>   useKeyTab=true
>   keyTab="/etc/hadoop/conf/zkcli.keytab"
>   storeKey=true
>   useTicketCache=true
>   principal="zkcli@platalyticsrealm"
>   debug=true;
> };
>
>
> When i run zookeeper client using the command
> *./zkCli.sh -server hadoop-master:2181*
>
> it produces following exception
>
>  SASL configuration failed: javax.security.auth.login.LoginException: No
> key to store Will continue connection to Zookeeper server without SASL
> authentication, if Zookeeper server allows it.
>
> Any suggestions
>
> Thanks
>



-- 
Cheers
Michael.