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

Priority: Low
Current State: New
Released In: n/a
Target Release: n/a
Applies To: Extension
Component: LdapContrib
Reported By: MichaelRitter
Waiting For:
Last Change By: MichaelRitter
Suppose my LDAP server is on 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:// 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).

  • 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


ItemTemplate edit

Summary {Ldap}{Port} should be based on {Ldap}{Host}
ReportedBy MichaelRitter
Codebase 1.1.2
SVN Range
AppliesTo Extension
Component LdapContrib
Priority Low
CurrentState New
TargetRelease n/a
ReleasedIn n/a
Topic revision: r1 - 16 Feb 2011, MichaelRitter
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy