After much work and preparation, the 3.0 plugin is ready to go. Most of the kinks should be worked out of it, but if you notice anything please let me know! Just like the previous versions, the plugin must be installed in the “mu-plugins” folder. The only difference with WP 3.0, is that the folder does not exist by default. You will need to create the “mu-plugins” folder under “wp-content”. Drop the files in there and you should be good to go!
The plugin also now supports basic group authentication for both allow and deny groups. Thanks to the help of Ken Newquist, we were able to test this extensively across both Active Directory and OpenLDAP platforms. Example configurations are available on the Documentation page.
Other fixes and changes included in this release:
- Basic deny/allow group logic
- Changed bulk add logic to not automatically create blogs if the option is enabled – wordpress does not support this functionality
- Fixed issues with connection check not working when plugin is not enabled
- Fixed typo in default ldaps port in the documentation
- Fixed issue where local users would still attempt to authenticate against ldap
- Added better error checking on failure when adding users from the add user menu
The plugin can be download from the Sourceforge project page. As always, I hope you enjoy it and please report any problems or suggestions you might have!
In an effort to simplify my own setup, the blog address has been changed to http://wpmuldap.tuxdocs.net. The old address will redirect traffic so any existing links out there should be fine.
For those of you testing on the 3.0 trunk, I have added basic allow and deny group support for overall blog access. There is logic in there to handle nested groups as well. However, I only have the ability to test this against an Active Directory server – so if any of you are connecting to openldap, opendirectory or something else and are willing to test, let me know how it works (or how it doesn’t)!
I just wanted to give everyone a heads up that the svn trunk will be in a very alpha state as I beginning testing and tweaking for the 3.0 WP release. Anyone else who is testing – feel free to post back anything weird you may be noticing. As of right now, things seem to function in a basic form.
The latest version of the WPMU Ldap plugin is now available for download. This is a minor bugfix release – see the changlog for full details. Even though the plugin version is 2.9 – it should continue to work with the 2.8 series of WPMU.
The plugin can be download from the Sourceforge project page. As always, I hope you enjoy it and please report any problems or suggestions you might have!
The latest version of the WPMU Ldap plugin is now available for download. This is a minor bugfix release, and also includes revamped back end code to use the new authenticate hook instead of the old method of overwriting the wp_authenticate function. It should also correct some of the odd issues that surfaced from 2.8.2.
This release will completely break any remote chance of compatibility with version older than 2.8. If you are still running an older version, this is a great reason to upgrade!
The plugin can be download from the Sourceforge project page. As always, I hope you enjoy it and please report any problems or suggestions you might have!
This is a bugfix release. With the 2.8.1 release, on first load of the login page a authentication error was being displayed. This problem has been corrected.
The plugin can be download from the Sourceforge project page. As always, I hope you enjoy it and please report any problems or suggestions you might have!
The latest version of the WPMU Ldap plugin is now available for download. What happened to 2.8? Since WPMU jumped right to 2.8.1, we will too! This version contains minor bugfixes and a few new features. This release further integrates into the new WPMU 2.8.1 release. The full list of changes are:
- LDAP Attributes converted to lowercase on save
- Experimental SSO Support
- Changed ldap_connect attributes to match as documented
- Removed default “Add New” option in 2.7
- Fixed issue where display_name cannot be edited, added upgrade function to migrate existing values
In order for users to be able to modify their display name, the display_name value has been modified to edit the value directly in the users db table. Because of this, you will need to run the function on the “Upgrade” tab to migrate over the existing values.
The plugin can be download from the Sourceforge project page. As always, I hope you enjoy it and please report any problems or suggestions you might have!
I’ve been doing some thinking on how to best implement group support into the plugin. This would probably be a multi phase approach, to hopefully fulfill all requests.
NOTE: This is currently a work in progress and there is no estimate on when it will be complete
Per Blog Settings
LDAP Group mapping on a per blog, per role basis. This would all for any given blog to map each individual role to a separate LDAP group. The goal would be for these groups to automatically check for new users on logon and update accordingly. The biggest concern here is figuring out a way for the automatic updating to happen without having a huge impact on performance.
Sitewide Settings
Group based control of the following:
- Who can login to the blog (standard user)
- Who can login to the blog with automatic blog creation
- Who can’t login – deny list
Are there any other thoughts on other possible setups or anything else that others would like added? If so – please leave a comment with your thoughts!
NOTE: This release is REQUIRED for WordPress MU 2.7.1 and later
This is a bugfix release that is necessary for WordPress MU 2.7.1. Some core functionality has changed which was causing the LDAP plugin to incorrectly re-populate the users with a subscribe status on blog 1. This was causing some array_merge php errors – and also could have resulted in weird behavior on site admin logins.
Unfortunately, if you are affected by this, there is some minor database cleanup that is necessary. Site admin users will need the subscribe capability removed from the wp_usermeta for wp_1_capability. Sorry for the inconvenience.
In addition, this realease also adds the ability to map the WordPress Nickname field to a ldap attribute. If the mapped attribute does not exist, it will use the default value to populate the display name.
As always, the plugin can be downloaded from the Sourceforge Project Page.
