Re: ZK 3.4.6 creating malformed TGT

Ok, thanks Irfan! Patrick On Wed, Aug 24, 2016 at 2:58 PM, Irfan Hamid wrote: > Sure. It was not very straightforward. I ended up setting the logging level > on the client side by adding the -Dlogging.level=DEBUG and > -Dsun.security.krb5.debug=true. Additionally I set

Re: ZK 3.4.6 creating malformed TGT

Sure. It was not very straightforward. I ended up setting the logging level on the client side by adding the -Dlogging.level=DEBUG and -Dsun.security.krb5.debug=true. Additionally I set debug=true in the jaas.conf. With this I got log lines similar to the following on the client: KrbException:

Re: ZK 3.4.6 creating malformed TGT

Thanks Patrick, Actually it wasn't a DNS issue but I believe this is something that others in the community could find useful since the issue had to do with default realms domain-to-realm conversions and krb5.conf issues. Our setup has multiple domains (one for prod and one for internal testing

Re: ZK 3.4.6 creating malformed TGT

I'm not an expert but I believe this indicates an environmental issue, see "service ticket not found in the subject" here: https://steveloughran.gitbooks.io/kerberos_and_hadoop/content/sections/errors.html Patrick On Tue, Aug 16, 2016 at 12:11 PM, Irfan Hamid wrote: >

ZK 3.4.6 creating malformed TGT

Hi, I'm very certain this is due to an error in my jaas or krb5 conf files but I can't seem to figure out where. My jaas.conf looks something like this: Client { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true keyTab="/etc/zkcli_app_eng.keytab" storeKey=true