StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>My company uses WordPress and MediaWiki internally and we use HTTP_AUTH access control to create a "single sign on". As we add more applications, we simply integrate them into the HTTP_AUTH system where practical. For security, you can run HTTP_AUTH over SSL. The basic steps are:</p> <p>Configure the .htaccess to specify the authentication type. We use MySQL in production but you could have a simple htpasswd file.</p> <p>In the WordPress directory's .htaccess file add the following:</p> <pre> <Files wp-login.php> AuthType Basic AuthName "Restricted Access" AuthUserFile /some/path/to/htpasswd Require valid-user </Files> </pre> <p>In the WordPress wp-admin/ directory's .htaccess add the following:</p> <pre> AuthType Basic AuthName "Restricted Access" AuthUserFile /some/path/to/htpasswd Require valid-user </pre> <p>In the MediaWiki directory's .htaccess file add the following:</p> <pre> AuthType Basic AuthName "Restricted Access" AuthUserFile /some/path/to/htpasswd </pre> <p>Then install the <a href="http://www.mediawiki.org/wiki/Extension:HttpAuth" rel="nofollow noreferrer">HttpAuth</a> extension for MediaWiki and the <a href="http://wordpress.org/extend/plugins/http-authentication/" rel="nofollow noreferrer">HTTP Authentication</a> plugin for WordPress and configure. We had to make some slight modifications to the MediaWiki extension as our hosting environment does not provide mod_php but if you have mod_php it will work out of the box.</p> <p>Note that our environment is a private intranet so everyone is authenticated. The above .htaccess files will work for publicly viewable blogs but some additional tweaking may be required for the MediaWiki .htaccess depending on whether you want everyone to be required to be authenticated or not and if the site is publicly available.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload