Table of Contents
the path to the tree
the authority required to authenticate access to the tree
the lists of users or groups who are permitted access when authenticated
The syntax is the same as the access control syntax used by NCSA and Apache. However, the httpd.access file only supports a subset of directives supported by NCSA and Apache. You can copy an existing NCSA or Apache access to the filer without editing or reformatting.
where Title phrase is a word or phrase that is passed to the authentication dialog as a title for the dialog that prompts the user for a password.
AuthName My private stuff
require user dole
The <Limit GET> and </Limit> directives are not supported, but are retained for format consistency with NCSA and Apache. The filer just ignores them.
The following example restricts access to the directory tree /home/htdocs/private/conspiracy to the group ``guyinblack'', which consists of the users whose IDs are cancer, deepthroat, mrx, and skinner. The authentication dialog is titled ``Area 51.''
AuthName Area 51
require group guyinblack
In this example, ``guyinblack'' is defined by the following entry in /etc/httpd.group:
guyinblack: cancer deepthroat mrx skinner
The following example requires the client to provide a Windows Domain username and password to access the directory tree /home/htdocs/win. The authentication dialog is ``Windows(tm) Authentication'' This authentication dialog, typed exactly as presented here, is required to enforce NTLM authentication.
AuthName Windows(tm) Authentication </Directory>
If this authentication control is used the Filer must have CIFS running, and either be a member of a Windows Domain or be using Local User authentication.
Table of Contents