I have the following scenario.
I have one server, running two node-red instances, e.g. myserver.net/nodered1 and myserver.net/nodered2.
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.