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.

Sign up for GitHub

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

Jump to bottom

Experience of not being allowed access too technical (403 error) #54

Open
consideRatio opened this issue Jul 23, 2020 · 0 comments
Open

Experience of not being allowed access too technical (403 error) #54

consideRatio opened this issue Jul 23, 2020 · 0 comments
Labels
post-mortem-followup Valuable to follow up for the open source ecosystem. wontfix This will not be worked on

Comments

@consideRatio
Copy link
Member

Currently users arriving to the JupyterHub without being part of the ACL according to JupyterHub (which due to #22 requires a manual restart atm), they just get a 403 error which is a bit too technical for them to realize what went wrong and if they could do something about it.

I wanted to document this as an issue to better resolve this long term even though I mark it as a wontfix for nh2020.
@consideRatio consideRatio added wontfix This will not be worked on post-mortem-followup Valuable to follow up for the open source ecosystem. labels Jul 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
post-mortem-followup Valuable to follow up for the open source ecosystem. wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@consideRatio