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/05/01 02:43:05 UTC

[jira] [Updated] (AMBARI-10875) Kerberos Identity data is empty when Cluster.security_type != KERBEROS

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

Robert Levas updated AMBARI-10875:
----------------------------------
    Attachment: AMBARI-10875_01.patch

> Kerberos Identity data is empty when Cluster.security_type != KERBEROS
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-10875
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10875
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10875_01.patch
>
>
> Kerberos Identity data is empty when Cluster.security_type does not equal "KERBEROS".  
> Technically this seems to make sense since there shouldn't be any relevant Kerberos identities if the cluster isn't configured for Kerberos; however a _chicken-and-the-egg_ condition is encountered when manually enabled Kerberos and a listing of the needed Kerberos identities is needed before Kerberos is to be fully enabled. 
> *Solution*
> Allow the keberos_identities API end points to generate data even if Cluster.security_type is not equal to "KERBEROS".



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