Sync your WordPress users with .htpasswd file for enabling Apache basic authentication based on file for your resources
Screenshots
Htpasswd Generator settings page
FAQ
How WordPress users are synchronized with *.htpasswd_generated* file?
This plugin hooks to some WordPress Actions involving user’s creation, update or deletion, such as:
- user_register
- profile_update
- delete_user
- password_reset
After plugin activation, only new users or updated users can access protected resources, why?
WP user’s passwords are hashed before storing on db, so they cannot be reverted to plain text for security reason. Apache basic authentication based on file expects a different type of password hashing, so this plugin cannot use WP hashed version but has to catch and hash user’s password before they are hashed from WP. Unfortunately, the only way to sync .htpasswd_generated
with existing users is to update their password (even with same value) from admin panel or from reset password functionality so it can be caught and hashed when still plain text.
Is it opensource?
You can fork, edit and pull request sources from GitHub
ChangeLog
1.1.2
- No new feature. Just needed to meet WordPress update system
1.1.1
- Fixed issue #1: switched encryption algorithm to APR1-MD5, compatible with Apache 2.2.18 and above, both on Linux and Windows
1.1.0
- Automatic folder protection: now in new settings page you can specify folders path you want to protect: no more need to move and rename
rename_me_to_.htaccess
manually!
- New FTP upload feature: if you need to protect a remote resource (on another server than WordPress installation), you can upload
.htpasswd_generated
automatically via FTP to another server. Remember to configure .htaccess
file properly on remote server.