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

Define how the authorization in the web layer will work with other components #60

Closed
kinow opened this issue Mar 10, 2019 · 3 comments
Closed

Comments

@kinow
Copy link
Member

kinow commented Mar 10, 2019

JupyterHub has authentication, and also a thin layer of authorization in its reverse proxy. But the Cylc UI server will need to redefine parts of its authorization.

This issue is to record discussions on authorization for the web layer, which will interface with JupyterHub and with Cylc UI Server.

See related discussion in cylc/cylc: cylc/cylc-flow#1901

See related discussion in cylc/cylc-jupyterhub: cylc/cylc-uiserver#10

@kinow kinow changed the title Define how the authorization in the web layers plays with other components Define how the authorization in the web layer plays with other components Mar 10, 2019
@kinow kinow changed the title Define how the authorization in the web layer plays with other components Define how the authorization in the web layer will work with other components Mar 10, 2019
@hjoliver
Copy link
Member

But the Cylc UI server will need to redefine parts of its authentication.

Do you mean authorization there? (I'm slightly confused)

@kinow
Copy link
Member Author

kinow commented Mar 11, 2019

Oh! Good spot, sorry. Fixed the text.

@kinow kinow added this to the 1.0 milestone Sep 14, 2019
@kinow kinow modified the milestones: 1.0, 2.0 Sep 10, 2021
@oliver-sanders
Copy link
Member

Closed by cylc/cylc-uiserver#230

@oliver-sanders oliver-sanders removed this from the 2.0.0 milestone Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants