Thanks to a lot of help from the support and development groups (special thanks to Richard and Adrian), and despite having focused on my upcoming job switch and WPhone in the last month, I finally found some time to release version 1.1 of wpDirAuth, an LDAP authentication plugin for WordPress I also maintain.
The new version adds support for more directory server configurations and vendors by supporting privileged pre-binding. It also adds a few interface and documentation tweaks, and has been tested under WordPress 2.2.x and 2.3.
tekArtist 
I just installed wpDirAuth and using it to authenicate against Microsoft Active Directory. However in order to bind to our directory we do not use the default port of 389. Can you tell me how to change the default port??
Thank you.
LikeLike
Hi there Victoria,
You should post this type of questions to the wpDirAuth support group instead:
http://groups.google.com/group/wpdirauth-support/
But the short answer is that there is currently no option to do so built-in.
Join and post on the support group, and we’ll pickup the discussion there.
I’ll tell you how to change the code to do it right away, and I’ll add the feature in the next release.
Cheers
LikeLike
Thanks for providing a very useful tool.
How would I go about qualifying the wpdirauth LDAP authentication to only validate a user who is in a particular OU? Just using the standard filter, anyone in the University of Tennessee can authenticate via their LDAP credentials. However, I need to narrow that down to only those within the College of Law Library (all have ou=Law Library in their LDAP entries).
Thanks again.
LikeLike