Repository navigation
Description
Why?
M4.4 of the ELIXIR Compute Platform (WP4) needs the ELIXIR On-Cloud TESK deployments to accept LS Login tokens and to authorize users by the agreed group policy. The TESK chart and tesk-api already support this: group-based authorization (auth.mode, auth.env_basegroup, auth.env_subgroup) and, for identity providers whose groups don't fit TESK's group structure, authorization by a claim of the user info (elixir-cloud-aai/TESK#265, elixir-cloud-aai/tesk-api#78). What remains is the configuration at the ELIXIR On-Cloud deployments, tracked here so that the TESK repo stays generic.
Authorization policy (agreed). Users must be members of the LS Login (Perun) group ECP_CLN (organization ELIXIR, "ELIXIR Compute Platform group for cloud apps") or any of its subgroups, including EOC-Compute for approved compute users (elixir-cloud-aai/krini#45, #49). The exact entitlement values are recorded in #46; don't hardcode a guessed value.
How?
- On a test deployment, enable auth with LS Login and check token validation.
- Choose the authorization mode: the group model (settle
auth.env_subgroup, or the base group alone), or the claim-based option with theECP_CLNvalues from LS Login: record the ECP_CLN entitlement values #46. Use a TESK chart and tesk-api release that include the claim-based option. - Record the configuration here (no secrets), and roll it out on the FI TESK (
csc-tesk-noauth.rahtiapp.fi; the name may need to change once auth is on). - The GR and CZ deployments follow in Enable LS Login on the GR and CZ TESK deployments #50; NL only if TESK is chosen in Deploy a TES service at the NL Node (SURF) #22.
- If something doesn't work, open an issue in elixir-cloud-aai/TESK or elixir-cloud-aai/tesk-api for the generic gap.
Acceptance criteria
- The test deployment and the FI TESK accept LS Login tokens from
ECP_CLNmembers and reject others. - The configuration is recorded here for the other Nodes.
Dependencies: a TESK chart release that includes elixir-cloud-aai/TESK#265; #46.
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 fieldsBacklog
Activity
uniqueg commentedon Nov 8, 2026
Moved here from elixir-cloud-aai/TESK: the service repos stay generic and easy to deploy anywhere, so issues about specific deployments live in generic-issues.
[-]TESK: enable LS Login authentication with the ECP_CLN group model on all deployments[/-][+]Enable LS Login on the ELIXIR On-Cloud TESK deployments[/+]12 remaining items
uniqueg commentedon Nov 21, 2026
Done on 2026-11-21 (runbook blocks A-C, deployer-bot): the FI TESK runs chart 0.4.0 (tesk-api 2.0.0, TES 1.1.0) with LS Login tokens required. Only EOC-Compute and ADMIN may run tasks; no group model. New host
tesk.rahtiapp.fi,serviceInfo.idfi.rahtiapp.tesk; the old hostcsc-tesk-noauth.rahtiapp.fipoints to the same instance and also answers401without a token, until it's switched off.Next: the token test by a member (V), then #111 (proTES with its own client; until then proTES has no working backend), #110 pass 2 (NVFlare hub), the docs update, and finally the old host off.
uniqueg commentedon Nov 21, 2026
Token check (V) passed on 2026-11-21 with a member token from the portal: both claim values (EOC-Compute, ADMIN) recognized, no super-admin match, 200 with the token, a task with an input ran to COMPLETE and printed
hello, the task is owned by the caller (not anonymous), and 401 without a token for it. The FI TESK attesk.rahtiapp.fiis done. Next: #111 (proTES with its own client).