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

Vitaly Brodetskyi updated AMBARI-9693:
--------------------------------------
    Attachment: AMBARI-9693.patch

> Review and update kerberos descriptors for various services
> -----------------------------------------------------------
>
>                 Key: AMBARI-9693
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9693
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9693.patch
>
>
> In Ambari 1.7.0, UI used to make appropriate config property changes when 
> kerberizing the cluster.
> In 2.0.0, this is all driven by the Kerb API.
> But during testing we've noticed that some properties that were previously 
> set were no longer set. For example, hbase.hbase.coprocessor.master.classes, 
> hbase.coprocessor.region.classes, etc.
> See 
> https://github.com/apache/ambari/blob/branch-1.7.0/ambari-web/app/data/HDP2/secure_mapping.js#L554
> There could be a bunch of other parameters that need to be ported over from 
> the secure_mapping.js file in order for the cluster to function properly in a 
> secure manner.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to