fix edge case where auth state is left behind in an updated instance #30
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.
If the
authorization_url
andenable_auth_state
values were previously set, then later one or both are unset, jupyterhub is restarted, and the database is not cleared, there will be anauth_state
present for users who previously logged in stored in the database.In this case, jupyterhub will still attempt to update the
auth_state
with a now invalidauthorization_url
. This adds additional checks to ensure that this will not attempt to update theauth_state
with invalid settings.