AWS Secrets Manager external secrets bug w/Google

[bcharleson]

Describe the problem/error/question

Hello n8n team!

We are facing a potential bug issue that we are seeing using the AWS secrets manager. Google seems to be the only one that is not passing through the token. All other external secrets are passing through appropriately.

We have the enterprise self-hosted n8n with v 1.77.0 and the bug still persists.

Let me know if I need to route this any other direction but figured the community would be a good start.

Thanks!

Brandon

What is the error message (if any)?

API token is not passing through

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Debug info

core

• n8nVersion: 1.77.0
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.2
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: memory

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/133.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2025-01-30T02:52:15.216Z}

[Joffcom]

Hey @bcharleson,

We have created an internal ticket to look into this which we will be tracking as "GHC-670"

[bcharleson]

Awesome, thank you!

[bcharleson]

@Joffcom -- if you don't mind, can we please loop in @iandreileo into this ticket? We are working together on this. Thanks!

[Joffcom]

Are you using oauth with other tools as well with a similar pattern to the secret?

[iandreileo]

Hi @Joffcom ,

No, we don't.

It seems like the problem is somewhere on the OAuth nodes from Google or something because we use the AWS secrets managers with other nodes in n8n, and it works perfectly.

Also, it seems like the secrets are correctly retrieved by n8n, but they are not added in the OAuth request.

Thanks!

[Joffcom]

Hey @iandreileo,

Perfect thanks, I will pass this over to the team that looks after secrets so they can debug it a but more. I suspect it won't just be Google credentials it will be all OAuth ones. For now it might be worth not using the secret so you can at least connect, Someone from the team will be in touch once they pick this up.

[iandreileo]

Hello,

Is there any news here?

Thanks so much!

[Joffcom]

Hey @iandreileo

It is being looked into, someone from the team will be in touch if they have any other questions.