<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://build2be.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>build2be/com/e - basic auth</title>
 <link>https://build2be.com/category/basic-auth</link>
 <description></description>
 <language>en</language>
<item>
 <title>Temporary Securing Drupal through Basic Auth in settings.php</title>
 <link>https://build2be.com/content/temporary-securing-drupal-through-basic-auth-settingsphp</link>
 <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot;&gt;&lt;p&gt;We needed to protect our production site from prying eyes for a while with a basic authentication. Using apache basic auth settings seemed not enough. Or actually was too much. We wanted the theme to blend in. So these files were not supposed to get protected. Only our Drupal pages should.&lt;/p&gt;
&lt;p&gt;The solution came from &lt;a href=&quot;http://php.net/manual/en/features.http-auth.php&quot;&gt;http://php.net/manual/en/features.http-auth.php&lt;/a&gt;. Adding the following to sites/default/settings.php makes the customer happy and drush too.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
 <pubDate>Tue, 15 Jun 2010 08:35:32 +0000</pubDate>
 <dc:creator>clemens</dc:creator>
 <guid isPermaLink="false">104 at https://build2be.com</guid>
 <comments>https://build2be.com/content/temporary-securing-drupal-through-basic-auth-settingsphp#comments</comments>
</item>
</channel>
</rss>
