Skip to content

fix(bqjdbc): add default OAuth client id/secret#12946

Open
logachev wants to merge 4 commits intomainfrom
kirl/user_auth_default_client
Open

fix(bqjdbc): add default OAuth client id/secret#12946
logachev wants to merge 4 commits intomainfrom
kirl/user_auth_default_client

Conversation

@logachev
Copy link
Copy Markdown
Contributor

b/500714643

This OAuth ClientId/Secret is used also by BQ CLI and other drivers, so this is not a real "secret" (e.g. can be found in BQ CLI py files).

@logachev logachev requested review from a team as code owners April 28, 2026 22:43
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces default OAuth client credentials in BigQueryJdbcUrlUtility and updates the DataSource getters to return these defaults when values are missing. It also includes a new test case to verify the default behavior. Feedback highlights that applying these defaults unconditionally may conflict with other authentication types and recommends using trim().isEmpty() for more robust string validation. Additionally, hardcoding credentials in the source code was identified as a security risk.

logachev and others added 3 commits May 1, 2026 17:24
…gle/cloud/bigquery/jdbc/DataSource.java

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…gle/cloud/bigquery/jdbc/DataSource.java

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants