ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wangyaoxin (JIRA)" <>
Subject [jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
Date Tue, 06 Dec 2016 01:41:58 GMT


wangyaoxin commented on AMBARI-19079:

Hi [~rlevas]  ,Thank you ,I see  and I'll give a new description of the problem:
If we use ppc(power machine), after enable kerberos,  when excute :hdfs dfs -ls /  ,the wrong
message is: Failure to initialize security context [Caused by org.ietf.jgss.GSSException,
major code: 13, minor code: 0
it might just because the ibm jdk don't support the kerberos client kinit, and we have to
use the {ibm_home/jre/bin/kinit to create tickets manual;
and another problem is the templates files of hbase metrics and zookeeper ,like zookeeper_jass.conf.j2
( required)  sun isn't configurable
This cause problem when we use IBM Jdk to directly turn on Kerberos, that requires to change
configurations at back-end. Therefore I raised the question, is it necessary for ambari supporting
an automatic start of Kerberos operated by ibm?

> The kerberos -kt should be free configuration
> ---------------------------------------------
>                 Key: AMBARI-19079
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: wangyaoxin
>            Assignee: wangyaoxin
>             Fix For: trunk, 2.5.0
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool Kinit ({jdk_home}/jre/bin/kinit
-A -k -t); therefore I sense it would be better to add two configurations item in kerberos-env
for kt and java type, for example, cmd_type and java_type .

This message was sent by Atlassian JIRA

View raw message