authorization.md

Controlling authorization

Requestor's endpoints are protected by Arborist policies:

• To create an access request, users must have create access on service requestor for the relevant resource paths (either the resource paths provided in the request, or the resource paths for the policy provided in the request).
• To update an access request, users must have update access on service requestor for the relevant resource paths.
• To delete an access request, users must have delete access on service requestor for the relevant resource paths.
• Users can see their own access requests regardless of their access in Arborist by hitting the GET /request/user endpoint.
• To see other access requests (when GETting a specific access request or when querying existing access requests), users must have read access on service requestor for the relevant resource paths.

Authorization configuration example

User [email protected] wants to request access to dataset D. The resource path for dataset D in the user.yaml file is /programs/P/projects/D.

The authorization is flexible: we can allow specific users to request access to specific datasets, or allow all users to request access to all datasets (see the example configuration below), or something in-between.

authz:
  # policies automatically given to authenticated users
  all_users_policies:
    - requestor_creator

  resources:
    - name: programs
      subresources:
        - name: P
          subresources:
            - name: projects
              subresources:
                - name: D

  policies:
    - id: requestor_creator
      description: Allows requesting access to any resource under "/programs"
      role_ids:
        - requestor_creator_role
      resource_paths:
        - /programs
    - id: dataset_D_reader
      description: Allows access to dataset D
      role_ids:
        - reader
      resource_paths:
        - /programs/P/projects/D

  roles:
    - id: requestor_creator_role
      permissions:
        - id: requestor_creator_action
          action:
            service: requestor
            method: create
    - id: reader
      permissions:
        - id: reader_action
          action:
            service: '*'
            method: read

The user can request access to dataset D by requesting access to the dataset_D_reader policy. The resource path for this policy is /programs/P/projects/D, and since the user has access to create in service requestor for all resource paths under /programs, the user is allowed to request access to this policy. The resulting entry in the Requestor database looks something like this:

{
    "request_id": "<unique ID>",
    "username": "[email protected]",
    "policy_id": "dataset_D_reader",
    "status": "DRAFT"
}

An administrator now needs to review this access request and approve or reject it. We can add a policy to the user.yaml to grant [email protected] access to manage access requests for dataset D:

authz:
  policies:
    - id: requestor_dataset_D_updater
      role_ids:
        - requestor_updater
      resource_paths:
        - /programs/P/projects/D

  roles:
    - id: requestor_updater
      permissions:
        - id: requestor_updater_action
          action:
            service: requestor
            method: update

  users:
    [email protected]:
      policies:
        - requestor_dataset_D_updater

The administrator now has access to update the status of the access request. If they approve the request, [email protected] is granted access to the dataset_D_reader policy.

Removing access

A user's access to a policy can be removed by creating a new request that includes the revoke query parameter. Submit a POST request to the request endpoint, for example:

POST https://mycommons.org/requestor/request?revoke

The body of the request should have the username and policy_id, for example

{
    "username": "[email protected]",
    "policy_id": "dataset_D_reader",
}

Just like access requests, revocation requests must be approved before they take effect. The user's access will be revoked when the new request has been approved by an administrator.

IMPORTANT NOTE: Requestor can only revoke access that has been granted through Requestor.

What does this mean? Access granted through the user.yaml file cannot be revoked by Requestor. Similarly, removing access through the user.yaml file will not revoke access granted by Requestor.