Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lifetime of auth tokens limiting workflow execution runtime #52

Open
uniqueg opened this issue Oct 9, 2018 · 1 comment
Open

Lifetime of auth tokens limiting workflow execution runtime #52

uniqueg opened this issue Oct 9, 2018 · 1 comment
Labels
priority: medium Medium priority status flag: help wanted Extra attention is needed type: auth Related to authorization or authentication workload: days Likely takes days to resolve

Comments

@uniqueg
Copy link
Member

uniqueg commented Oct 9, 2018

Is your feature request related to a problem? Please describe.
Current support for the OAuth2 implicit flow authorization scheme, handling authorization from WES-ELIXIR via cwl-tes to TESK is limited by the duration of validity of the issues tokens (e.g., 60 minutes for ELIXIR AAI). In other words: Workflows with runtimes exceeding one hour cannot currently be run in an AAI-secured setup.

Describe the solution you'd like
Support for refresh tokens should be added to WES-ELIXIR to allow negotation of new authorization tokens. For ELIXIR AAI, a refresh token can be obtained by requesting a token with an offline_token scope. In order to be able to do that, WES-ELIXIR first needs to be registered as a client with the identity provider/broker.

Describe alternatives you've considered
N/A at this time.

Additional context

  • While requesting tokens inside WES-ELIXIR should solve the problem in a test environment, it is likely not by itself a tenable solution in a real-world scenario where authentication would likely take place in a user-facing web service, not inside WES-ELIXIR. A way to "pass the refresh token" (or equivalent) would thus need to be found, possibly by using OpenID Connect hybrid flow.
  • Implementation of a refresh token policy would further increase security by restricting authorization tokens to single use.
@uniqueg uniqueg added this to the Release candidate v1.0.0-rc milestone Oct 9, 2018
@uniqueg uniqueg removed this from the Release candidate v1.0.0-rc milestone Sep 1, 2019
@uniqueg uniqueg removed the security label Feb 20, 2020
@uniqueg
Copy link
Member Author

uniqueg commented Apr 20, 2020

See AAI guidelines set up by ELIXIR Cloud & AAI. This needs to be set up together with a client that exposes a dedicated endpoint for refreshing the token.

@uniqueg uniqueg added priority: medium Medium priority type: auth Related to authorization or authentication workload: days Likely takes days to resolve status flag: help wanted Extra attention is needed labels Apr 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium Medium priority status flag: help wanted Extra attention is needed type: auth Related to authorization or authentication workload: days Likely takes days to resolve
Projects
None yet
Development

No branches or pull requests

1 participant