You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move from oauth2client to google-auth / support ADC #6422
The above Pull Request supports Application Default Credentials (ADC), but when trying to access BigQuery using Workloads Identity, an incorrect message is displayed during the Test Connection.
Steps to Reproduce
To use ADC, set the environment variable GOOGLE_APPLICATION_CREDENTIALS.
Set the Name and Project ID.
Press the TEST Connection button.
Expected Behavior
Connection Test Success
Actual Behavior
Connection Test Failed:
Service account info was not in the expected format, missing fields token_uri, client_email.
It seems that the Test Connection checks the format of the service account JSON file and verifies the existence of token_uri and client_email. However, when using ADC, these keys do not exist, causing the test to fail even though the connection actually succeeds.
Technical details:
Redash Version: 25.1.0
Browser/OS: Any
How did you install Redash: Container on EKS
The text was updated successfully, but these errors were encountered:
Issue Summary
Move from oauth2client to google-auth / support ADC #6422
The above Pull Request supports Application Default Credentials (ADC), but when trying to access BigQuery using Workloads Identity, an incorrect message is displayed during the
Test Connection
.Steps to Reproduce
GOOGLE_APPLICATION_CREDENTIALS
.Expected Behavior
Connection Test Success
Actual Behavior
It seems that the Test Connection checks the format of the service account JSON file and verifies the existence of token_uri and client_email. However, when using ADC, these keys do not exist, causing the test to fail even though the connection actually succeeds.
Technical details:
The text was updated successfully, but these errors were encountered: