Repository navigation
Conversation
nauski
force-pushed
the
oauth2-allow-missing-username
branch
from
October 28, 2026 19:53
abfffb2 to
e2dae25
Compare
nauski
force-pushed
the
oauth2-allow-missing-username
branch
from
November 4, 2026 10:58
e2dae25 to
ba6b81a
Compare
nauski
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
DOV-9955
Documents the new
oauth2_username_from_tokensetting as a normal setting. When enabled, an OAUTHBEARER login without a username in its GS2 header is accepted, and the username is taken from the token. A username that the client does send must still match the token. The default isno.