Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 334 / 532

Restricting Access to Your Web Site
334 Netscape Enterprise Server Administrator’s Guide
# The following ACL rule denies everyone not in the directory
# server and everyone in the directory server except for
# GroupA and GroupB access to the directory “my_stuff”
acl "path=/export/user/990628.1/docs/my_stuff/";
authenticate (user,group) {
database = "default";
method = "basic";
};
deny (all)
(user = "anyone");
allow (read,execute,list,info)
(group = "GroupA,GroupB");
If someone requests the following URL:
http:// server_name /my_stuff/web/presentation.html
The server would first check access control for the entire server. If the ACL for
the entire server was set to continue, the server checks to see if there is an ACL
for the file type (
*.html
). Then, it checks for an ACL for the directory,
my_stuff
. If one exists, it checks the ACE and then moves on to the next
directory. The server continues traversing the path either until it reaches an ACL
that says not to continue or until it reaches the final ACL for the requested URL
(in this case, the file
presentation.html
).
To set up access control for this example using the Server Manager, you could
create an ACL for the file only or for each resource leading to the file. That is,
one for the entire server, one for the
my_stuff
directory, one for the
my_stuff/web
directory, and one for the file.
Restricting Access to Your Web Site
This section takes you through the process of restricting access to the files or
directories on your web site. The sections following this one describe in detail
each option available when using access control. Keep in mind that most
access control rules use only a subset of the available options.
You can set access control through two Enterprise Server mechanisms, both
offer flexibility in the scope of your desired settings: