Skip to content

Improve the user experience when Google credentials are expired or revoked #50

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

Closed
parthea opened this issue Jun 7, 2017 · 2 comments
Closed
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@parthea
Copy link
Contributor

parthea commented Jun 7, 2017

I think the user experience could be improved when Google credentials are expired or revoked. I see that we have a reauth parameter in read_gbq and to_gbq but this will cause the authentication to run each time even if the credentials are valid to cater for the environment where there are multiple users. It may be helpful to also have the ability to automatically trigger authentication flow when credentials are expired or revoked.

https://github.com/pydata/pandas-gbq/blob/master/pandas_gbq/gbq.py#L771

@jreback jreback added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Jun 9, 2017
@tswast
Copy link
Collaborator

tswast commented Sep 20, 2018

This is partially addressed by #212. It's now possible to refresh the credentials if the credentials are expired or revoked by manually setting reauth=True. Before that change, pandas-gbq would still try to load the expired credentials even when reauth=True and would fail with this error.

@parthea
Copy link
Contributor Author

parthea commented Apr 21, 2020

Closing as obsolete.

@parthea parthea closed this as completed Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

3 participants