Chat Basic Auth issues in n8n UI

[lhunt-mb]

Bug Description

For some reason, we have all of a sudden had issues when using the internal Chat UI to test Chat webhooks - of a basic auth dialog appearing. The webchat triggered node is configured with a Basic Auth credential.

When entering the credentials into the basic auth dialog - it works fine. But then fails with 403 errors with other chat triggers we have with authorisation failed errors.

This seems to have started after creating another Basic Auth credential (not used in any workflows yet)

To Reproduce

1. Go to chat within workflow editor
2. Type a chat in
3. Basic Auth dialogue pops up
4. Enter credentials (which didn't need to do previously)
5. Chat works
6. Go to another workflow with a different basic auth credential
7. Chat now fails with "Authorization data is wrong!" response
8. Debugging in console - the request returns a 403 - and is using the incorrect Basic auth credentials (the one in the previous workflow)

Expected behavior

Multiple Basic Auth credentials work within the n8n internal test chat ui without manually entering in credentials, and working correctly.

Debug Info

Debug info

core

• n8nVersion: 2.11.2
• platform: npm
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: postgres
• executionMode: regular
• concurrency: -1
• license: enterprise (production)
• consumerId: 88259dd3-63f7-49d7-bf02-9fe63b2db99d

storage

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

pruning

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

client

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

Generated at: 2026-03-24T02:45:28.722Z

Operating System

Ubuntu Linux

n8n Version

2.11.2

Node.js Version

24

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

[n8n-assistant]

Hey @lhunt-mb,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7432".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7432