[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ldaps and Active Directory

To: Quanah Gibson-Mount <quanah@stanford.edu>
Subject: Re: ldaps and Active Directory
From: Michael Ströder <michael@stroeder.com>
Date: Fri, 09 Dec 2005 18:52:33 +0100
Cc: OpenLDAP-software@OpenLDAP.org
In-reply-to: <DB052FB65F992A1E4DA6F379@cadabra-sw.stanford.edu>
References: <BAY106-F31B3550EE7DC3EF8F5DA21B0420@phx.gbl> <008201c5fc46$17514700$a0601bac@axalto.com> <DB052FB65F992A1E4DA6F379@cadabra-sw.stanford.edu>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920

Quanah Gibson-Mount wrote:
> 
> 
>> Did you change your LDAP port from 389 (clear text connection) to 636
>> (SSL
>> connection)?
> 
> Port 389 is not necessarily clear text, as LDAP V3 supports TLS over
> 389. Just to be clear.

But if someone uses LDAP URL schema ldaps:// without specifying a port
number the port 636 is assumed as default. You would send a startTLS ext
op over a connection specified by LDAP URL scheme ldap://.

Ciao, Michael.

References:
- ldaps and Active Directory
  - From: "Grant Sturgis" <gesturgis@hotmail.com>
- Re: ldaps and Active Directory
  - From: Shuh Chang <schang@axalto.com>
- Re: ldaps and Active Directory
  - From: Quanah Gibson-Mount <quanah@stanford.edu>

Prev by Date: Re: Slow adding attributes to a entry with many attributes
Next by Date: database corruption
Index(es):
- Chronological
- Thread