Skip to content

proTES

proTES is a gateway for GA4GH TES services. It receives task requests, applies middleware (plugins) and forwards each task to one of the TES services that it knows.

Role in the deployment

proTES sits in front of the Nodes' TES services: clients send their tasks to proTES, and proTES distributes them to the Nodes. It can read the verified TES services of a Cloud Registry, so that a new Node is used once it is registered and verified; the ELIXIR On-Cloud's proTES lists its TES services in its configuration instead (see below). Register a proTES that you deploy in the Cloud Registry like any other TES service, and end every upgrade or change of it by updating its entry, or checking that sync did (see After a deployment or an upgrade).

Docs

In the ELIXIR On-Cloud

As of November 2026:

What Value
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 or ECP_CLN:ADMIN, issued to a client that it accepts, such as Krini's (see Researchers)
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

A Node's TES service is added to the configuration when its admins ask for it and the service requires LS Login tokens (see 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.

Configuration

The effective configuration of the ELIXIR On-Cloud's proTES, as of 18 November 2026 (see Access control in the proTES docs for what the roles may do):

Setting Value
Deployment Helm chart protes-0.6.0.tgz of the v0.6.0 release 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
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
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
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)
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).

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). 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).