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

google impersonated service account: fail when scope not provided #537

Open
guillaumeblaquiere opened this issue Jan 21, 2022 · 1 comment · May be fixed by #762
Open

google impersonated service account: fail when scope not provided #537

guillaumeblaquiere opened this issue Jan 21, 2022 · 1 comment · May be fixed by #762

Comments

@guillaumeblaquiere
Copy link
Contributor

The scope is a requirement of the Service Account Credential generateAccessToken API

WIth "impersonated_service_account" credential type, if the scope is not set, the token request fail.

The idea is to add a scope by default (i.e. the Cloud Platform scope) if no scope is provided.

@liufuyang
Copy link

Took me a long time to figure out it is this issue by just looking at errors like this:

oauth2/google: status code 400: {
  "error": {
    "code": 400,
    "message": "Request contains an invalid argument.",
    "status": "INVALID_ARGUMENT"
  }
}

Will this be solved soon? Thanks @guillaumeblaquiere

kevin-dimichel added a commit to voxel51/fiftyone-teams-app-deploy that referenced this issue May 31, 2024
…uth action to set default scope to overcome error like in golang/oauth2#537
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 a pull request may close this issue.

2 participants