fix(google-workspace): normalize authorized user token writes#10986
Merged
Conversation
Contributor
|
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
2 participants
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.
Summary
Normalizes freshly written Google Workspace tokens to include
"type": "authorized_user"so thegwsCLI backend accepts them immediately after OAuth setup.Fixes #10913. Cherry-picked from #10919 (credit: @LeonSGP43).
What changed
_normalize_authorized_user_payload()helper tosetup.py,google_api.py, andgws_bridge.pyexchange_auth_code()— initial token write after OAuthcheck_auth()— token refresh in setup scriptget_credentials()— token refresh in API scriptrefresh_token()— gws bridge refresh"type"field is persistedTest plan
pytest -o addopts= tests/skills/test_google_oauth_setup.py tests/skills/test_google_workspace_api.py # 14 passed