Sun Microsystems Netscape Enterprise Server, Administrator'S Manual

Page: 357 / 532

Chapter 14, Controlling Access to Your Server 357
Access Control For Web Publishing
You might want to select the entire text element and copy to memory—if
there are errors, you’ll have to reenter the text. Click Update. The top frame
will display “Unrecognized expressions” in the Users/Groups and From
Host fields because you created a custom expression.
9.
Click Submit. If you made any errors in the custom expression, you’ll get a
JavaScript alert. Correct any changes and click Submit again.
Restart your server for the changes to take effect.
Access Control For Web Publishing
Web Publisher users can control who accesses their Web Publisher documents
and directories and what operations different users or different groups of users
can perform upon the files. They can also completely prohibit access to a file or
folder or you can restrict access to certain authenticated users.
The access control system supports a special user called owner . When an ACL
rule designates the user to be the owner, the permissions defined by this rule
apply to the owner assigned by Web Publisher for each document.
Only the owner can modify the access control (ACL) rules for a file. These rules
define the actions users can perform on the file, such as moving, copying,
renaming, or deleting it. An owner can reassign ownership of a file to another
user, and if a file has no owner, anyone with a valid username can identify
themselves as its owner. Because the username identified as the owner of a file
can change, any access control that you place on a file should target the owner
of a file rather than a specific username.
If the default access control (ACL) that governs your server is not restrictive or
flexible enough for your web publishing needs, you can use the Restrict Access
function (choose Server Preferences and click the Restrict Access link) to create
an ACL that is more appropriate for web publishing.
For example, you could create an ACL like this:
acl "uri=/publisher/";
allow (read, execute, list, info) user = anyone;
allow (write, delete) user = owner;