Use your existing LDAP as authentication-backend for your wordpress!

So what are the differences to other WordPress-LDAP-Authentication-Plugins?

  • Flexible: You are totaly free in which LDAP-backend to use. Due to the extensive configuration you can freely decide how to do the authentication of your users. It simply depends on your filters
  • Independent: As soon as a user logs in, it is added/updated to the WordPress’ user-database to allow wordpress to always use the correct data. You only have to administer your users once.
  • Failsafe: Due to the users being created in WordPress’ User-database they can also log in when the LDAP-backend currently is gone.
  • Role-Aware: You can map WordPress’ roles to values of an existing LDAP-attribute.

For more Information on the configuration have a look at


  1. Upload the extracted folder authLdap to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Configure the Plugin via the ‘authLdap’-Configuration-Page.


Where can I find more Informations about the plugin?

Go to

Where can I report issues with the plugin?

Please use the issuetracker at

Where can I report sensitive security issues with the plugin?

In essence: Report a security vulnerability at

Please see for more details


2022 年 6 月 28 日
I use it since 2 years for an Intranet an it work fine. I was afraid it was broken for WP 6.0 but, it is something else who went wrong in my functions.php Tested with success on Wordpres 6.0
2022 年 1 月 15 日
Very flexible plugin, stable codebase, excellent documentation. I especially like the clean configuration interface, which enables me to set the LDAP search filters easily. Plus, you don’t really have to do much – the default settings are what you need when authenticating against an openLDAP instance.
閱讀全部 19 則使用者評論






任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄



  • Fix issue with Groups not being updated on existing accounts (see for details)


  • Fix reducing assigned WordPress roles to single role on login when WordPress roles shall be kept
  • Add Behavioural testing and first 3 scenarios


  • Adds information about security-contacts
  • Addresses CVE-2023-41655


  • Fix regression from 2.5.7


  • Fix regressions from 2.5.4
  • Fix CI system


  • Update Tested up to


  • Fix issue with broken role-assignement in combination with WooCommerce
  • Fix spelling issue
  • Allow DN as role-definition


  • Ignore the order of capabilities to tell the role. In addition the filter editable_roles can be used to limit the roles


  • Fix issue with running on PHP8.1


  • Improve group-assignement UI


  • Make textfields in settings-page wider


  • Replace deprecated function
  • Fix undefined index
  • Add filter for retrieving other params at login (authLdap_filter_attributes)
  • Add do_action after successfull login (authLdap_login_successful)


  • Allow to use environment variables for LDAP-URI configuration


  • Allow to not overwrite existing WordPress-Users with LDAP-Users as that can be a security issue.


  • Add search-base for groups. This might come in handy for multisite-instances


  • This new release adds Multi-Site support. It will no longer be possible to use this plugin just in one subsite of a multisite installation!
  • Adds a warning screen to the config-section when no LDAPextension could be found
  • Fixes an issue with the max-length of the username


  • Fixes an issue with escaped backslashes and quotes


  • Allows parts of the LDAP-URI to be URLEncoded
  • Drops support for PHP 5.4


  • Allows multiple LDAP-servers to be queried (given that they use the same attributes)
  • Fixes issue with URL-Encoded informations (see


  • Adds support for TLS


  • Update to showing password-fields check (thanks to @chaplina)


  • Removed generation of default email-address (thanks to @henryk)
  • Fixes password-hashing when caching passwords (thanks to @litinoveweedle)
  • Removes the possibility to reset a password for LDAP-based users (thanks to @chaplina)
  • Removes the password-change-Email from 4.3 on (thanks to @litinoveweedle)
  • Fixes double authentication-attempt (that resulted in failed authentication) (thanks to @litinoveweedle)


  • Cleanup by removing deprecated code
  • Fixes issues with undefined variables
  • Enables internal option-versioning
  • Setting users nickname initially to the realname instead of the uid
  • Fixes display of password-change possibility in users profile-page


  • Fixed an issue with changing display name on every login
  • Use proper way of looking up user-roles in setups w/o DB-prefix


  • Updated version string


  • Use default user to retrieve group menberships and not logging in user.
  • return the UID from the LDAP instead of the value given by the user
  • remove unnecessary checkbox
  • Adds a testsuite
  • Fixes PSR2 violations



  • Fixed an issue with group-ids
  • Moved the code to GitHub (


  • Changed the login-process. Now users that are not allowed to login due to
    missing group-memberships are not created within your blog as was the standard
    until Version 1.0.3 – Thanks to
  • Changed the default mail-address that is created when no mail-address can be
    retrieved from the LDAP from to $ so that
    a new user can be created even though the mail address already exists in your
    blog – Also thanks to
  • Added support for WordPress-Table-prefixes as the capabilities of a user
    are interlany stored in a field that is named “$tablePrefix_capabilities” –
    again thanks to and also to sim0n of