NOTES ON DSEE PROTECTION
The DSEE protection mechanism for libraries and tasklists is based on the
DOMAIN operating system's protection mechanism. When you create a library or
a non-library tasklist, it acquires a default set of protection attributes
based on the initial file ACL of its parent directory. The default protection
attributes of a library's master and active tasklists are the same as the
library's.
In order to set DSEE protection attributes for a new library or non-library
tasklist, you must have initial file P (PROTECT) rights to its parent
directory.
In order to change the protection attributes of a library or a library task-
list, you must be an "administrator", as defined in those attributes. Then,
using the protect library and protect tlist commands, you can redefine the
protection attributes to prevent certain users from accessing libraries,
elements, and tasklists, and to restrict the access accorded DSEE users. (Note
that any DSEE user can issue protect library or protect tlist to simply view a
library or tasklist's protection attributes.)
protect library and protect tlist work by pairing Subject IDentifiers (SIDs)
with the following DSEE-defined user classes: non-user, reader, member, and
administrator. The rights assigned for various groups of users constitute the
"protection attributes" for the library or tasklist.
Each SID consists of person, project, organization, and node (PPON) fields.
You can use explicit identifiers for these fields, or wildcards that match
certain combinations of characters. For example, the following are both valid
SIDs:
o bob.os.r_d -- where "bob" is the person, "os" is the project,
and "r_d" is the organization.
o %.lang.% -- matches any person and organization identifiers
(because of the use of the "%" wildcards),
and the project identified as "lang".
As you know from the book, Administering Your DOMAIN System, one person may have
multiple SIDs, and use different SIDs while logged in.
The following list describes the DSEE protection classes, as applied to
libraries (protect library command):
o NON-USER has no access. A non-user is anyone whose SID is omitted
from the protection attributes or assigned explicit non-user status
in the protection attributes.
o READER can view the library and its constituent objects only.
o MEMBER can view and modify the library and its objects, but cannot
delete the library or its objects.
o ADMINISTRATOR has full access. The trusted project ADMINISTRATOR can
view the library, modify its contents, delete its contents, delete
the entire library, and change library protection.
The following list describes the protection classes as applied to tasklists
(protect tlist command):
o EXPLICIT NON-USER, whose rights are specified as NON USER. Explicit
non-users have no rights to examine, read or add to the tasklist.
If an explicit non-user attempts to add tasks via add task, the DSEE
facility will ignore his request.
o IMPLICIT NON-USER, whose SID is not listed in the protection
attributes. An implicit non-user has no rights to examine or read
the tasklist. The DSEE facility will not, however, automatically
discard add task messages sent by these users. When it receives
an add task request from an implicit non-user, the DSEE facility
asks any member or administrator of the tasklist if he wants
to receive the task. It adds the task only if that question is answered
affirmatively.
o READER. A reader can use commands that do not directly modify the
tasklist, but he cannot process tasks on the tasklist. DSEE does
not ask a reader about adding tasks from other readers or non-users,
since readers can't modify the tasklist.
o MEMBER. The member can process tasks on the tasklist, thereby
changing its contents. The DSEE facility asks members whether
they want to receive tasks that non-users and readers try to add to
the tasklist. When members send tasks to the list, the DSEE facility
places them on the list without questions.
o ADMINISTRATOR, who has full rights. The trusted administrator can
examine the tasklist, receive queries about requests to add a task
to the tasklist, process tasks, and change the protection for the
tasklist. Tasks sent by the administrator (like those sent by
members) are always added to the tasklist, without questions.
DSEE protection is on a per-library and per-tasklist basis. Thus, protection
set with protect library and protect tlist applies both to existing objects
within the library or tasklist, and to new objects as they are created. If
you try to execute a command for which you do not have proper access, the
DSEE facility will return an insufficient rights error.
For information about using the protect library and protect tlist commands,
type help protect library and help protect tlist.