Item10361: {Ldap}{Port} should be based on {Ldap}{Host}

Suppose my LDAP server is on ldap.mydomain.com and is only accessible via SSL. In order for NET::LDAP to connect to the server properly, I have to set {Ldap}{Host} to ldaps://ldap.mydomain.com and {Ldap}{Port} to 636 (standard ldaps port). I would have expected that leaving the {Ldap}{Port} setting blank would automatically choose the correct standard port here. But a look at the code reveals that in case of a blank port setting the port always seems to be set to 389 (the standard LDAP port without SSL). Also, I did not expect the need to use the ldaps:// in the host setting (normal ldap:// would not require it).

Suggestion:

• Document the need to specify ldaps:// explicitly.
• Check for ldaps:// being set and change the default port accordingly, if no port is set explicitly.

BTW: My observations are based on release 4.30 of LdapContrib, the latest at the time of this writing.

-- MichaelRitter - 16 Feb 2011

Commenting is disabled while not logged in