Authenticate bigquery client behind a proxy connection.

[tangtai]

I am currently building a Next.js app that utilizes API routes to fetch data from BigQuery. Initially, I was able to successfully run it locally using a service account. However, the app recently stopped working, and I suspect that it may be due to my network being behind a proxy server instead of being directly connected

FetchError: request to https://www.googleapis.com/oauth2/v4/token failed, reason: connect ETIMEDOUT 172.217.160.74:443 at ClientRequest.<anonymous> (/Users/---/node_modules/next/dist/compiled/node-fetch/index.js:1:65756) at ClientRequest.emit (node:events:513:28) at TLSSocket.socketErrorListener (node:_http_client:494:9) at TLSSocket.emit (node:events:513:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21)

If anyone have experience or fixes for client connection behind a proxy?

[loferris]

In order to more properly assess this issue, I think it'd be helpful to know how your current approach to auth lines up with how the auth library deals with OAuth2. Otherwise, this doesn't necessarily look like a client library issue so much as managing retries with timeouts. Please feel free to re-open!