[
https://issues.apache.org/jira/browse/AMBARI-10875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523528#comment-14523528
]
Hudson commented on AMBARI-10875:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2501 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2501/])
AMBARI-10875. Kerberos Identity data is empty when Cluster.security_type !=
KERBEROS (rlevas) (rlevas:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c7d6fcbc5311301b9478e4305e612f5e72df20c4)
*
ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java
> 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)
