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.

Sign up for GitHub

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

Jump to bottom

ENH: provide config options for changing default client secrets (and scopes) #38

Open
tswast opened this issue Sep 24, 2020 · 1 comment
Open

ENH: provide config options for changing default client secrets (and scopes) #38

tswast opened this issue Sep 24, 2020 · 1 comment
Assignees
@RahulDubey391
Labels
type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.

Comments

@tswast
Copy link
Collaborator

tswast commented Sep 24, 2020

When pydata-google-auth is used in contexts where the API is not enabled on the default GCP project that owns the client secrets or the default scopes do not include the desired product / operation, authorization errors are encountered.

It would be difficult to get pydata-google-auth verified for every combination of scopes, so a better long-term solution would be to encourage people to provide their own client secrets files. Imagine use cases such as notebook hosting services or an enterprise fleet which wants data scientists to use its approved version of pandas.
@tswast tswast added the type: feature request 'Nice-to-have' improvement, new feature or different behavior or design. label Sep 24, 2020
@RahulDubey391
Copy link

Hi @tswast , I would like to work on this issue. Can you please assign it to me?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RahulDubey391 RahulDubey391

Labels
type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tswast @RahulDubey391