Protect Login
Out of the box, WordPress will happily let anyone try to log in as often as they like. Type the wrong password a thousand times and it just shrugs and shows you the form again – which is exactly what someone running a brute-force script is counting on. Protect Login closes that door. It started life as a fork of Johan Eenfeldt‘s original Limit Login Attempts, a plugin a lot of us leaned on for years, and grew from there. It slows brute-force attacks to a crawl Protect Login watches failed logins per IP address. After a handful of wrong attempts that visitor has to wait before trying again, and if they keep guessing the wait grows. So a script built to try thousands of passwords ends up sitting on its hands. You decide who gets in, and who doesn’t Protect Login keeps a visible list of every address that’s currently locked out, right in the settings, and lets you release any of them with a single click. You can also keep an allowlist of addresses that skip the checks entirely (your office, your VPN’s exit node) and a blocklist of addresses that are turned away immediately. One login list, shared across all your sites If you look after more than one WordPress site – an agency, or just a small pile of your own projects — someone hammering one of them is often about to try the rest. Protect Login can link your sites together over its own Remote API: pick one site as the host, point the others at it with a URL and a key, and the block-, allow- and lockout-lists stay in sync across the lot. Block an address once and it’s blocked everywhere. And a few more things Gets the real client IP right when your site sits behind a reverse proxy or CDN — direct and proxy modes Speaks IPv6, not only IPv4 Works on Multisite, applying settings and lists across the network. Ships WP-CLI commands, so you can manage addresses and settings straight from the terminal. Lets developers set everything in code via filters — and locks the matching field in the UI, so nobody ends up fighting their own filter. Can enforce a minimum password strength for new passwords
wpDirAuth
Please see the Changelog (Development tab above) for recent updates/changes. wpDirAuth shifts authentication from the local WordPress instance to a central directory (LDAP) server(s). wpDirAuth allows users of central directory (LDAP) servers to login to authorized WordPress instances without having to register. The plugin creates a new account for each directory user on first login so that they have full access to preferences and functions, as any WP user would. Activating the plugin will not restrict you to using directory authentication and you will still be able to both create new WP-only users as well as turn on public registration in WordPress. You can also assign any privilege levels to your directory users, and the those users will be referred to their institutional password policy whenever they would normally able to update their WP passwords (on the profile screen, in user edit, etc). LDAP/LDAPS Authentication should work with most LDAP enabled directory services, such as OpenLDAP, Apache Directory, Microsoft Active Directory, Novell eDirectory, Sun Java System Directory Server, and more. wpDirAuth supports LDAP and LDAPS (SSL) connectivity and can force SSL for WordPress authentication if it is available on the Web server. It also supports server connection pools, for pseudo load balancing and fault tolerance, or multiple source directory authentication. Because the key used to locate a user’s profile in the LDAP server is not always the same, depending on your LDAP server type and institutional choices, you can define your own through the wpDirAuth administration tool. When logging in as a directory user, the WP “remember me” feature is downgraded from 6 months for regular WP users to only 1 hour, so that institutional passwords are not overly endangered when accessing WP from public terminals. Branding & Notifications You can define notifications addressed to your directory users in key WordPress areas, such as the login screen and the profile edit screen. Since these admin-editable values support HTML (admin, coders, beware of xss!), you can point your directory users to central support information related to functions such as changing their institutional password, a WordPress usage related policy, etc. There is also a simple and optional terms of services concept, only implemented for directory users, which will simply record a one-time acceptance date when agreed upon. Note that agreeing to the TOS has no effect on the user’s level of access in the system, fact which could change in future version if there is a demand for it, or through direct code contribution to that effect. Using wpDirAuth Once installed and activated, you will be able to administer your directory settings through the dedicated plugin configuration tool found under the wpDirAuth menu found in the WordPress Settings admin section. Directory Authenticated users can now be pre-added to your wordpress system and granted roles by going to the Add Dir Auth User menu found in the WordPress Users admin section. Contextual help for this section is available for this section within WordPress’ built-in help menu. See the inline help found in the tool for more information on the settings. There is a secondary activation toggle, so you can install and activate the plugin, check out the options panel, but not immediately accept directory authentication, or even simply turn the feature on or off at any time. Help and Support Please post questions, request for help to the WordPress plugins forum or email wpdirauth@gilzow.com. Please be sure to include ‘wpdirauth’ in the subject line. TO-DO’s Internationalization Refactor to a class More action/filter hooks Source and Development wpDirAuth welcomes friendly contributors wanting to lend a hand, be it in the form of code through SVN patches, user support, platform portability testing, security consulting, localization help, etc. The [current] goal is to keep the plugin self-contained (ie: no 3rd-party lib) for easier security maintenance, while keeping the code clean and extensible. Focus is on security, features, security, and let’s not forget, security. Unit tests will hopefully be developed and constant security audit performed. Recurring quality patch contributions will lead to commit privileges to the project source repository. Please post questions/requests for help to the wordpress forums and/or email wpdirauth@gilzow.com License General Public License Copyrights are listed in chronological order, by contributions. wpDirAuth: WordPress Directory Authentication, original author Copyright (c) 2007 Stephane Daury – http://stephane.daury.org/ wpDirAuth and wpLDAP Patch Contributions Copyright (c) 2007 PKR Internet, LLC – http://www.pkrinternet.com/ wpDirAuth Patch Contributions Copyright (c) 2007 Todd Beverly wpLDAP: WordPress LDAP Authentication Copyright (c) 2007 Ashay Suresh Manjure – http://ashay.org/ wpDirAuth Patch Contribution and current maintainer Copyright (c) 2010-2017 Paul Gilzow – http://gilzow.com/ wpDirAuth is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation. wpDirAuth is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. Project History Originally started from a patched version of wpLDAP (1.02+patch), wpDirAuth has since then been heavily overhauled and features have been modified and added. In other words, a classic case of pimp my lib' (hopefully for the better). * Current: wpDirAuth: http://wpdirauth.gilzow.com/ * Original: wpLDAP: https://wordpress.org/plugins/wpldap/ * wpLDAP Patch: https://web.archive.org/web/20100731020249/http://www.pkrinternet.com/~rbulling/private/wpLDAP-1.02-ssl.patch
