From 424138a465b8a0a23fbe8831047fe24a9cc715d9 Mon Sep 17 00:00:00 2001 From: Alex Kanitz Date: Wed, 18 Nov 2026 02:42:54 +0100 Subject: [PATCH 1/2] docs: record proTES configuration Record the effective configuration of the ELIXIR On-Cloud's proTES on its operator page: deployment, token issuer and audience, group mapping and the added admin rules, TES services and plugins. Mark the page verified against the live service info and configuration, and name ECP_CLN:ADMIN next to EOC-Compute in the access row. Refs elixir-cloud-aai/generic-issues#31 Co-Authored-By: Claude Opus 5.5 --- docs/operators/services/protes.md | 40 ++++++++++++++++++++++++++----- 1 file changed, 34 insertions(+), 6 deletions(-) diff --git a/docs/operators/services/protes.md b/docs/operators/services/protes.md index 27fae02..7c38d6c 100644 --- a/docs/operators/services/protes.md +++ b/docs/operators/services/protes.md @@ -1,5 +1,5 @@ --- -last_verified: null +last_verified: 2026-11-18 --- # proTES @@ -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)) | | 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 | @@ -47,8 +47,36 @@ 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. -[gi-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` | +| 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](../ls-login.md)). + +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]). + +[gi-111]: From 1882e739f50b9e28f3d015df6fd7fcd5e09d639c Mon Sep 17 00:00:00 2001 From: Alex Kanitz Date: Wed, 18 Nov 2026 08:20:59 +0100 Subject: [PATCH 2/2] docs: explain proTES subgroup matching The group mapping matches the EOC-Compute and ADMIN subgroup values, not the parent ECP_CLN value, which LS Login releases only if the parent group is assigned to the client's facility (generic-issues#46). Addresses a Sourcery review thread. Co-Authored-By: Claude Opus 5.5 --- docs/operators/services/protes.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/operators/services/protes.md b/docs/operators/services/protes.md index 7c38d6c..45668e2 100644 --- a/docs/operators/services/protes.md +++ b/docs/operators/services/protes.md @@ -74,9 +74,16 @@ 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]). +[gi-46]: [gi-111]: