[
https://issues.apache.org/jira/browse/TC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Mitchell updated TC-73:
------------------------------
Summary: TO - Enhance LDAP implementation to follow referrals (was:
Enhance LDAP implementation to follow referrals)
> TO - Enhance LDAP implementation to follow referrals
> ----------------------------------------------------
>
> Key: TC-73
> URL: https://issues.apache.org/jira/browse/TC-73
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops
> Reporter: Jeremy Mitchell
> Priority: Minor
>
> the ldap.conf file created from postinstall looks like this and is required
> to support ldap authentication:
> { "host" : "ldap.foo.bar.com", "admin_dn" : "[email protected]", "admin_pass"
> : "password", "search_base" : "dc=foo,dc=bar,dc=com" }
> this means if you login using ldap credentials, the search is scoped to the
> foo subdomain. If there are other subdomains in bar (i.e. foo1 and foo2), you
> may want to increase the scope of the search and change the search_base of
> your ldap configuration to look like:
> { "host" : "ldap.foo.bar.com", "admin_dn" : "[email protected]", "admin_pass"
> : "password", "search_base" : "dc=bar,dc=com" }
> however, the current implementation of ldap in traffic ops using Net::LDAP
> does not support following "referrals".
> Looks like the relevant code is here or around here:
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/TrafficOps.pm#L393
> This link may offer some more insight into referrals:
> http://etutorials.org/Server+Administration/ldap+system+administration/Part+II+Application+Integration/Chapter+10.+Net+LDAP+and+Perl/10.5+Advanced+Net+LDAP+Scripting/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
