This policy enforcement point (PEP) makes decisions based on the four basic roles of "metadata reader", "reader", "writer", and "admin". These roles are assigned to principals on Fedora objects and datastreams. Assigned roles are inherited through the repository tree until blocked by another assignment.

This PEP makes use of the Access Roles Module to assign and query roles in the repository.

Roles

• metadata reader - can retrieve information about Fedora objects, but cannot retrieve content
• reader - can retrieve information about Fedora objects, including content
• writer - all permissions of reader; can create, modify and delete Fedora objects
• admin - all permissions of writer; can modify the roles assigned to Fedora objects

Policy

The permissions granted to these roles are fixed. This PEP makes decisions in Java code, rather than consulting any kind of declarative policy. If more nuanced roles or policies are required, then you can switch to the Local XACML Role-based PEP and reuse the roles you have already assigned in your repository.

Role/Permission Matrix