fix(provider): add required OAuth scope for Google authentication#20214
fix(provider): add required OAuth scope for Google authentication#20214SOUMITRO-SAHA wants to merge 1 commit into
Conversation
Add missing Google Cloud Platform scope to GoogleAuth initialization to ensure proper authentication with Vertex AI services. Without this scope, the authentication flow would fail when accessing Google Cloud resources. This fixes potential authentication issues in the provider implementation.
|
The following comment was made by an LLM, it may be inaccurate: Found a potentially related PR: #19931 - feat(provider): support per-provider Google credentials for Vertex AI This PR may be related as it also deals with Google Vertex AI provider configuration. You should check if this PR already addresses the OAuth scope issue or if the two changes are complementary. |
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes #20202
Type of change
What does this PR do?
The Google Vertex provider was missing OAuth scopes when authenticating. This caused GLM models to fail with "invalid_scope" errors because Google didn't know what permissions were being requested.
Added the
https://www.googleapis.com/auth/cloud-platformscope to the GoogleAuth configuration so Google knows we need access to Vertex AI.How did you verify your code works?
Tested locally with GLM models through the Google Vertex provider. The authentication now succeeds and models respond correctly.
Screenshots / recordings
2026-03-31.12-34-53.mp4
Checklist