[
https://issues.apache.org/jira/browse/AMBARI-17787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384047#comment-15384047
]
Hadoop QA commented on AMBARI-17787:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12818801/AMBARI-17787.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7921//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7921//console
This message is automatically generated.
> LDAPS must be used to communicate with an Active Directory when Kerberos is
> being enabled (FE)
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-17787
> URL: https://issues.apache.org/jira/browse/AMBARI-17787
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-17787.patch
>
>
> LDAPS must be used to communicate with an Active Directory when Kerberos is
> being enabled.
> This should be verified on input by the frontend 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)