...
<path to Container>/fcr:accessroles
REST methods:
| method | description |
|---|---|
| GET | Retrieves the roles assigned on a resource. |
| GET w/effective parameter | Retrieves the effective roles assigned on a resource, which may cascade from an ancestor role assignment. |
| POST | Sets all the roles assigned on a resource. |
| DELETE | Removes any roles assigned on a resource, such that effective roles are inherited again. |
The POST and GET methods currently support a JSON structure (as Content-type application/json) where principals are mapped to lists of roles:
...
By default, role names are not validated, since the module does not define the set of role names that may be assigned in Fedora. However, you may configure a set of specific roles and then the API will validate roles.
Example Data
| No Format |
|---|
root/ (default content roles, i.e. no roles for anyone)
├── Container A (EVERYONE => reader; johndoe => admin)
│ ├── Binary 1 (johndoe => admin)
│ └── Container Q (EVERYONE => reader; johndoe => admin)
│ └── Container R (janedee => admin)
├── Container B (EVERYONE => reader; johndoe => admin)
│ └── Container T
│ └── Container V
└── Container C |
Inheritance of Effective Roles
...