Skip to content

test: run the M4.4 chain end to end with LS Login #44

Open

Description

@uniqueg

Why?

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?

  1. 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.
  2. 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.
  3. Workflows: as the member, run one example per language that WESkit supports on the BIH deployment. If WESkit validates tokens by then (WESkit: verify and enable LS Login bearer token validation on the BIH deployment #19, nice to have), also check that the non-member is refused there.
  4. 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.
  • The report is attached to this issue.

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 Nov 8, 2026
  2. removed
    type: authRelated to authorization or authentication
    on Nov 13, 2026
  3. added
    status: triageHas not been triaged by admin
    and removed on Nov 18, 2026
  4. added and removed
    status: triageHas not been triaged by admin
    on Nov 19, 2026
  5. uniqueg commented on Nov 21, 2026

    @uniqueg
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ecp-wp4: M4.4ELIXIR Compute Platform WP4 milestone/deliverable this issue contributes topriority: highHigh prioritystatus: blockedSomething prevents progresstype: testingRelated to code testingworkload: daysLikely takes days to resolve

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions