You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2017/02/27 10:01:45 UTC

[jira] [Updated] (AMBARI-20196) Ambari should install the unlimited key JCE policy based on service requirements even if cluster is not Kerberized

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

Robert Levas updated AMBARI-20196:
----------------------------------
    Attachment: AMBARI-20196_trunk_01.patch
                AMBARI-20196_branch-2.5_01.patch

> 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_trunk_01.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)