Restricting Access to Web Pages

If you have content in your webspace that you want to restrict to specifc users or groups, you can use a .htaccess file to control access.

You can (and should) also ensure people use HTTPS connections, for better security.

There are several ways of securing your page - read the examples section to see some more complete examples that put everything together.

Creating a .htaccess file

Directives for controlling access should be put in a file called .htaccess inside the directory you want to protect.

Note that .htaccess directives don't affect parent directories - place them at the highest level you want them to control.

The file needs to be readable by the w3serv user; in most cases, this means making the file world-readable (eg. mode 644).

The directory it lives in, and all its parents up to your home directory, also need to be executable-by-others, (eg. mode 0711 or better.)

If the web server can't read the .htaccess file, it will deny access to the entire directory and any subdirectories below it.

Controlling access to specific files

By default, a .htaccess file is applied to the whole directory it lives in, and all sub-directories.

To limit restrictions to a specific file, put them inside a <Files> directive.

For example, you only want to restrict access to a "secure.html" page:

Requiring HTTPS

These days, virtually all web pages should use encrypted connections unless there's a specific reason not to.

This is especially true for password-protected pages - even for trivial pages, you should make sure that passwords are never transmitted in cleartext.

To require HTTPS for a directory, put the following snippet in your .htaccess file:

If the page isn't being accessed over HTTPS, it will redirect the browser to the HTTPS version of the site.

If you're using a Personal Domain or CGI Scripts, you will need to change www to username.web or cgi respectively.

It's important that you put any other directives inside the second IfModule section, to ensure that all authentication happens over HTTPS.

Password protection

There are two main ways of implementing password protection: with your own manually-maintained password file, or using CSE account authentication.

Using a password file

The simplest form of password-based access control is to list usernames and encrypted passwords in a file. Typically, this file is called .htpasswd.

For this example, assume that you're restricting the secure directory, so you're working inside /web/username/secure/:

$ cd /web/username/secure/

First, you need to create the password file - this doesn't have to be in the same directory, but often is...

We can do this using the htpasswd command (-c means create).

First we create a user called "bob".

Now the bob user is there. You can add other users the same way but without -c.

Next, you need to tell the web server to restrict access based on that file.

Add this to .htaccess (within the <IfModule mod_ssl.c> section)

This lets any user in the .htpasswd file get access.

You can limit access to specific users in the file by using require user username1 username2 ... instead of require valid-user.

Using zID and zPass

Alternatively, you can authenticate users with their zID and zPass:

This will grant access to any valid CSE user.

To restrict access to specific users, use require user user1 user2 user3 ...

Note that users need to have an account at CSE as well as a working zID.

User groups

To restrict to users in given account class, say COMP1234, you can use require group @COMP1234

This will allow all teachers and students of COMP1234 in the current session

Some frequently-used classes include:

• Staff and equivalent: @Employee @Visitor @Conjoint
• Subject: @COMP1234
• Subject teachers (not students): @COMP1234_Teacher

If you want to restrict access to people in a specfic unix group, say csg, use:

Preventing filesystem access

Files in your webspace normally need to be world-readable so that the webserver can access them.

This means that any users on CSE systems will have access to the underlying files as well.

If you want to ensure that random CSE users won't have access to your content, you will need to lock down the file permisions, while still granting access to the webserver.

You can do this with the priv webonly command, which makes a directory group-owned by the webserver, so that only you and the webserver can get inside it through the normal unix filesystem.

Usage:

For more complete information on how this works, run priv help webonly.

Note that this only applies to static content - PHP and CGI scripts only need to be user-readable, so you can simply chmod 600 secretfile.php and it will work the way you need it to.

Host-based access

You can restrict based on the IP address or domain name that the user is coming from:

This will only allow people to access the page if their computer's domain name ends in .unsw.edu.au.

Alternatively, you can restrict access by IP range:

Examples

Restrict a directory to course students only

Restrict access to any valid CSE user and associated zPass authentication

Require a password on a CGI script

• A single file only is restricted (secure.cgi)
• The SSL redirection is to cgi instead of www because it is a CGI script
• This uses a password file instead of zID authentication

See Also

• World Wide Web - WWW FAQs
• .htaccess files - use and configuration of .htaccess directives
• man htpasswd or man apache (on a linux machine)
• Apache Server Documentation Project (particularly the Apache 1.3 auth section).