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/01/02 17:54:13 UTC

[jira] [Updated] (AMBARI-8976) Use cluster property rather than cluster-env/security_enabled to enable or disable Kerberos

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

Robert Levas updated AMBARI-8976:
---------------------------------
    Priority: Blocker  (was: Major)

> Use cluster property rather than cluster-env/security_enabled to enable or disable Kerberos
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8976
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8976
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: kerberos
>             Fix For: 2.0.0
>
>
> Use a cluster property rather than {{cluster-env/security_enabled}} to enable or disable Kerberos.  Since {{cluster-env/security_enabled}} is used by services to determine if Kerberos is enabled or not, it should not be set before completing the process of enabling or disabling Kerberos.  To declare whether the cluster enable or disable Kerberos, a property on the cluster should be set.  The property should be called {{security_type}} and must have one of the following values:
> * NONE
> * KERBEROS 



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