Just because your web page is on the Intranet, that doesn't mean that the whole world can see it. Web pages, like any other files on the Intranet, have "access controls" that tell the web server who gets to see them.
This tutorial will present the basic priciples of access control, and a simple approach for managing access controls for both a user directory and a group directory. It will also provide some tips for experienced users.
Each person with an Intranet account is a user. Each user can be a member of one or more groups. For example, almost all users are a member of the group csupomona, which is the group of campus intranet users. Some groups are automatically created and others have users added manually. If you have an Intranet user name and password, you can view all the groups.
There is a special "group", Internet, which indicates that a file is accessible to everyone in the world with internet access.
Files on the Intranet are contained in directories (also called "folders" on Windows and Mac). There are three things you can do to a directory:
Each of these privileges can be given to users or groups.
For viewing web pages, none of these are technically necessary (the web server can find any page with "search" permitted—the default—even if it can't read the directory), but the method outlined below allows users to see listings of directories that contain web pages.
For creating or editing web pages, all three privileges are necessary
There are three things you can do with a file:
Again, all these privileges can be given to users and groups.
For viewing web pages, only "read" access is necessary. You might think that "write" access would be necessary to edit an existing web page, but this isn't always true—some web page editors delete the old file and insert the new edited file, which requires insert and delete access to the directory, but not write access to the file.
When a file is read-permitted to the Internet, anyone can go to it in a web browser and view it. If it is not permitted to the Internet, anyone attempting to view it will get a dialog box asking for his/her BroncoName and BroncoPassword. When a person's BroncoName and BroncoPassword are submitted, one of three things will happen:
As you can see, web pages should ordinarily be set so that the Internet can read them, unless you specifically need to restrict access to certain users or groups.
By default, all files and directories in a user directory will be accessible only to the user. The steps below will set up your user directory to hold web pages accessible to the world, and leave the possibility of restricting some of them later on.
If you have already set permissions in your user directory using a method other than the one above, going back and using it could cause some of your settings to break. One approach is to use the "long form" (see below. Also view detailed User Directory Configuration instructions):
By default, files and directories in a group directory can be read by anyone on the internet, and can be modified by any member of the group.
To restrict access to specific files or directories:
The interface described above is for setting basic permissions; it is often called the "short form". By clicking on the downward-pointing triangle below the right edge of the table, you can open the "long form", which lets you change more settings, including the ability to permit others to control the access to files and directories, and in the case of individual files, to control their ability to execute. Use of the "long form" is beyond the scope of this tutorial, but there are detailed User Directory Configuration instructions available through Intranet Services.
Scripts in your cgi-bin may require specific permissions to run correctly, and setting permissions globally using the "short form" may reset them, causing them to break. For example, some CGI scripts require that users have insert and delete access to a directory, or write access to a file, and both of these are turned off in the default configurations explained above.
If you are used to using chmod in the Unix shell to control file access, please instead use aclmod on the Intranet; it gives full control over file access. Enter aclmod -h at the shell prompt for help.