ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "wangyaoxin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19079) The kerberos -kt should be free configuration
Date Mon, 05 Dec 2016 09:42:58 GMT

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

wangyaoxin updated AMBARI-19079:
--------------------------------
    Description: 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
.  (was: 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 a configuration item in kerberos-env
for kt, for example, cmd_type.)

> The kerberos -kt should be free configuration
> ---------------------------------------------
>
>                 Key: AMBARI-19079
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19079
>             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
(v6.3.4#6332)

Mime
View raw message