You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test: run the M4.4 chain end to end with LS Login #44
Each part of the M4.4 chain has its own issue, but nothing checks the whole chain with real LS Login users: client, proTES gateway, TES backends at the Nodes, and WESkit. The M4.4 report needs this as evidence. This issue covers what can be checked without the Krini rewrite; the run from Krini follows with #37.
How?
Use two LS Login test accounts: one member of ECP_CLN (or of a subgroup, e.g. EOC-Compute), one non-member. The evidence contains no tokens and no personal identifiers.
Tasks: as the member, submit a TES task through the proTES gateway with the GA4GH SDK CLI or curl, and check that it runs on the backends of at least two Nodes. Check that the non-member gets 403 and a request without a token gets 401.
Write a short report: what ran where, timings, failures and gaps. File bugs in the owning repos and link them here. Move checks that can be automated into the service repos' test suites (e.g. test: save the Rahti checks in the test suites protes#424).
Acceptance criteria
The member's tasks and workflows succeed; the non-member and requests without a token are refused at the gateway.
At least one task ran on each Node whose backend accepts tokens.
From #55, which closed today: also check here, in the end-to-end run, that (1) a workflow runs from Krini through a WES backend, and (2) a user who is not in EOC-Compute or ADMIN is refused, with an account that is in neither group.
Activity
uniqueg commentedon Nov 21, 2026
From #55, which closed today: also check here, in the end-to-end run, that (1) a workflow runs from Krini through a WES backend, and (2) a user who is not in EOC-Compute or ADMIN is refused, with an account that is in neither group.