Beskrivelse
This plugin adds an additional layer of protection for the wp-login.php page using HTTP Digest Authentication with the PHP header() function.
So it doesn’t require configuring web server files like .htaccess or .htdigest and works on all web hosting environments.
Important: If you already have a plugin which does HTTP Authentication please deactivate it before activating this plugin. Similarly if you have configured your web server to do HTTP authentication on the wp-login.php file please remove it before using this plugin.
If you are using FastCGI PHP this plugin may keep prompting for the credentials even if you enter the right pair, in this case use the following in your .htaccess file
<IfModule mod_setenvif.c>
SetEnvIfNoCase ^Authorization$ "(.+)" PHP_AUTH_DIGEST=$1
</IfModule>
Advantages of HTTP Digest Authentication
- Digest Authentication is very much safer than HTTP Basic Authentication whose credentials can be easily decoded with a base64 decoder.
- From Wikipedia on HTTP Basic Authentication:
The BA (Basic Authentication) mechanism provides no confidentiality protection for the transmitted credentials. They are merely encoded with BASE64 in transit, but not encrypted or hashed in any way.
- Digest Authentication on the other hand uses MD5 on the credentials making it «one way»
- Uses server and client nonces to prevent replay attacks
Features of the HTTP Digest Auth plugin
- Works using PHP header() function and doesn’t require modification of service config files (like .htaccess, nginx.conf etc)
- Supports HTTP credentials for each WordPress user
- Clears the HTTP Digest credentials when the user logs out of WordPress (more on this in the FAQ)
- Verifies if both the HTTP and WordPress credentials are of the same user (this is the default behavior and can be changed)
- Works on all major Web Servers (Tested on Apache, Nginx and Lighttpd)
Plugin Behavior
- When this plugin is activated for the first time all WordPress users will have the following Digest credentials
Username: <WordPress username>
Password: password
This can be changed from Users > Your Profile. - After activating this plugin for the first time you’ll be prompted for HTTP credentials when you logout
- Similarly if you change your HTTP username or password you’ll be prompted for this when you logout
Available languages
- Engelsk
- Serbo-Croatian by Borisa Djuraskovic
The HTTP Digest Authentication Plugin official homepage.
Skjermbilder
Logging in using HTTP digest credentials 
The WordPress login page with the HTTP username 
Setting a HTTP Digest username and password via Users > Your Profile 
Logged out of WordPress 
Trying to login with someone else’s WordPress username
Installasjon
- Unzip and upload the
http-digest-authfolder to the/wp-content/plugins/directory. - Activate the HTTP Digest Authentication plugin through the ‘Plugins’ menu in WordPress.
- Configure a HTTP username/password by going to
Users > Your Profilepage. - You’ll be prompted for these credentials when you logout after activating the plugin for the first time.
Ofte stilte spørsmål
- Installation Instructions
-
- Unzip and upload the
http-digest-authfolder to the/wp-content/plugins/directory. - Activate the HTTP Digest Authentication plugin through the ‘Plugins’ menu in WordPress.
- Configure a HTTP username/password by going to
Users > Your Profilepage. - You’ll be prompted for these credentials when you logout after activating the plugin for the first time.
- Unzip and upload the
- How does HTTP logout work?
-
When you access the wp-login.php page a portion of the realm is generated and stored in a session variable so the realm looks like «HTTP Auth Session MTM4MTc0NzU3OQ==»
When you logout of WordPress this session variable is deleted and a new realm is generated, hence the browser prompts you for credentials. - How are the HTTP Digest credentials stored?
-
The username is stored in the
wp_usermetatable in plain-text. The password is stored in a two-way encryption format in the same table. It is encrypted and decrypted with the mcrypt_encrypt() and mcrypt_decrypt() functions. - But I saw the plain-text password in my database
-
That means your PHP installation doesn’t have the mcrypt extension. To check if this is the case go to your
<?php phpinfo(); ?>and check if there is a section called mcrypt. If there isn’t one in your VPS/Dedicated server install iton Debian/Ubuntu
apt-get install php5-mcrypton Centos/Fedora
yum install php5-mcryptAfter installation change the password (or enter the same password in Your Profile) to encrypt it.
Shared hosting users needn’t worry about this as any decent host should already have this installed.
- Help! I forgot my HTTP Digest credentials
-
You can find your username by executing the following MySQL query.
SELECT meta_value FROM `wp_usermeta` WHERE meta_key = 'http-digest-auth_username' and user_id = (SELECT ID from wp_users where user_login = 'WordPress_Username');Remember to replace
wp_with your actual database prefix andWordPress_Usernamewith your login name.The password can be reset with the following query
UPDATE `wp_usermeta` SET meta_value = 'password' WHERE meta_key = 'http-digest-auth_password' and user_id = (SELECT ID from wp_users where user_login = 'admin');This will set the HTTP password to
password. Login and change it immediately. - What does the «Anyone can use these credentials» option do?
-
By default if you access the wp-login.php page using your HTTP credentials, only YOUR WordPress username can login.
This security measure can be disabled by ticking this option. - Are the HTTP credentials stored in the database even after this plugin is deactivated/deleted?
-
Deactivating this plugin doesn’t affect the credentials but deleting the plugin erases all HTTP user credentials leaving no trace of it in the database.
Vurderinger
Bidragsytere og utviklere
«HTTP Digest Authentication» er programvare med åpen kildekode. Følgende personer har bidratt til denne utvidelsen:
Bidragsytere
Oversett “HTTP Digest Authentication” til ditt språk.
Interessert i utvikling?
Bla gjennom koden, sjekk ut SVN-repositoriet, eller abonner på utviklingsloggen med RSS.
Endringslogg
1.2.1
- 3rd September 2014
- Removed
line-heightstyling on input boxes
1.2
- 26th May 2014
- Fixed bug that allowed logging in with empty credentials
- Added Serbo-Croatian language, props Borisa Djuraskovic
1.1
- 22nd March 2014
- Reduced repetitive code with inheritance
.htaccessrules for FastCGI PHP
1.0
- 16th October 2013
- Initial version