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

if on a remote server (e.g. using auth_local_webserver=False), then don't cache user credentials by default #605

Open
tswast opened this issue Jan 23, 2023 · 1 comment
Labels
api: bigquery Issues related to the googleapis/python-bigquery-pandas API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@tswast
Copy link
Collaborator

tswast commented Jan 23, 2023

If on a remote server (e.g. using auth_local_webserver=False), then there's a good chance the code is running on a shared machine (e.g. a VM or Colab notebook). In these cases, we should not cache credentials to a local filesystem, as there is a chance that other users have access to the same machine.

If I remember correctly, Colab already has patched this library to disable the caching when installed there, but it'd be great if we could do this by default in a way that works for all potentially-shared environments.

@tswast
Copy link
Collaborator Author

tswast commented Jan 23, 2023

Note: in addition to tackling this here for pandas-gbq, we should update the defaults in pydata-google-auth for folks using that library directly. pydata/pydata-google-auth#63

@meredithslota meredithslota added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Aug 23, 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-pandas API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

2 participants