The technical aspect of the translation isn’t hard. The plugin directory contains a file named ad-integration.pot, which is the starting point for any translation. The followng briefly describes the steps required to create a new language file.

1. Copy the ad-integration.pot file and rename the copy to ad-integration-<language>_<COUNTRY>.po. Replace <language> with the abbreviation for the language, and <COUNTRY> with the abbreviation for the country. For example, the language file for italian would be called ad-integration-it_IT.po. The appropriate language and region codes can be found here.
2. Download Poedit from here and install it.
3. Launch Poedit and open the language file you created. (For example, ad-integration-it_IT.po)
4. The original english text can be seen on the left hand side. Your translations will be on the right. If you click on a line, you can input your translation at the bottom of the program window. Please make sure to keep the %s and %d symbols in your translated text. They are placeholders that are replaced by values from the plugin at runtime. For example, the english text “Error deleting Setting Key `%s`” is translated in german to “Fehler beim Löschen des Schlüssels`%s`”.
5. In order to save your translations, simply click “File -> Save”. This will automatically create a .mo file (i.e. ad-integration-it_IT.mo). This file contains the translated text in a binary form that is ultimately used in WordPress.
6. When you are finished translating, send me the translation file (po) at christoph.steindorff@ecw.de.

All translators will be mentioned in the readme.txt (and therefore also on wordpress.org) by name and, on request, also with an eMail address and homepage.

Here the plans for further improvements of the Active Directory Integration WordPress plugin:

• WordPress MU compatibility (planned for 1.0) Rudimentary implemented since 0.9.9.8 but WordPress 3.0 MultiSite is supported.
• WordPress 3.0 compatibility
• tool for testing DONE 0.9.9-dev
• object-orientation redesign DONE 0.9.1
• code clean up DONE 0.9.1
• email notification of user and/or admin when a user account is blocked DONE 0.9.1
• drop table on uninstall or deactivation DONE 0.9.2
• adding more languages
• better user interface for role <> group assignment
• set different ldap ports per server
• help page DONE 0.9.2.
• determine WP display name from AD attributes DONE 0.9.3
• authenticate against multiple domains (perhaps, have to think about)
• enable/disable password changes for local (non AD) WP users DONE 0.9.8
• multiple authorization groups (as requested by Lori Dabbs) DONE 0.9.8

to be continued…

AD Integration is in principle compatible to WordPress 3.0. However  there is a little problem with the changes made to wp_insert_user() in wp-includes/registration.php. Now WordPress prevents from creating users with email addresses that are in use by other users already in the database.

The current development version contains a workaround, so Automatic User Creation works as before. A new option will be introduced with the 0.9.9.9 release. Then you can decide how the behavior should be, when duplicate email addresses are found:

1. The User will not be created (default, secure).
2. The User will be created and you’ll have 2 or more users with the same email address (unsecure).
3. The User gets a new, partially random email address (partially unsecure).

The new version 0.9.9.9 will be released soon. Use the development version until then.

Today I have finished my work an the WordPress Plugin Active Directory Integration and published it on wordpress.org . The plugin  is based on a work of  Jonathan Marc Bearak and gives you the ability to authenticate and authorize your WordPress users against an Active Diretory. One of the major improvements is security.