-
Notifications
You must be signed in to change notification settings - Fork 591
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
Cannot authenticate using private_key
and client_email
#1173
Comments
I guess I found the error. Tomorrow I'll check at the office. |
Changed private_key : process.env.GCLOUD_PRIVATE_KEY by private_key : process.env.GCLOUD_PRIVATE_KEY.replace(/\\n/g, '\n') |
@eduardo-tenorio-guiabolso THANK YOU! |
@eduardo-tenorio-guiabolso I had the same challenge with hosting on Heroku, I needed to store the private key in environment variable, and your fix saved my day (doing the newline .replace on the key) Thank you so much :) |
@eduardo-tenorio-guiabolso I have been banging my head against a wall trying to figure out how to handle the newline characters, thank you so much for posting your solution, it worked perfectly! |
(╯°□°)╯︵ ┻━┻ ...but yeah, this definitely does the trick. thanks a million! |
SAVED MY LIFE! THANK YOU! |
I am trying to connect my NodeJS application to Pub/Sub. Since the production environment is in an AWS instance, I cannot use the default credentials approach. So, my approach is to pass a credentials object with the private key and the client email:
According to the docs. This variable is passed as an argument in a class constructor:
When I run locally, everything is OK. There is no
err
and I can publish tothis.topicName
. When I run on my staging environment, at AWS, I receive the error Error: Could not load the default credentials. Browse to https://developers.google.com/accounts/docs/application-default-credentials for more information.. I don't know what I am doing wrong. I tried several combinations of theGCLOUD_PRIVATE_KEY
. With and without the markers "-----BEGIN PRIVATE KEY-----\n" and "\n-----END PRIVATE KEY-----\n".Is this a bug or am I doing something wrong that I don't know?
The text was updated successfully, but these errors were encountered: