[
https://issues.apache.org/jira/browse/AMBARI-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051127#comment-15051127
]
Robert Levas commented on AMBARI-11001:
---------------------------------------
I am not exactly sure where this is done, however I assume it is automagically
handled by the Krb5LoginModule implementation. I believe that the logic for
obtaining and renewing Kerberos tickets is all handled in that implementation
based on the setting in the JAAS config file.
> Ambari uses users' interactive ticket cache
> -------------------------------------------
>
> Key: AMBARI-11001
> URL: https://issues.apache.org/jira/browse/AMBARI-11001
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Labels: JAAS
> Fix For: 2.1.0
>
> Attachments: AMBARI-11001_01.patch
>
>
> It appears that it is necessary to kinit prior to starting ambari-server,
> even after ambari-server setup-security (#3). It seems that this should be
> automatically handled by Ambari.
> Ambari-server should NOT use the same ticket cache as the interactive user.
> STR:
> 1. kinit
> 2. ambari-server start
> 3. verify that ambari-server can authenticate with ticket specified in #1
> 4. kdestroy
> 5. try to authenticate through Ambari again (it will not work)
> *Solution*
> Ensure JAAS Login works properly such that the Kerberos tickets for the
> account that executes Ambari is not relevant.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
