Repository navigation
Description
Why?
proTES is the gateway in the M4.4 chain. Its code now validates bearer tokens, maps groups to the roles user and admin, and calls the TES backends with its own client-credentials token (or a transitional per-backend basic mode), with nothing stored per task (elixir-cloud-aai/protes#201, done for proTES). proTES itself stays generic: issuers, audiences, group mappings, its own client and the backends are deployment configuration. This issue holds the ELIXIR On-Cloud part of that configuration, which moved here from elixir-cloud-aai/protes#201.
How?
-
(LS Login: register the proTES client #47) Register a client-credentials client for proTES at LS Login (
PROTES_CLIENT_ID,PROTES_CLIENT_SECRET), and store its credentials as a Secret for the deployment. -
(LS Login: record the ECP_CLN entitlement values #46) Check with real LS Login tokens of a test member of
ECP_CLN:- the exact
ECP_CLNentitlement value(s) ineduperson_entitlement(do not hardcode a guessed string; expect something likeurn:geant:lifescience-ri.eu:group:<vo>:ECP_CLN…#…), and the value forECP_CLN:ADMIN; - whether members of subgroups (e.g.
ELIXIR-DE,EOC-Compute) carry the parentECP_CLNvalue; if not, mapECP_CLNand each subgroup value touser; - whether the claim appears in the access token or only via userinfo (the sample token of 2026-10-20 carries no group claims, so groups come from userinfo);
- that FOCA's JWKS and userinfo validation accept the tokens (so far only tested with a fake identity provider in proTES's smoke test).
- the exact
-
Set the deployment configuration: issuer
https://login.aai.lifescience-ri.eu/oidc/,userinfo_claims: [eduperson_entitlement], the frontends' client IDs asaudience, i.e. Krini's (LS Login: register Krini's client #48; cf. feat(auth): send the user's token to services krini#44), and theECP_CLNvalues from step 2 ingroup_mapping(user;ECP_CLN:ADMINasadmin). -
Configure every backend of the production deployment with its auth mode (
client_credentials, orbasicfrom Secrets until the node accepts tokens). Coordinate with each Node; the Node admins also confirm which of the listed instances are still live:- CZ: Funnel/OpenPBS (
funnel.cloud.e-infra.cz), Poiesis (poiesis.dyn.cloud.e-infra.cz), TESK (tesk-na.cloud.e-infra.cz, still live?) - DE: Funnel/Slurm @ BIH (
spe4hd.tes.bihealth.org) - FI: TESK (
csc-tesk-noauth.rahtiapp.fi), Funnel/Slurm (fip-86-50-228-254.kaj.poutavm.fi), Poiesis (poiesis.rahtiapp.fi), plus the test Poiesis and CSC VM instance (vm4816.kaj.pouta.csc.fi) if still live - GR: TESK (
tesk-eu.hypatia-comp.athenarc.gr) - NL: planned (Deploy a TES service at the NL Node (SURF) #22)
Alternatively, the backends come from the Cloud Registry (feat: discover TES backends from the registry protes#260) once they are registered and verified there (Populate the Cloud Registry: owners register their own deployments, admins remove placeholder entries #29).
- CZ: Funnel/OpenPBS (
Acceptance criteria
- Task requests with tokens of
ECP_CLNmembers (and subgroup members) are accepted; non-members get403. - Tasks reach every live Node's backends via the configured mode.
Dependencies: a proTES release with the auth changes (elixir-cloud-aai/protes#246). Token support at the nodes: #35, elixir-cloud-aai/TESK#20 (Funnel), elixir-cloud-aai/TESK#21 (Poiesis); until then, those backends use basic.
Part of the ELIXIR Compute Platform WP4 sprint (M&Ds due end of December 2026).
If you want to work on this issue:
- Assign yourself (if someone is already assigned, ask them first or pick another one)
- Move the issue to "In progress" on the project board
- Start working 🚀
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsDone
Activity
8 remaining items
uniqueg commentedon Nov 18, 2026
Closing as decided: the gateway part of M4.4 works, and the configuration is recorded on the operator page: https://docs.elixir-on.cloud/en/latest/operators/services/protes/#configuration (elixir-cloud-aai/docs#179).
In short (proTES 0.6.0 on Rahti,
https://protes.rahtiapp.fi/ga4gh/tes/v1):https://login.aai.lifescience-ri.eu/oidc/); accepted clients: Krini and the Cloud Registry UI; groups from userinfo (eduperson_entitlement).ECP_CLN:EOC-Compute->user;ECP_CLN:ADMIN->admin, with three added rules so admins can run tasks too (decided 2026-11-12). Non-members get403.csc-tesk-noauth.rahtiapp.fi) withauth: none; no Node's TES service yet; Cloud Registry discovery off.What remains moved to its own issues:
client_credentials): Connect proTES to the FI TESK with its service token #111 (the LS Login client of LS Login: register the proTES client #47 is approved).