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 2016/02/03 18:35:40 UTC

[jira] [Created] (AMBARI-14905) Add API directive to force toggling Kerberos if the cluster's security type has not changed

Robert Levas created AMBARI-14905:
-------------------------------------

             Summary: Add API directive to force toggling Kerberos if the cluster's security type has not changed
                 Key: AMBARI-14905
                 URL: https://issues.apache.org/jira/browse/AMBARI-14905
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 2.2.0
            Reporter: Robert Levas
            Assignee: Robert Levas
             Fix For: 2.2.2


Add an API directive to force toggling Kerberos if the cluster's security type has not changed.  

This is useful for _retry_ attempts to enable or disable Kerberos when the workflow progressed far enough to store the _new_ security type.  

Trying to enable Kerberos when the cluster's security type is already set to {{KERBEROS}} will result in a successful response from the Ambari server but no actions will be performed.  Same for attempting to disable Kerberos when the cluster's security type is already set to {{NONE}}.  

By forcing the operation using the {{force_toggle_kerberos=true}} directive, the security type check is avoided, thus allowing the _retry_ operation to proceed. 

Example: 
{code}
PUT /api/v1/clusters/CLUSTER_NAME?force_toggle_kerberos=true
{
  "Clusters" : {
    "security_type" : "KERBEROS"
    }
}
{code}



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