-
Notifications
You must be signed in to change notification settings - Fork 27
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
Comments
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
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
Do you mean authorization there? (I'm slightly confused) |
Oh! Good spot, sorry. Fixed the text. |
Closed by cylc/cylc-uiserver#230 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: