AWS Secrets Manager External secrets bug w/Google

[brandoncharleson]

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

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

• n8n version:
• Database (default: SQLite):
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• Running n8n via (Docker, npm, n8n cloud, desktop app):
• Operating system:

[brandoncharleson]

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

[ria]

Hi @brandoncharleson

Please note, as Enterprise customer, you can avail of our email support at [email protected] directly, if you want a quicker response.

Have you tried to set up the credential from scratch again? Can you share which other Google credentials you’ve experienced this with?

Thanks!

[ria]

Actually @brandoncharleson, I’ve just confirmed that this is a bug and we’re already working an a fix for this.

We’ll update this thread here when the fix will be released.

[jan]

New version [email protected] got released which includes the GitHub PR 13110.

[brandoncharleson]

Thanks Ria!

[brandoncharleson]

Thanks Jan!

[JensAtRokt]

We are encountering the same issue, tried upgrading to the latest version available at the time (1.84).

Let me know if I can provide any further information to help resolve the problem