{"id":583,"date":"2011-07-19T17:17:44","date_gmt":"2011-07-20T00:17:44","guid":{"rendered":"http:\/\/hybridclassroom.com\/blog\/?p=583"},"modified":"2011-09-08T19:40:11","modified_gmt":"2011-09-09T02:40:11","slug":"how-to-password-protecting-a-website-directory-with-htaccess","status":"publish","type":"post","link":"https:\/\/www.hybridclassroom.com\/blog\/?p=583","title":{"rendered":"How-To: Password Protecting a Website Directory with .htaccess"},"content":{"rendered":"

How-To: Password Protecting a Website Directory with .htaccess<\/p>\n

by Richard White<\/p>\n

2011-07-19<\/p>\n

A friend of mine who maintains a website for his classes recently asked me how to go about creating a password-protected folder for the site. He wants to store materials on there that would be accessible to his students who would use a Name and Password to browse the folder.<\/p>\n

In other words, when a user tries to go to a certain location on this teacher’s website, he wants them to have to authenticate with a Name and Password before they’ll be allowed to enter the site.<\/p>\n

\"\"<\/a><\/p>\n

Here’s how you password protect a folder, in three easy steps.<\/p>\n

1. Create the folder that will store the protected material.<\/h3>\n

For our example, we’ll assume that my account on the webserver is called rwhite<\/i>, and the website files are all stored in public_html<\/i>. In that directory public_html<\/i>, create a new directory “secretstuff”, which is where we’ll be storing our password-protected materials. This folder should have a permission of 755.<\/p>\n

(There are lots of different ways to “create a folder”, depending on how you manipulate files on your server. You might ssh<\/i> in to the server, you might use Dreamweaver or Coda, … If you’re not sure how to manipulate files and directories on your server, learn how to do that first and then come back here!)<\/p>\n

So in terms of your websites directory structure, here’s what we have so far (your files and directories will look different from mine–the ones shown are for example only):<\/p>\n

\r\n\/\r\n|---home\/\r\n    |---rwhite\/\r\n\t|---logs\/\r\n        |---mail\/\r\n        |---public_ftp\/\r\n        |---public_html\/\r\n\t    |---about.html\r\n            |---index.html\r\n            |---secretstuff\/\r\n<\/pre>\n
2. Use a text editor to create a text file called “.htaccess” in the folder that you want to protect.<\/h3>\n
To keep unauthorized users from peeking inside the directory secretstuff<\/i>, you’ll need to add two additional files to your website that will instruct the server under what conditions it should display the contents.<\/p>\n
The first file is a text file called .htaccess<\/i> that is stored in the secretstuff<\/i> directory. Note that this filename doesn’t really have a name—it only has an extension (the eight letters after the period). That means that this file won’t show up in most directory listings unless you specifically tell your computer to list ALL files.<\/p>\n
Use a text editor<\/a>—Notepad, TextWrangler, BBEdit, TextMate, vi, emacs, nano, edit, whatever—to create the .htaccess<\/i> file in the secretstuff<\/i> directory. The file .htaccess<\/i> should include these four lines:<\/p>\n
\r\nAuthName \"Secret Stuff\"\r\nAuthType Basic\r\nAuthUserFile \"\/home\/rwhite\/.htpasswds\/public_html\/secretstuff\/passwd\"\r\nRequire valid-user\r\n<\/pre>\n
Be sure to save the file with the name .htaccess<\/i> (including the period in front!). That file should have permissions 644.<\/p>\n
What does all of that mean?<\/p>\n
First of all, .htaccess<\/i> is used by the Apache web server to do all sorts of things on your website, and you probably already have a few .htaccess files sprinkled here and there on your site—we don’t want to mess with those. This particular .htaccess file in the secretstuff directory is simply being used to control access to that directory.
\nThe four lines in that file, in order, say:<\/p>\n
    \n
  1. Display this name in the authentication dialog box.<\/li>\n
  2. Use Basic http authentication.<\/li>\n
  3. Find the file containing passwords at this location on the server (see step 3 below).<\/li>\n
  4. Make sure user has been authenticated before giving them access to this folder.<\/li>\n<\/ol>\n
    The only really tricky part about this step is the location of the password file. Note that the .htpasswds<\/i> directory listed here is NOT contained in \/home\/rwhite\/public_html—placing that directory in a publicly-accessible folder is a security risk. Instead, the .htpasswds<\/i> directory is contained in \/home\/rwhite<\/i>, which is not accessible by a browser. That location IS accessible to Apache, however, which will look at that location to find out which users will provide what passwords in order to gain access to the protected folder.<\/p>\n
    So here’s what we’ve got now:<\/p>\n
    \r\n\/\r\n|---home\/\r\n    |---rwhite\/\r\n\t|---logs\/\r\n        |---mail\/\r\n        |---public_ftp\/\r\n        |---public_html\/\r\n\t    |---about.html\r\n            |---index.html\r\n            |---secretstuff\/\r\n\t\t|---.htaccess\r\n<\/pre>\n
    3. Use a text editor to create the text file called “passwd” that we’ll place in the .htpasswds directory.<\/h3>\n
    As discussed above, the passwd<\/i> file will be be located someplace where a browser can’t get to it. Here’s where we’re going to put it.<\/p>\n
    \r\n\/\r\n|---home\/\r\n    |---rwhite\/\r\n\t|---.htpasswds\r\n\t    |---public_html\r\n              \t|----secretstuff\r\n\t\t    |---passwd\r\n        |---logs\/\r\n        |---mail\/\r\n        |---publc_ftp\/\r\n\t|---public_html\/\r\n            |---about.html\r\n            |---index.html\r\n\t    |---secretstuff\/\r\n\t\t|---.htaccess\r\n<\/pre>\n
    Note that if you don’t already have a directory called .htpasswds<\/i>, you’ll need to create it, and then nest inside it the public_html<\/i> and secretstuff<\/i> directories. (Although some tutorials will instruct you to place a single .htpasswd file in those location, creating a directory will give you more flexibility later on, should you choose to create additional .htaccess authentications.) The .htpasswds<\/i> directory and those nested inside it should all have permissions of 644, as should the passwd<\/i> file itself.<\/p>\n
    Now, what actually goes IN the passwd<\/i> file? For our purposes, it’s going to consist of a single line: the Name, a colon, and then the Password that a user will need to get into the password-protected secretstuff<\/i> directory.<\/p>\n
    Assuming we want to allow ImaStudent<\/i> to access the directory using a password of 123456<\/i> (not a very good password, obviously), that one line in the file passwd<\/i> will contain both of those pieces of information, and look like this:<\/p>\n
    \r\nImaStudent:EdQXJLHVRhCFo\r\n<\/pre>\n
    Whoa, whoa, whoa. Where did EdQXJLHVRhCFo<\/i> come from? That doesn’t look like our password 123456<\/i> at all.<\/p>\n
    That’s because EdQXJLHVRhCFo is an htpasswd “hash” of 123456. Apache is so security-conscious that it doesn’t even want to know what your real password is—it only wants to store a “hash”, or one-way coded version, of that password. When a user enters their password into the authentication box, that hashed password (the EdQXJLHVRhCFo, converted from 123456) will be compared to the hashed version in your passwd<\/i> file.<\/p>\n
    So how do you know what hash to include in your passwd<\/i> file?<\/p>\n
    There are a few ways to do this. One way is to go to a website like this one<\/a> and enter your password into the indicated field.<\/p>\n
    Or, if you wish to do it yourself on the computer, open up a Terminal and on the command line, type<\/p>\n
    \r\n$ htpasswd -ndb ImaStudent 123456\r\n<\/pre>\n
    …and you’ll get a line that you can paste into your passwds<\/i> file.<\/p>\n
    Once you’ve got everything put together, try going to the page that you’ve created and see if you can see anything. If all works as planned, you’ll be confronted by a dialog box that looks something like this.<\/p>\n
    \"\"<\/a><\/p>\n
    By typing in the appropriate Name and Password, the browser should proceed to display the previously hidden contents of that folder!<\/p>\n
    There’s one more thing you may need to take care of, however, depending on how you want to use the new secretstuff<\/i> folder. If you’re going to use it to serve up regular webpages like index.html<\/i> then you’re all done: once a user’s attempt to access the directory is authenticated, those pages will appear just as in any other directory.<\/p>\n
    \"\"<\/a><\/p>\n
    You may, however, wish to just dump a bunch of files into that folder that students can access. They might be text files, or Word documents, or graphics. If this is the case, it may also be that your webserver doesn’t by default allow these files to be “indexed,” or listed, and you’ll get an error message like the one above.<\/p>\n
    This is easily fixed. In your .htaccess<\/i> file—the same one that we were working on in step 2 above—add a fifth line:<\/p>\n
    \r\nAuthName \"Secret Stuff\"\r\nAuthType Basic\r\nAuthUserFile \"\/home\/rwhite\/.htpasswds\/public_html\/secretstuff\/passwd\"\r\nRequire valid-user\r\nOptions +Indexes\r\n<\/pre>\n
    This line will allow this directory’s contents to be Indexed, or listed, even if there aren’t any html<\/i> files to be displayed.
    \n    \"\"<\/a><\/p>\n
    Now students are able to view or download those files simply by clicking on them in the browser window.<\/p>\n","protected":false},"excerpt":{"rendered":"
    How-To: Password Protecting a Website Directory with .htaccess by Richard White 2011-07-19 A friend of mine who maintains a website for his classes recently asked me how to go about creating a password-protected folder for the site. He wants to store materials on there that would be accessible to his students who would use a … Continue reading How-To: Password Protecting a Website Directory with .htaccess<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[70,75,79],"tags":[],"_links":{"self":[{"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/583"}],"collection":[{"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=583"}],"version-history":[{"count":40,"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/583\/revisions"}],"predecessor-version":[{"id":684,"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/583\/revisions\/684"}],"wp:attachment":[{"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=583"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=583"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hybridclassroom.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=583"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}