Error: Missing key, key or keyFile option must be provided!

While using gcloud on my own local server, I write:

var gcloud = require('gcloud');
var bucket;

bucket = gcloud.storage.bucket({
    projectId: 'myProjectName',
    keyFilename: 'resources/key.json',
    bucketName: 'testnameorwhatever'
});

bucket.write('demo.txt', 'Hello World', function(err) {
        var stuff = err || 'Created demo.txt'
        console.log(stuff);
});

if I do specify the right path to the key, it gives this output (not thrown error, just console log):
[Error: Missing key, key or keyFile option must be provided!]
I do not understand this message. There is a key specified, and the path to it is right. I know that, as if I write the wrong keyFilename path, it throws ENOENT error 34. So, is it about the key description or something?

Which version of gcloud-node are you using?

the latest one, I guess. 0.8.1

Can you verify that in yourproject/node_modules/gcloud-node/package.json? :)

Yeah, here is a fraction of it:

{
  "name": "gcloud",
  "version": "0.8.1",
  "author": {
    "name": "Google Inc."
  },
  "description": "Google Cloud APIs Client Library for Node.js",
...

Thanks, I'll play around and try to find the 🐛

Just in case I am dumb and use the wrong key, my key json has these fields in it:

{"web":{"auth_uri":"https://accounts.google.com/o/oauth2/auth", "client_secret": ..., "token_uri":...

and so on. Is that the right key? :)

Not dumb at all! There are a million things you can do in the Developers Console, it's very easy to get lost.

I believe you are using a client ID for a webapp, where what we want is a service account. https://github.com/GoogleCloudPlatform/gcloud-node/#elsewhere step 4 should show how to do that.

I'm going to close as I was able to reproduce the same error with a webapp key, and remedy it with a service key. If you run into anything else, ask away!

I'd say this issue comes down to a misunderstanding of the error message. The error itself is suggesting that a keyFile or key parameter should be specified, when really the error should suggest that they are likely using an invalid key file. Should we improve this err message?

Seems the error is created in gapitoken so we have no control over the error message, unless we do some of our own sanity checking when passing in the key / key file.

I'm try to use the same feature and I've the same error.

Have a fix to this problem?

@marcacohen

@marcacohen did you try #261 (comment)?

Nothing... I try to pass the client_email and the private_key manual, but I recive this error:

12176:error:0906D06C:PEM routines:PEM_read_bio:no start line:openssl\crypto\pem\pem_lib.c:703:Expecting: ANY PRIVATE KEY

You generated a service account JSON key from the developer's console, and it looked like:

{
  "private_key_id": "...",
  "private_key": "...",
  "client_email": "...@developer.gserviceaccount.com",
  "client_id": "....apps.googleusercontent.com",
  "type": "service_account"
}

You instantiated gcloud like:

require('gcloud')({
  credentials: {
    private_key: '...',
    client_email: '...@developer.gserviceaccount.com'
  }
});

and got that error?

More code that shows what you're doing and full stack traces would help me debug.

My JSON not is in this format.

The private_key have only ~16 chars. I'm almost on madness to solve this problem. :(

refactor(ts): merge initial TypeScript conversion (#334)

fix: drop support for node.js 4.x and 9.x (#261)

build: auto-approve renovate-bot PRs for minor updates (#1145) (#261)

build(tests): fix coveralls and enable build cop (#261)

build: add generated samples to .eslintignore (#261)

chore(deps): update dependency sinon to v10 (#261)

Fix the linter (#261)

chore(nodejs): remove api-extractor dependencies (#261)

refactor(ts): merge initial TypeScript conversion (googleapis#334)

chore(deps): lock file maintenance (#261)

chore(deps): lock file maintenance (googleapis#261)

Navigation Menu

Repository navigation

Error: Missing key, key or keyFile option must be provided! #261

57 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Error: Missing key, key or keyFile option must be provided! #261

Description

Activity

stephenplusplus commented on Oct 17, 2014

Lordink commented on Oct 17, 2014

stephenplusplus commented on Oct 17, 2014

Lordink commented on Oct 17, 2014

stephenplusplus commented on Oct 17, 2014

Lordink commented on Oct 17, 2014

stephenplusplus commented on Oct 17, 2014

ryanseys commented on Oct 17, 2014

ryanseys commented on Oct 17, 2014

thebergamo commented on Nov 5, 2014

stephenplusplus commented on Nov 5, 2014

thebergamo commented on Nov 5, 2014

stephenplusplus commented on Nov 5, 2014

thebergamo commented on Nov 5, 2014

57 remaining items

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions