Separate OAuth2 grant validation - #3639
Merged
Merged
Conversation
adamtheturtle
had a problem deploying
to
vuforia
September 12, 2026 20:41 — with
GitHub Actions
Failure
adamtheturtle
had a problem deploying
to
vuforia
September 12, 2026 20:41 — with
GitHub Actions
Failure
Member
Author
|
The exact-head Test workflow is terminal. In addition to the two |
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.
The OAuth2 token handler combined request parsing, grant dispatch, two distinct authentication workflows, scope validation, and response construction. That required both Ruff and Pylint complexity suppressions.
This splits the client-credentials and password-grant validation into focused functions and shares only the access-token response construction. The public endpoint behavior and exact response payloads remain unchanged.
Validation: