Meitar

This plugin turns your WordPress Dashboard into a familiar management interface for an enterprise-scale LDAP Directory Information Tree (DIT). Configure a connection to your LDAPv3 directory server, and from then on any modifications you make to your WordPress user database through the WordPress admin screens will be reflected in your LDAP database. This offers a simpler and more convenient front-end for managing user account information to support single sign-on (SSO), identity management, and other enterprise functions.
Donations for this plugin make up a chunk of my income. If you continue to enjoy this plugin, please consider <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP-LDAP&item_number=WP-LDAP&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted" rel="nofollow ugc">making a donation</a>. 🙂 Thank you for your support!
All user accounts on the WordPress side are mirrored as <a href="https://www.ietf.org/rfc/rfc2798.txt" rel="nofollow ugc"><code>inetOrgPerson</code> (RFC 2798)</a> entries on the LDAP side. The following WordPress user account fields to LDAP attribute translations take place when a new WordPress user is created:
<ul>
<li>The WordPress <code>user_login</code> field becomes the <code>uid</code> attribute in the LDAP database.</li>
<li>The WordPress <code>user_email</code> field becomes the <code>mail</code> attribute in the LDAP database.</li>
<li>The WordPress <code>display_name</code> field becomes the <code>displayName</code> attribute in the LDAP database.</li>
<li>The WordPress <code>user_pass</code> field becomes the <code>userPassword</code> attribute in the LDAP database.</li>
</ul>
There is no mapping for the WordPress user ID number on the LDAP side. Instead, users are uniquely identified by their fully-qualified Distinguished Name (DN). A user’s DN is automatically composed by combining their WordPress <code>user_login</code> with the WordPress Multisite’s configured LDAP Search Base setting. For instance, by default, a WordPress Multisite with WP-LDAP installed running at <code>https://example.com/</code> with a user whose username is <code>exampleuser</code> will automatically be mirrored over LDAP to the user identified as <code>uid=exampleuser,dc=example,dc=com</code>.
In addition to the above mappings, the following optional mappings also take place if or when the user updates their user profile:
<ul>
<li>The WordPress <code>first_name</code> field becomes the <code>givenName</code> attribute in the LDAP database.</li>
<li>The WordPress <code>last_name</code> field becomes the <code>sn</code> attribute in the LDAP database.</li>
<li>The WordPress <code>nickname</code> field becomes the <code>cn</code> attribute in the LDAP database.</li>
<li>The WordPress <code>description</code> field becomes the <code>description</code> attribute in the LDAP database.</li>
<li>The WordPress <code>user_url</code> field becomes the <code>labeledURI</code> attribute in the LDAP database.</li>
<li>The WordPress user’s avatar becomes the <code>jpegPhoto</code> attribute in the LDAP database. (Not yet implemented.)</li>
</ul>
Moreover, WP-LDAP is aware of certain features provided by other plugins. These include:
<ul>
<li>The WordPress user’s S/MIME certificate (<code>smime_certificate</code> field) becomes the <code>userSMIMECertificate</code> attribute in the LDAP database. (This functionality is provided by the <a href="https://wordpress.org/plugins/wp-pgp-encrypted-emails/" rel="ugc">WP PGP Encrypted Emails</a> plugin and that plugin must be installed and activated for this to work.)</li>
</ul>
This plugin is designed for medium to large deployments of WordPress Multisite (or Multi-Network) instances, originally developed as a collaboration with the <a href="https://glocal.coop/activist-network-platform/" rel="nofollow ugc">Glocal Coop’s Activist Network Platform</a> project. If you run multiple WordPress Multisite Networks, you can configure each WP Network with different LDAP settings. This plugin does not currently support single-site installs; please <a href="https://github.com/meitar/wp-ldap/issues" rel="nofollow ugc">post an issue on GitHub</a> if you want to use LDAP data stores with a WP single-site install and we can discuss use cases. 
This plugin is free software, but grocery stores do not offer free food. Donations for this plugin make up a chunk of my income. If you continue to enjoy this plugin, please consider <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP-LDAP&item_number=WP-LDAP&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted" rel="nofollow ugc">making a donation</a>. 🙂 Thank you for your support!

WP-LDAP

Translates the WordPress user database to an LDAP store of the same; manage your LDAP DIT using your WordPress Dashboard.

CoSign SSO is a WordPress plugin that provides several alternative authentication methods to WordPress, and it maybe easily extend to support more SSO login methods. CoSign v2 and CoSign v3 are the first two Single Sign-on(SSO) addins, that whay this plugin named. The other login method is just a by-product which provides LDAP authentication.
When this plugin is enabled, and the login method is set to SSO, then using a external CoSign single sign-on login service. When user click login, browser will redirect to remote login url, and will redirect back after successful logged in. If set login method to LDAP, login with the familiar login screen, but authentication backend changed to LDAP.
Whether using SSO or LDAP login method, LDAP options must provided to fetch user account information. If the logged in user account does not exists, create it on the fly by default.
<h3>Settings</h3>
The settings for CoSign SSO are extremely simple. But before you change the login method to ‘SSO’ or ‘LDAP’, you mast check options for cosign and ldap carefully. Wrong configrations will ban all users including yourself!
If you cannot login any more, don’t blame me. A trick may help you:
<pre><code>$ touch <PLUGIN_DIR>/cosign-sso/FALLBACK
</code></pre>
If the fallback file contains “ldap”, “cosign2”, or “cosign3”, it will fallback to the right login method.
After you correct the settings, not forgot to remove the FALLBACK file.
Notes for CoSign 3.x:
<ul>
<li>CoSign 3.x filter needs to add a “/cosign/valid” location as cosign handler.</li>
<li>If wordpress uses a permlink, which means the RewriteRule in .htaccess may conflict with the “/cosign/valid” handler.</li>
<li>You can hack wp-includes/rewrite.php, add “RewriteRule ^cosign/valid – [L]” right after “RewriteBase” directive.</li>
</ul>
<h3>Localization</h3>
This section describes how to localized, which means let cosign-sso speak in your language.
<ul>
<li>POT file : cosign-sso/languages/cosign_sso.pot</li>
<li>Copy pot file to your locale, such as cosign-sso/languages/cosign_sso-zh_CN.pot for Chinese.</li>
<li>Translate it using your favorate editor. lokalize and kbabel are recommended.</li>
<li>Convert po to mo using command: </li>
</ul>
<pre>
 $ cd plugins/cosign-sso/languages
 $ msgfmt cosign_sso-zh_CN.po -o cosign_sso-zh_CN.mo
</pre>
<h3>Known Issues</h3>
No known issues at this time.
If you find any bugs or want to request some additional features for future releases, please log them on the wordpress project of <a href="http://redmine.ossxp.com/" rel="nofollow ugc">homepage for our interest projects</a>

CoSign Single Signon

CoSign SSO is a WordPress plugin that provides several alternative authentication methods to WordPress, and it maybe easily extend to support more SSO …

WP-LDAP vs CoSign Single Signon