New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BigQuery 3.0.0 - OAuth2 Authentication #418
Comments
@callmehiphop @rac0316 do we support receiving a |
In version 1.3 it was supported as an optional field. See: https://cloud.google.com/nodejs/docs/reference/bigquery/1.3.x/global#ClientConfig It seemed to have gotten lost somewhere in the latest releases. I did a little research and it looks like when the BigQuery 1.3 uses BigQuery 3.0 uses **I can verify if you downgrade the |
Good catch! I opened an issue over on the auth library: googleapis/google-auth-library-nodejs#677. |
This issue is preventing a sample from being created for this doc: |
Hello, I managed to get over this bug by doing this: #68 (comment) |
Tagging in @feywind as an FYI. |
Possibly fixed by #566 |
Blocked
token
argument google-auth-library-nodejs#677Environment details
@google-cloud/bigquery
version: 3.0.0Steps to reproduce
Attempting to use an OAuth2 token to authenticate to the BigQuery API version 3.0.0. Successfully can get a valid token using tutorial here: https://github.com/googleapis/google-auth-library-nodejs#oauth2
Instantiate BigQuery with token and project param
new BigQuery({ token: validAuthTokenFromAbove, projectId: validProjectId });
Attempt to run a query - this will return a "failed to fetch" error. After digging into the code, it's trying to fall back to Application Default Credentials. It seems the token property is being ignored.
*** If I downgrade BigQuery to v 1.3.0 everything works fine! I'll be using this for now until this gets resolved.
The text was updated successfully, but these errors were encountered: