This API can be used to perform create, retrieval, update and delete operations on the MOLGENIS permission system. The MOLGENIS permission is based on Spring Security.
Parameters
These parameters are used by the endpoint in this API:
'typeId': This is the type of resource for which the permission is granted.
This maps to the 'type' in Spring security's ObjectIdentity.
In MOLGENIS examples of these types are 'entityType', 'package', 'plugin', and also row level secured entities, in which case the type is the entityType identifier prefixed with "entity-"
'identifier': This is the identifier of the actual resource within the resource type for which the permission is granted.
This maps to the 'identifier' in Spring security's ObjectIdentity.
'inheritance': a boolean indicating if inherited permissions should be returned or only the permission that are actually set for the roles and users requested. This parameter is only used in the GET permission requests. Setting this to true will return a tree with all inherited permissions for the requested users and roles. This field cannot be combined with paging.
'page': The pagenumber for the results, should only be provided combined with 'pageSize'. This field cannot be combined with 'inheritance=true'.
'pageSize': The number of results per result page, should only be provided combined with 'page'. This field cannot be combined with 'inheritance=true'.
'permission': A permission for a resource, the permissions that can be used differ per resource type, but are always a subset of READMETA,COUNT,READ,WRITE,WRITEMETA.
Query for user or role
user
The user for which to get/create/update the permission. This should be the username as stated in the 'sys_sec_User' table in the MOLGENIS database.
role
The role for which to get/create/update the permission. This should be the rolename as stated in the 'sys_sec_Role' table in the MOLGENIS database.
The user/role query for this API's GET operations should be provided in the RSQL syntax Examples:
Query for user 'Cardiologist' or users with role "CARDIOLOGY"
q=user==Cardiologist,role==CARDIOLOGY
Query for users 'Cardiologist' or 'Neurologist'
q=user=in=(Cardiologist,Neurologist)
Permission inheritance
There are two kinds of inheritance in the permission system:
Users inherit permissions from their roles, and roles from their parentroles.
The access control list (ACL) for a resource can have a parent, in that case permissions on the parent also grant permissions on the child ACL's. In the current MOLGENIS system this is the case for entity types and packages, both inherit permissions from the package in which they reside..
Managing row level security
Getting all resource types in the system
Endpoint
GET https://molgenis.mydomain.example/api/permissions/types
### Creating a new resource type in the system (Row level securing an entity type)
This will create a new type in the system and add access control lists for all existing rows.
This enables row level security and is only enabled for superusers.
Please keep in mind that all existing rows will get the current user as owner.
##### Endpoint
##### Parameters
URL: 'typeId' as described in the [parameters section](##Parameters)
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|201 Created | Type created |
|403 Forbidden | the user has no permissions to execute this action |
|409 Conflict | the type already exists |
##### Example
Enable row level security on entity type 'hospital_neurology_patients'.
Request:
```https://molgenis.mydomain.example/api/permissions/types/entity-hospital_neurology_patients
Deleting a resource type from the system (Removing row level security from an entity type)
This will delete a type, the access control lists for all rows will remain in the system. This disables row level security.
##### Parameters
URL:
- 'typeId' as described in the [parameters section](##Parameters)
- 'identifier' as described in the [parameters section](##Parameters)
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|201 Created | access control list created |
|400 Bad request| the permission request content is not valid |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role does not exist |
|409 Conflict | the a access control list already exists for this object |
##### Example
Add an ACL for 'Patient1' in _entity_ type 'hospital_neurology_patients'.
Request:
##### Parameters
URL:
- 'typeId' as described in the [parameters section](##Parameters)
Query:
- Optional: 'page' as described in the [parameters section](##Parameters)
- Optional: 'pageSize' as described in the [parameters section](##Parameters)
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|200 Ok | Success |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role or permission does not exist |
##### Response body
List of ACLs for a type in the system.
##### Example
Request:
##### Parameters
URL:
- 'typeId' as described in the [parameters section](##Parameters)
- 'identifier' as described in the [parameters section](##Parameters)
Query:
- Optional: [Query for user or role](##Query for user or role)
- Optional: 'inheritance' as described in the [parameters section](##Parameters)
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|200 Ok | Success |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role or permission does not exist |
##### Response body
A list of permissions objects containing the identifier and the label for the resource, the user or role that has this permission if any, and a list of [inherited permissions](###Permission inheritance).
The user and role of a permission can be absent if permission is only derived from inherited permissions.
##### Example
Request:
The neurologist and the nurse inherit their READ permissions from the their "NEUROLOGY" role, while the reception inherits the READ permission from the READ permission they have on the parent package "hospital" of the "hospital_neurology" package.
### Getting permissions for one or more users and/or roles for a resource type
##### Endpoint
##### Parameters
URL:
- 'typeId' as described in the [parameters section](##Parameters)
Query:
- Optional: [Query for user or role](##Query for user or role)
- Optional: 'inheritance' as described in the [parameters section](##Parameters)
- Optional: 'page' as described in the [parameters section](##Parameters)
- Optional: 'pageSize' as described in the [parameters section](##Parameters)
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|200 Ok | |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role or permission does not exist |
##### Response body
A list of permissions per resource is returned in the 'data' field.
These lists of permissions contain object containing the 'identifier' and the 'label' for the resource, the user or role that has this permission if any, and a list of [inherited permissions](###Permission inheritance) if any.
The 'user'/'role' and 'permission' of a permission can be absent if permission is only derived from inherited permissions.
A links object is returned with a URL for the current result page in the 'self' field. If available a 'previous' and 'next' page are returned with links to the previous and next page of results/
Optionally a 'page' object is returned containing the size and number of the current page and a 'totalElements' field containing the total number of results and 'totalPages' containing the total number of queries.
The page object is only returned if the request contained paging parameters
##### Example
Request:
##### Parameters
URL: none
Query:
[Query for user or role](##Query for user or role)
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|200 Ok | Success |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role or permission does not exist |
##### Response body
A list of permissions on resources per resource type.
For every resource type a object is returned containing the typeId, a label for the typeId, a label for the resource type and a list of permissions per resource.
These lists of permissions contain object containing the identifier and the label for the resource, the user or role that has this permission if any, and a list of [inherited permissions](###Permission inheritance).
The user and role of a permission can be absent if permission is only derived from inherited permissions.
##### Example
Request:
##### Request
The endpoint expects a list of permissions, each permission should contain a 'permission' and a 'user' or a 'role'.
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|201 No content | permissions created |
|400 Bad request| the permission request content is not valid |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role does not exist |
|409 Conflict | the a permission already exists for this combination of user/role and object |
##### Example request
URL:
https://molgenis.mydomain.example/api/permissions/entityType/hospital_cardiology_patients
Body:
##### Request
The endpoint expects a list of resources, each of which should contrain the identifier for the resource and a list of permissions, each of these permission should contain a 'permission' and a 'user' or a 'role'.
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|201 No content | permissions created |
|400 Bad request| the permission request content is not valid |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role does not exist |
|409 Conflict | the a permission already exists for this combination of user/role and object |
##### Example
URL: https://molgenis.mydomain.example/api/permissions/entity-hospital_neurology_patients
Body:
Request:
The endpoint expects a list of permissions, each permission should contain a 'permission' and a 'user' or a 'role'.
##### Response
| Status code | Description |
|---------------------|-----------------------------------------------------------------------------------|
|204 No content | permissions updated |
|400 Bad request| the permission request content is not valid |
|403 Forbidden | the user has no permissions to execute this action |
|404 Not found | the type, object, user, role or permission does not exist |
##### Example
Request:
URL: https://molgenis.mydomain.example/api/permissions/entityType/hospital_cardiology_patients
Body:
```{
permissions:[{
permission:WRITE,
role:CARDIOLOGY
},{
permission:WRITEMETA,
user:Cardiologist
}]
}
Update permissions for one or more users and/or roles for resources of a certain type
The endpoint expects a list of resources, each of which should contrain the identifier for the resource and a list of permissions, each of these permission should contain a 'permission' and a 'user' or a 'role'.
