-
Notifications
You must be signed in to change notification settings - Fork 92
support JupyterHub access scopes #863
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
702dc63
support using JupyterHub service access scopes in JupyterHubAuth
minrk eead588
document jupyterhub service auth
minrk 413c474
test jupyterhub service auth tokens
minrk 47efc80
expose jupyterhub_service_name in helm chart
minrk 9e5097f
need to set scopes to test them
minrk 9109d5b
simplify/clarify collision avoidance in jupyterhub auth
minrk 2d4a10c
Fix traitlets configuration detail
consideRatio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this code have
or notrather thanorin the if statement? I didn't understand this code block.The dask-gateway-server user's username will be changed if it starts with
user:orservice:, which perhaps may or may not ever be allowed though - I'm not sure. It contradicts the comment about not changing the username. Perhaps it should include "except in the edge case the name is starting with "user:" or "service:".There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the comment and simplified the condition to clarify.
This is to avoid collisions and also avoid changes for the ~99% of cases where it's just users accessing the service. JupyterHub doesn't put limits on usernames, so e.g. a user can technically have the name
service:name(unlikely because most identity providers don't allow this). This ensures that a user is never misrepresented asservice:namein this situation, they would beuser:service:name.gateway doesn't really use this for anything, so it's not that important. But this at least guarantees there is no collision. You can parse the result with:
and it will always be correct, even for names containing
:.