Skip to content

chore: configure proTES for ELIXIR On-Cloud #31

Closed
elixir-cloud-aai/docs
#179

Description

@uniqueg

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?

  1. (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.

  2. (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_CLN entitlement value(s) in eduperson_entitlement (do not hardcode a guessed string; expect something like urn:geant:lifescience-ri.eu:group:<vo>:ECP_CLN…#…), and the value for ECP_CLN:ADMIN;
    • whether members of subgroups (e.g. ELIXIR-DE, EOC-Compute) carry the parent ECP_CLN value; if not, map ECP_CLN and each subgroup value to user;
    • 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).
  3. Set the deployment configuration: issuer https://login.aai.lifescience-ri.eu/oidc/, userinfo_claims: [eduperson_entitlement], the frontends' client IDs as audience, i.e. Krini's (LS Login: register Krini's client #48; cf. feat(auth): send the user's token to services krini#44), and the ECP_CLN values from step 2 in group_mapping (user; ECP_CLN:ADMIN as admin).

  4. Configure every backend of the production deployment with its auth mode (client_credentials, or basic from 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).

Acceptance criteria

  • Task requests with tokens of ECP_CLN members (and subgroup members) are accepted; non-members get 403.
  • 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 🚀

Activity

  1. added
    type: authRelated to authorization or authentication
    workload: daysLikely takes days to resolve
    ecp-wp4: M4.4ELIXIR Compute Platform WP4 milestone/deliverable this issue contributes to
    on Oct 23, 2026
  2. moved this from Backlog to In progress in BioHackEU26: Miscellaneouson Nov 12, 2026
  3. 8 remaining items

  4. added
    status: triageHas not been triaged by admin
    and removed on Nov 17, 2026
  5. moved this from Backlog to Ready in ELIXIR On-Cloudon Nov 17, 2026
  6. added and removed
    status: triageHas not been triaged by admin
    on Nov 18, 2026
  7. self-assigned this
    on Nov 18, 2026
  8. moved this from Ready to In progress in ELIXIR On-Cloudon Nov 18, 2026
  9. moved this from In progress to Done in ELIXIR On-Cloudon Nov 18, 2026
  10. uniqueg commented on Nov 18, 2026

    @uniqueg
    MemberAuthor

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

    • Tokens: LS Login only (https://login.aai.lifescience-ri.eu/oidc/); accepted clients: Krini and the Cloud Registry UI; groups from userinfo (eduperson_entitlement).
    • Roles: 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 get 403.
    • Backends: one, the CSC test TESK (csc-tesk-noauth.rahtiapp.fi) with auth: none; no Node's TES service yet; Cloud Registry discovery off.
    • Plugins: none configured.
    • Checked: runbook block 2.3 passed on 2026-11-16 with a Krini token against the FI TESK.

    What remains moved to its own issues:

  11. moved this from In progress to Done in BioHackEU26: Miscellaneouson Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

ecp-wp4: M4.4ELIXIR Compute Platform WP4 milestone/deliverable this issue contributes topriority: highHigh prioritytype: authRelated to authorization or authenticationworkload: daysLikely takes days to resolve

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions