Repository navigation
Expand file tree
/
Copy pathconfig.dev.yaml
More file actions
43 lines (43 loc) · 1.66 KB
/
Copy pathconfig.dev.yaml
File metadata and controls
43 lines (43 loc) · 1.66 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
# Config overlay for local development with Docker Compose
# (`docker-compose.yaml`); NOT for deployments, which must set the issuers,
# the audience and the groups of the roles (see `docs/access-control.md`).
# For local tests with access tokens without an identity provider of your
# own, use the Compose override of the smoke test instead, with its fake
# identity provider (see `docs/development.md`)
security:
auth:
# Replace with the issuer of your identity provider, whose tokens you use
issuers:
- https://login.example.org/oidc/
# Accept tokens for any audience (i.e., of any app)
verify_audience: False
# Claims with the groups of users, if not in access tokens
userinfo_claims:
- groups
access_control:
# Map your groups to the roles `user` and `admin`, e.g.:
# group_mapping:
# compute-users: user
# compute-admins: admin
claim_groups: groups
group_mapping: {}
# Start without admin groups
require_admin: False
# List the TES instances to forward tasks to, and how proTES authenticates at
# them (see `docs/access-control.md`), e.g.:
# custom:
# tes:
# backends:
# - type: ga4gh-tes
# url: https://tes.example.org
# auth: none
# Plugins that process new tasks (see `docs/plugins.md`). The default
# pipeline routes in random order; this overlay uses FOCA's ordered failover
# instead (the TES instances in the order listed above). Routing by the
# distance to the input data (`tes.routing.distance`) is an opt-in, as it
# sends the addresses of the hosts of task inputs to third parties
plugins:
pipeline:
- id: route
alternatives:
- plugin: foca.routing.ordered