[Auth_ldap] Authentication to port 636 with Active Directory
Aaron Smith
Aaron.Smith at kzoo.edu
Tue Oct 24 05:28:52 PDT 2006
I have auth_ldap authenticating to Active Directory on port
3269 using OpenSSL and ldaps://. Is there a reason why auth_ldap has
to authenticate to the Secure Global Catalog port of 3269 instead of the
Secure LDAP port of 636? If I try to point to authentication URL to
port 636, it just times out (the server *is* listening at that port).
I'd like to authenticate via an AD attribute that currently is not in
the Global Catalog. I can add it, but if auth_ldap with authenticate to
the regular port, then I won't have to mess around with doing that. :-)
--------------------------------------------------------------------
Aaron Smith Aaron.Smith at kzoo.edu
System Administrator (269) 337-7496
Kalamazoo College
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.rudedog.org/pipermail/auth_ldap/attachments/20061024/16a65eda/attachment.htm
More information about the Auth_ldap
mailing list