Skip to content
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

"https://www.googleapis.com/auth/bigquery" scope is unecessary #1444

Closed
tswast opened this issue Dec 14, 2022 · 0 comments · Fixed by #1503
Closed

"https://www.googleapis.com/auth/bigquery" scope is unecessary #1444

tswast opened this issue Dec 14, 2022 · 0 comments · Fixed by #1503
Labels
api: bigquery Issues related to the googleapis/python-bigquery API. type: process A process-related concern. May include testing, release, or the like.

Comments

@tswast
Copy link
Contributor

tswast commented Dec 14, 2022

"https://www.googleapis.com/auth/bigquery",

"https://www.googleapis.com/auth/cloud-platform" is a superset of "https://www.googleapis.com/auth/bigquery". We should only need 1, and per the rest of cloud we should use "https://www.googleapis.com/auth/cloud-platform"

Note: I'm filing this issue due to googleapis/google-auth-library-python#1204. I believe that even after the issue identified there is addressed (default scopes shouldn't cause user/impersonated credentials to downscope), google-auth might be downscoping credentials unnecessarily because it sees the "bigquery" scope and it's not present by default.

@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/python-bigquery API. label Dec 14, 2022
@tswast tswast added the type: process A process-related concern. May include testing, release, or the like. label Jan 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the googleapis/python-bigquery API. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant