-
Notifications
You must be signed in to change notification settings - Fork 388
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
Error: The incoming JSON object does not contain a client_email field #137
Comments
I am pretty sure we require |
I'm having the same problem and I have a JSON file with the exact same format (no |
@daywaves You should use the service account JSON for OAuth2 authentication. Can you describe what you are trying to do, and where it is failing? |
You are mixing things up a bit :) You need to create a "Service account key" if you want to use this for service->service communication, where your account is used to perform actions. If you want to use the credentials of the user to perform actions on behalf of the user, you want to use OAuth2. In that case - you wouldn't use application default credentials, rather a standard OAuth2 workflow. We have some improved docs to cover this stuff sitting over in the next branch. I'm going to close this out for now - feel free to keep asking questions! |
This doesn't seem accurate. The Ruby gem for authenticating (particularly with Google Cloud Storage) does not require a client_email in order to operate. |
Interesting! Can you share a link? |
So, I haven't dug really deep into the Ruby library, but the functionality seems to be located here: https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-core/lib/google/cloud/credentials.rb#L49 I confirmed locally that loading a bucket and listing its files doesn't require a client_email, while the node client generates an error. It seems the Ruby client allows it to not be present, but also allows it to be passed in discretely. |
A similar problem arose. Thank you. |
Hello, I hate to message on old threads, but I just encountered this issue as well. Is there a solution somewhere I am not seeing? |
I'm followin the google calendar API docs in a NodeTS project and getting the same issue. This is my credentials.json. |
I am facing the same issue, do we have solution to this one ? |
Having the same issue when passing the result of |
Google = dogs*** |
I get this error when I'm using a OAuth client ID JSON file as GOOGLE_APPLICATION_CREDENTIALS.
Here's the content of this JSON file.
Here's the code where I get this error.
The text was updated successfully, but these errors were encountered: