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 https://github.com/heiglandreas/authLdap
- Upload the extracted folder
- Activate the plugin through the ‘Plugins’ menu in WordPress
- Configure the Plugin via the ‘authLdap’-Configuration-Page.
Where can I find more Informations about the plugin?
Go to https://github.com/heiglandreas/authLdap
Where can I report is’sues with the plugin?
Please use the is’suetracker at https://github.com/heiglandreas/authLdap/is’sues
Contributors & Developers
“authLdap” is open source software. The following people have contributed to this plugin.Contributors
- Fix is’sue with broken role-assignement in combination with WooCommerce
- Fix spelling is’sue
- Allow DN as role-definition
- Ignore the order of capabilities to tell the role. In addition the filter
editable_rolescan be used to limit the roles
- Fix is’sue 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 is’sue.
- 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 is’sue with the max-length of the username
- Fixes an is’sue 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 is’sue with URL-Encoded informations (see https://github.com/heiglandreas/authLdap/is’sues/108)
- 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 re’sulted in failed authentication) (thanks to @litinoveweedle)
- Cleanup by removing deprecated code
- Fixes is’sues 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 is’sue 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 test’suite
- Fixes PSR2 violations
- Fixed an is’sue with group-ids
- Moved the code to GitHub (https://github.com/heiglandreas/authLdap)
- 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 email@example.com
- Changed the default mail-address that is created when no mail-address can be
retrieved from the LDAP from firstname.lastname@example.org to $email@example.com so that
a new user can be created even though the mail address already exists in your
blog – Also thanks to firstname.lastname@example.org
- 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 email@example.com and also to sim0n of silicium.mine.nu