Fixing Google BigQuery Auth Proxying
The article discusses a solution for routing authentication traffic through a proxy when using Google BigQuery client libraries in C#. It highlights the issue where authentication and token refresh requests bypass the proxy, leading to timeouts. The recommended fix involves using a proxied GoogleCredential in the client builder configuration.
- ▪C# applications behind a proxy may face issues with Google BigQuery client libraries.
- ▪Authentication requests often ignore the proxy, causing timeouts.
- ▪Setting a proxied GoogleCredential in the client builder resolves the issue.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3946739) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Ryan Esteves Posted on May 22 Fixing Google BigQuery Auth Proxying #dotnet #googlecloud #aspdotnet #bigquery TL;DR builder.Credential = credential; - Fails to route authentication traffic through the proxy. builder.GoogleCredential = credential; - Successfully routes OAuth token requests through the proxy.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
