ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8480) Kerberos service components should indicate security state
Date Sun, 30 Nov 2014 11:21:12 GMT

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

Robert Levas updated AMBARI-8480:
---------------------------------
    Issue Type: Improvement  (was: Bug)

> Kerberos service components should indicate security state
> ----------------------------------------------------------
>
>                 Key: AMBARI-8480
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8480
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, stacks
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos, lifecycle, security
>             Fix For: 2.0.0
>
>
> The Kerberos service components should indicate security state when queried by Ambari
Agent via STATUS_COMMAND.  Each component should determine it's state as follows:
> h3. KERBEROS_CLIENT
> h4. Indicators
> * Command JSON
> ** config\['configurations']\['cluster-env']\['security_enabled'] 
> *** = “true”
> h4. Pseudocode
> {code}
> if indicators imply security is on and validate
>     state = SECURED_KERBEROS
> else
>     state = UNSECURED
> {code}
> _*Note*_: Due to the _cost_ of calling {{kinit}} results should be cached for a period
of time before retrying.  This may be an issue depending on the frequency of the heartbeat
timeout.



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

Mime
View raw message