Multiple instances authentication


I have the following scenario.
I have one server, running two node-red instances, e.g. and
Both instances use the builtin user-password authentication.
I would like to open and edit both node-red editor instances into two tabs of the same browser.

Unfortunatly, both instances will store into the browser local storage the "auth-tokens", and therefore,
the second instance will overwrite the auth token of the first.
E.g. if I first do login on nodered1, and then on nodered2, nodered2 will work fine, but to successfully deploy or work with nodered1, I have to re-do login, but this will overwrite the nodered2 token, and so on.

Question: is there a way to prevent this overwrite? E.g. a simple settings.js option to customize where/how the auth token is stored.


Hi @FStefanni

this is a known issue that was recently raised with the auth mechanism we have - you can't have two instances on the same domain.

There's no workaround - we need to change how the auth works in the editor.


thank you for the quick reply.
So I'll wait for the issue closing.


You could open the other instance in a private/incognito browser tab. That way the local storages won't interfere.

Or open the second one in a different browser.

Does it work with a different sub-domain? If so, that should be easy to do.

Otherwise, like others, I'd recommend different browser profiles. I have to do this for work as I have accounts on the same service across multiple tenants, Office 365 in particular. The new Microsoft Edge (Chromium based) is excellent for this. But plenty of other browsers also support it. It is better than using an in-private session as that doesn't remember your settings.

Different sub-domains is fine and is how all of the existing multi-tenant node-red systems have approached it.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.