[
https://issues.apache.org/jira/browse/AMBARI-20196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20196:
----------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 9112148e597baedaab1dea15c8da299dee6f63c7
Author: Robert Levas <[email protected]>
Date: Mon Feb 27 14:51:46 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit 23861e4b66ea2b918d84f45865f8383ac0fc3efd
Author: Robert Levas <[email protected]>
Date: Mon Feb 27 14:53:06 2017 -0500
{noformat}
> Ambari should install the unlimited key JCE policy based on service
> requirements even if cluster is not Kerberized
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-20196
> URL: https://issues.apache.org/jira/browse/AMBARI-20196
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Labels: encryption, jce_policy, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-20196_branch-2.5_01.patch,
> AMBARI-20196_branch-2.5_02.patch, AMBARI-20196_trunk_01.patch,
> AMBARI-20196_trunk_02.patch, AMBARI-20196_trunk_03.patch,
> AMBARI-20196_trunk_04.patch
>
>
> Ambari should install the unlimited key JCE policy based on service
> requirements even if cluster is not Kerberized. For example, if a service
> needs the unlimited key JCE policy for an encryption task not related to
> Kerberos.
> On a similar note, the unlimited key JCE policy is not being distributed to
> the agents if Kerberos is enabled using the "manual" option - as opposed to
> integrating with an existing KDC.
> On a related note, Ambari Server host automatically unpacks JCE unlimited
> during "ambari-server setup" (unless custom JDK is used).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
