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
Connect proTES to the FI TESK with its service token #111
Once the FI TESK requires tokens (#35), proTES can't use it: proTES calls its backends with its own client credentials token (#31), which tesk-api can only accept with the allow-list of clients (elixir-cloud-aai/tesk-api and elixir-cloud-aai/TESK, linked). Until then the FI TESK is out of proTES' backends. Part of the parent issue.
How?
With proTES' client (LS Login: register the proTES client #47), get one token and record here its claims that matter, without the token: iss, client_id, azp, aud, sub, typ header, lifetime. Choose the client claim for TESK accordingly.
Upgrade the FI TESK to the tesk-api and chart releases with the allow-list; set the issuer (https://login.aai.lifescience-ri.eu/oidc/), the claim, and proTES' client ID. Keep the user-token settings of Enable LS Login on the ELIXIR On-Cloud TESK deployments #35.
Set the FI TESK in proTES' backends with auth: client_credentials and proTES' issuer for client credentials (chore: configure proTES for ELIXIR On-Cloud #31 step 4), and run proTES' integration check against it (a task that completes, one that fails, one cancelled).
Check that a direct request with proTES' token is accepted, and that a user token still is too.
Activity