Security - eXist: A NoSQL Database and Application Development Platform - page 151

Managing Permissions
When resources are added to the database, the owner of those resources is the user
adding the resources, the group of those resources is the primary group of the user
adding the resources, and the mode is calculated from default permission modes sub‐
ject to the user's umask, as described in “User masks” on page 139 .

You may modify the permissions of a resource in the database at any time provided
you have the appropriate rights to modify the permissions of that resource. Table 8-8
shows the ownership and group membership requirements for modifying the per‐
missions of a collection or resource.

Table 8-8. Requirements to modify permissions

Action Collection modification requirement Resource modification requirement

Change owner

• Member of the dba group • Member of the dba group

Change group Either: Either:

• Owner and member of the destination group • Owner and member of the destination group

• Member of the dba group • Member of the dba group

Change mode Either: Either:

• Owner • Owner

• Member of the dba group • Member of the dba group

Tools for Permission Management
As with managing users and groups, there are a number of approaches to managing
permissions in eXist.

Using the Java Admin Client
The Java Admin Client (see “The Java Admin Client” on page 29 ) provides an excel‐
lent facility for modifying the permissions of collections and resources in the data‐
base. This is the tool we will focus on in “Permission Management with the Java
Admin Client” on page 154 . The “Resource properties” option on the File menu in the
Java Admin Client opens the permissions management screen shown in Figure 8-13 .