[Globus] Support custom username handling #357
Merged
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.
Move the code responsible for fetching the username to a separate get_username() method so it can be overridden.
An example is running a Globus Jupyterhub Server that can accept logins from one or more providers (Google, ORCID, Any university in CILogon, etc.), wants needs to ensure usernames are unique. That way, person@uchicago.edu and person@gmail.com are assigned different usernames. The jupyterhub config could look like this:
This is similar to the GenericOAuthenticator username picker, except the key in Globus will never change, so a callable is always preferred.