[
https://issues.apache.org/jira/browse/AMBARI-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001849#comment-15001849
]
Hadoop QA commented on AMBARI-13847:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12771858/AMBARI-13847.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 2 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.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4268//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4268//console
This message is automatically generated.
> Ranger smart config - AD url missing ldap:// (or ldaps://)
> ----------------------------------------------------------
>
> Key: AMBARI-13847
> URL: https://issues.apache.org/jira/browse/AMBARI-13847
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.3
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-13847.patch
>
>
> When configuring LDAP/AD for usersync in new Ranger smart config, Ambari
> should construct the LDAP/AD url with prefix "ldap://";. For example, the url
> should like "ldap://localhost:389";
> When ambari is configurd with LDAP, ranger.usersync.ldap.url value should be
> set to authentication.ldap.primaryUrl with ldap:// as the prefix if not using
> ssl and should be prefixed with ldaps:// if using ssl.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
