[
https://issues.apache.org/jira/browse/AMBARI-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002997#comment-15002997
]
Hudson commented on AMBARI-13847:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #849 (See
[https://builds.apache.org/job/Ambari-branch-2.1/849/])
AMBARI-13847. Ranger smart config - AD url missing ldap:// (or (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8dfb835127bfc51702c3a69d795ccef4efe91968])
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* ambari-server/src/test/python/stacks/2.3/common/test_stack_advisor.py
* ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
> 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)
