Closed gadgrandez closed 1 month ago
Hey @gadgrandez
That looks like it can't decode the private key which normally means you may not have pasted in the private key value correctly.
From the json file you get from Google can you make sure you copy everything between the "
for the private_key
value.
Hello @Joffcom. I have found the same instructions in various forums, however I have checked twice and copied it as is. Even when configuring the credential I receive the message "Connection tested successfully"
The same error occurs on various nodes that use service accounts. I don't know since when it happens, but I haven't had any problems for a few months.
Hey @gadgrandez
That is interesting is it just those 2 nodes? I wonder if we don't fully support service accounts with them yet.
I will check on Monday morning.
Ok, I've checked again. The error occurs on AI nodes using the "Google Vertex Chat Model".
Error: error:1E08010C:DECODER routines::unsupported at Sign.sign (node:internal/crypto/sig:128:29) at Object.sign (/usr/local/lib/node_modules/n8n/node_modules/jwa/index.js:152:45) at Object.jwsSign [as sign] (/usr/local/lib/node_modules/n8n/node_modules/jws/lib/sign-stream.js:32:24) at GoogleToken.requestToken (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:232:31) at GoogleToken.getTokenAsyncInner (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:166:21) at GoogleToken.getTokenAsync (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:145:55) at GoogleToken.getToken (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:97:21) at JWT.refreshTokenNoCache (/usr/local/lib/node_modules/n8n/node_modules/google-auth-library/build/src/auth/jwtclient.js:172:36) at JWT.refreshToken (/usr/local/lib/node_modules/n8n/node_modules/google-auth-library/build/src/auth/oauth2client.js:153:24) at JWT.getRequestMetadataAsync (/usr/local/lib/node_modules/n8n/node_modules/google-auth-library/build/src/auth/oauth2client.js:298:28)
Hey @gadgrandez,
Perfect so just to confirm this is not related to BigQuery and it is more of an issue with the Vertex AI node?
Internal reference for this one is AI-276
Hi @Joffcom. Yes, the issue is with Vertex AI Node.
I'm facing same problem here on version 1.53.2
Up, I also had the same problem on Vertex AI Node.
We have this error too!
same here.
This is a problem related to new lines inside the key. I managed to fix the error by switching the key format input type to "expression"
This is a problem related to new lines inside the key. I managed to fix the error by switching the key format input type to "expression"
Dear @restyler,
Thank you for your suggestion. Unfortunately, it's not working on my side. Could you please share the ending of the key where you put "}}"? In my case, I have it at the end as: -----END PRIVATE KEY-----\n" }}.
This is a problem related to new lines inside the key. I managed to fix the error by switching the key format input type to "expression"
Dear @restyler,
Thank you for your suggestion. Unfortunately, it's not working on my side. Could you please share the ending of the key where you put "}}"? In my case, I have it at the end as: -----END PRIVATE KEY-----\n" }}.
Same here
Had the same problem here using the Vertex node and the solution proposed by @restyler worked for me. It isn't the ideal because the key remains exposed.
@davivc Thanks for your comment. I have a question. I managed to connect successfully. But I can not load any project. Did you have the same issue? Thanks a lot.
@surenka11 Yes, it didn't load the projects for me as well. I used the option By ID and wrote manually then it worked. It's painful to do this that way, the credential is not secure but for prototyping now it's fine.
I'm having the same issue and @restyler's solution (using expression on private key) doesn't work for me. Do you have other ideas?
Error message
Error: error:1E08010C:DECODER routines::unsupported at Sign.sign (node:internal/crypto/sig:128:29) at Object.sign (/usr/local/lib/node_modules/n8n/node_modules/jwa/index.js:152:45) at Object.jwsSign [as sign] (/usr/local/lib/node_modules/n8n/node_modules/jws/lib/sign-stream.js:32:24) at GoogleToken.requestToken (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:232:31) at GoogleToken.getTokenAsyncInner (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:166:21) at GoogleToken.getTokenAsync (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:145:55) at GoogleToken.getToken (/usr/local/lib/node_modules/n8n/node_modules/gtoken/build/src/index.js:97:21) at JWT.refreshTokenNoCache (/usr/local/lib/node_modules/n8n/node_modules/google-auth-library/build/src/auth/jwtclient.js:172:36) at JWT.refreshToken (/usr/local/lib/node_modules/n8n/node_modules/google-auth-library/build/src/auth/oauth2client.js:153:24) at JWT.getRequestMetadataAsync (/usr/local/lib/node_modules/n8n/node_modules/google-auth-library/build/src/auth/oauth2client.js:298:28)
Fix got released with n8n@1.60.0
Bug Description
I am unable to interact with any Google Cloud service that uses a service account. I have tried with BigQuery and Vertex AI so far. The error in the console shows the error: call to gauth.request message: error:1E08010C:DECODER routines::unsupported
To Reproduce
Expected behavior
The BigQuery Node should run successfully and return results.
Operating System
Docker
n8n Version
1.53.2
Node.js Version
20
Database
PostgreSQL
Execution mode
main (default)