Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
47 changes: 41 additions & 6 deletions docs/operators/services/protes.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
last_verified: null
last_verified: 2026-11-18
---

# proTES
Expand Down Expand Up @@ -37,7 +37,7 @@ As of November 2026:
|---|---|
| Address | TES API at `https://protes.rahtiapp.fi/ga4gh/tes/v1` (the host itself has no page) |
| Version | proTES 0.6.0 |
| Access | LS Login access tokens of members of the group `ECP_CLN:EOC-Compute`, issued to a client that it accepts, such as Krini's (see [Researchers](../../researchers/index.md#before-you-start)) |
| Access | LS Login access tokens of members of the group `ECP_CLN:EOC-Compute` or `ECP_CLN:ADMIN`, issued to a client that it accepts, such as Krini's (see [Researchers](../../researchers/index.md#before-you-start)) |
Comment thread
uniqueg marked this conversation as resolved.
Resolved
| Environment | `test`: its service info calls it "proTES sandbox (BioHackathon 2026)" |
| TES services | one, listed in its configuration: the TESK for tests at CSC (`csc-tesk-noauth.rahtiapp.fi`), which accepts tasks without a token |
| Discovery in the Cloud Registry | off |
Expand All @@ -47,8 +47,43 @@ it and the service requires LS Login tokens (see [Get added behind the
gateway](../node-onboarding-tutorial.md#7-get-added-behind-the-gateway)).
No Node's TES service has been added yet.
The service info of proTES (`GET /ga4gh/tes/v1/service-info`) lists the TES
services that it uses. The rest of its configuration, such as its plugins
and how it authenticates at its TES services, is tracked in
[generic-issues#31][gi-31].
services that it uses.
Comment thread
sourcery-ai[bot] marked this conversation as resolved.
Resolved

[gi-31]: <https://github.com/elixir-cloud-aai/generic-issues/issues/31>
### Configuration

The effective configuration of the ELIXIR On-Cloud's proTES, as of
18 November 2026 (see [Access control in the proTES
docs](https://protes.readthedocs.io/en/v0.6.0/access-control/) for what the
roles may do):

| Setting | Value |
|---|---|
| Deployment | Helm chart `protes-0.6.0.tgz` of the [v0.6.0 release](https://github.com/elixir-cloud-aai/proTES/releases/tag/v0.6.0) on CSC's Rahti, image `elixircloud/protes:0.6.0` pinned by digest, with MongoDB 7.0 and RabbitMQ 4.3 from the chart |
| Token issuer | LS Login only: `https://login.aai.lifescience-ri.eu/oidc/` |
| Audience | the LS Login clients of Krini and of the Cloud Registry UI |
| Groups | read from LS Login's userinfo endpoint, claim `eduperson_entitlement` |
Comment thread
sourcery-ai[bot] marked this conversation as resolved.
Resolved
| Role `user` | `urn:geant:lifescience-ri.eu:group:elixir:ECP_CLN:EOC-Compute#aai.lifescience-ri.eu`: create tasks, list their own, list and read the plugins |
Comment thread
sourcery-ai[bot] marked this conversation as resolved.
Resolved
| Role `admin` | `urn:geant:lifescience-ri.eu:group:elixir:ECP_CLN:ADMIN#aai.lifescience-ri.eu`: the permissions API (`/admin/access-control/permissions`, on the public address) and the provenance of all tasks; three added rules (`admins-create-list-tasks`, `admins-list-plugins`, `admins-get-plugins`) give it the rights of `user` too |
Comment thread
uniqueg marked this conversation as resolved.
Resolved
| Other tokens | valid tokens without either group get `403 Forbidden` on tasks and plugins; the service info is public |
| Own tasks | only the user who created a task can read and cancel it; admins can read the provenance of any task, not the task |
| TES services | the TESK for tests at CSC, without authentication (`auth: none`) |
Comment thread
uniqueg marked this conversation as resolved.
Resolved
| Plugins | none configured (the service info lists no capabilities) |

LS Login releases only the groups assigned to the client's facility, so a
new client that should reach proTES needs `ECP_CLN:EOC-Compute` and
`ECP_CLN:ADMIN` assigned to its facility and its client ID added to the
audience (see [LS Login](../ls-login.md)).

The mapping matches the subgroup values, not the parent group `ECP_CLN`:
members of a subgroup carry the parent value only if the parent group is
assigned to the facility of the token's client, too
([generic-issues#46][gi-46]). Members of other `ECP_CLN` subgroups get no
role.

proTES doesn't use a client of its own yet. Once it calls the TES services
with its own LS Login token, the TESK at CSC moves to an address that
requires tokens and its entry here changes from `auth: none` to
`client_credentials` ([generic-issues#111][gi-111]).
Comment thread
uniqueg marked this conversation as resolved.
Resolved

[gi-46]: <https://github.com/elixir-cloud-aai/generic-issues/issues/46>
[gi-111]: <https://github.com/elixir-cloud-aai/generic-issues/issues/111>
Loading