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

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

Access Control For Web Publishing
358 Netscape Enterprise Server Administrator’s Guide
This ACL sets a restriction such that only the owner of a file within the
additional document directory of
/publisher
can modify or delete the file.
Note
For Unix, if you expect web publishing users to publish documents to a
directory, you need to set the Unix file permissions to give them write access to
that directory. You should also disable write permissions for directories you do
not want them to publish to.
Web Publisher has many operations that are restricted to the broad category of
valid server user. Many ACL rules, such as that for agents services, simply
require a user to be valid for the server. That is, users who are defined in the
server’s users database.
When you start Web Publisher, you are immediately prompted with the user
name authorization dialog box. You can leave this blank and operate as an
anonymous user, but as soon as you attempt to perform an operation restricted
to a valid user, you are again prompted for your user name. At this point, you
are also asked to enter your password, and only authenticated users can
continue with the operation.
Ownership of Files and Folders
Web Publisher files and folders can be owned by individual users. Only the
owner of a file or folder can define its access control definitions or reassign its
ownership. If a file or folder has no owner, no one can modify its access
control. You can define an access control definition that restricts certain
operations to the user who is the current owner of a file or folder, even when
ownership is reassigned.
Your can do a bulk ownership assignment for your Web Publisher users, and
the users can assign ownership for an individual file or folder through the Web
Publisher properties page, or they can become the owner of a file or folder as a
result of an automatic assignment by Web Publisher when you perform certain
actions.