[
https://issues.apache.org/jira/browse/AMBARI-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-13847:
------------------------------------
Description:
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.
> 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)
