I’ve finally migrated my corporate URL redirection service from anÂ handwrittenÂ MSFT-IIS-ASP solution to a new BSD jailed system running a Drupal instance. The new solution empowers the Front Page, the Path RedirectÂ and Web file Manager modules, and enables all authorized users to both maintain all the official URL redirects and manage a dedicated WebFM file repository, from anywhere their are working.
The base URL of the new service is http://go.valsania.it.
I finally got the time to make the wpDirAuth plugin function both on WordPress 2.5.1 and WordPressÂ ÂµÂ 1.5.1. My need is to migrate to the WPMU platform from Telligent’sÂ Community Server as soon as possible, since I’m planning to port my entire corporate infrastructure from MSFT to the more dependable BSD Unix technology.
Unfortunately the 1.2 version of this plugin simply didn’t work on the latest versions of WP, so I had to apply theÂ Patch for WordPress 2.5 compatibilityÂ kindly published byÂ Adam Yearout. As now, I’ve only got the time to test it against Microsoft Active Directory LDAP servers, but I plan to try it in an Apple Open Directory environment before put it in production. The pilot blog collection can be accessed at the well-known Valsania Corporate Blogs WMPU instance.
I’ve just tried to bind against an Apple Open Directory LDAP service, and the process is quite straightforward: the only real difference is the user object’s attribute to search for to identify the user who is logging in (sAMAccountName for AD, uid for OD), ad shown in the following image.
As you see, in this example we have an OD domain named mydomain.local, and we are using the unprivileged user named dsquery to bind to the LDAP service.
NOTE: remember to populate the EMailAddress attribute of your users in Open Directory, if you whish to the required E-mail field in WordPress user profile to be automatically filled upon the first logon.