[
https://issues.apache.org/jira/browse/AMBARI-18860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15657039#comment-15657039
]
Hadoop QA commented on AMBARI-18860:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838545/AMBARI-18860.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9226//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9226//console
This message is automatically generated.
> LDAPS must be used to communicate with an Active Directory when Kerberos is
> being enabled (BE)
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-18860
> URL: https://issues.apache.org/jira/browse/AMBARI-18860
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Vitaly Brodetskyi
> Assignee: Vitaly Brodetskyi
> Fix For: 2.5.0
>
> Attachments: AMBARI-18860.patch
>
>
> LDAPS must be used to communicate with an Active Directory when Kerberos is
> being enabled.
> This should be verified on input by the backend to ensure that the proper
> channel is open between Ambari and the Active Directory so Ambari can set and
> update passwords when managing accounts in the Active Directory.
> The LDAP URL, kerberos-env/ldap_url field must have the protocol set to ldaps
> rather than ldap (or anything else). Ideally the port is set correctly, be we
> cannot validate that since the LDAPS port can be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
