[
https://issues.apache.org/jira/browse/AMBARI-18463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-18463:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 1bf206907ea26eeeada640406ae2c130aa4140c9
Author: Robert Levas <rle...@hortonworks.com>
Date: Tue Oct 4 13:15:43 2016 -0400
{noformat}
Committed to branch-2.5
{noformat}
commit b3410400126fe7a3d32f0fd2597f38eb82b3f67c
Author: Robert Levas <rle...@hortonworks.com>
Date: Tue Oct 4 13:18:22 2016 -0400
{noformat}
> Regression: krb5JAASLogin.conf is not updated during secure BP install
> ----------------------------------------------------------------------
>
> Key: AMBARI-18463
> URL: https://issues.apache.org/jira/browse/AMBARI-18463
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Blocker
> Labels: blueprints, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18463_branch-2.5_01.patch,
> AMBARI-18463_branch-2.5_02.patch, AMBARI-18463_trunk_01.patch,
> AMBARI-18463_trunk_02.patch
>
>
> When installing a secure cluster using Blueprints, Ambari's
> {{/etc/ambari-server/conf/krb5JAASLogin.conf}} is not updated to reflect the
> details of the Ambari Kerberos identity.
> This was introduced by the patch for AMBARI-18406.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
