Aaron Axelsen

LDAP authentication is configured on a site-wide (as opposed to per-blog) level, so only Network Admin accounts have access to the configuration to LDAP connection information.
Please make sure you have PHP compiled with LDAP support. This will show up as an LDAP section in your phpinfo() if it is correct.
Remember – all the code for the plugin was contributed by volunteers, and you can show your gratitude by giving back to the community!
<h3>How It Works</h3>
When enabled, this plugin can automatically create WordPress user accounts and blogs for LDAP-authenticated users. Assuming user credentials authenticate against the LDAP server, creating local accounts and blogs follows this 
algorithm:
Create a new WPMU User, with LDAP username and a randomly generated password. 
Some user information, such as first and last name, is extracted from the 
 information returned from the LDAP server. 
Actions for user creation and activation are triggered. 
The user’s domain / URL are created depending on plugin configuration (i.e., 
 VHost vs SubDir). 
If the option is set, a blog is created, with path and name based on the LDAP 
 username and the blog is activated with the user being Administrator, and 
 appropriate actions are triggered.
It should be noted that even though a random password is created for a user (for WPMU accounts), it is never displayed to the user. This is intentional so that there is no confusion as to which password should be used; it will always be using LDAP credentials. As a result, though, if ever LDAP is disabled or if the server is unavailable, users created with LDAP authentication will be unable to log in unless their passwords are reset.

WPMU Ldap Authentication

A plugin to override the core WordPress authentication method in order to use a LDAP server for authentication.  Currently only supported on MultiSite …

sojweb

THIS IS FOR DEVELOPMENT PURPOSES, NOT FOR USE ON PRODUCTION SITES
This plugin is meant to be a reference; I’ve talked to several people who have similar setups, and thought it would beneficial to share some code.
This plugin allows users to be authenticated via CAS, and logins to be controlled via LDAP. Default user roles can be assigned based on LDAP group membership, and accounts can be auto-created for users that exist in LDAP, but not yet in WordPress.
It assumes that, for CAS authentication, the user is redirected to an outside address, then back to the referring address; that’s how it works where I’m at :-). You can also specify a group in LDAP that will always have admin privileges; useful for tech staff.
Before the plugin is used, the constants in <code>soj-ldap_constants.inc.php</code> must be filled out. The CAS default password is the one the user is registered with in WordPress; so all WP users will have this password. Be aware of that. There is obviously more that could be done there, and I’m happy to work with others who have ideas.
I’ve adapted this from an in-house plugin I made, so there might be leftover code bits or things that look strange… feel free to harass me about that, I did this in a bit of a rush.
I’ve only ever used this plugin on one environment, so it might not work out-of-the-box for you. I’m interested in making this plugin more robust, however, so please let me know of any issues.
Contact me: jj56@indiana.edu

SoJ CAS/LDAP Login

This plugin allows users to be authenticated via CAS, and logins to be controlled via LDAP.

WPMU Ldap Authentication vs SoJ CAS/LDAP Login