You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2015/04/10 18:33:12 UTC
[jira] [Resolved] (AMBARI-10053) The path(s) to the Kerberos
utilities (kadmin, klist, etc...) should be configurable
[ https://issues.apache.org/jira/browse/AMBARI-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas resolved AMBARI-10053.
-----------------------------------
Resolution: Fixed
Committed to branch branch-2.0.maint
{code}
commit 5fcfb6ab998b663742d7f6cf1db38d824aa93815
Author: Robert Levas <rl...@hortonworks.com>
Date: Tue Mar 24 06:30:52 2015 -0400
{code}
> The path(s) to the Kerberos utilities (kadmin, klist, etc...) should be configurable
> ------------------------------------------------------------------------------------
>
> Key: AMBARI-10053
> URL: https://issues.apache.org/jira/browse/AMBARI-10053
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: kerberos
> Fix For: 2.1.0
>
> Attachments: AMBARI-10053_01.patch, AMBARI-10053_01.patch
>
>
> The path(s) to the Kerberos utilities (kadmin, klist, etc...) should be configurable so that the utilities can be found if using custom Kerberos packages.
> This should work for both the Ambari server and agent-side functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)