Thank you for your fast reply. Thats what I already tried but that didn´t worked: pic
EDIT: My code in the settings is not disabled but you posted the part which is the one I enabled to have a password protection. I wouldn´t like to disable the password.
can you say more about the hardware? Node-Red is running on which device?
Have you tried typing this address in a browser (chrome ...) : http://192.168.1.54:1880/settings to access the settings from another device on the same network.
Replace 192.168.1.54 with the IP address of your hardware where run Node-Red
Sure. I am running it on an Raspberry Pi 4 and I tried to access the settings from the browser of the raspberry itself. The result is the same: "Unauthorized".
This: pic
PS: setting are also included.
EDIT: I am no expert in auth-stuff but I think it s no typical basic auth used by Node Red.
If you have admin auth set up, you cannot access the settings unless your current browser session is logged in. If you go to the normal Editor page in the same browser session and log in, you should then be able to see the output. Just tested that on 2 of my instances and it works.
Can you temporarily comment the lines about adminAuth and reboot NR. Just to confirm that you have access to the settings, without NR security ?
Therefore, there is no reason why it should not work, as our security expert testifies
maybe there is a way to parse the version number from a file. I tested to read a file from pi/.node-red/ and it worked (no access violation). But I could not find out where/if the version number is stored there.
It is to be expected that the URL "http://192.168.0.60:1880/settings" will give the "unauthorized" message as long as NodeRED has been secured using adminAuth:
But I was expecting the http request node to handle this correctly when adding:
.... or am I mistaken? Cause it certainly still returns "unauthorized"
I saw that the 1st http (local) request node indicates : actualVersion: "v"
Check that there are 36 in the "substring" Function node str.substring (31.36);
In this function I extract 5 characters from the payload from position 31 to 36
@knolleary pointed me in the right direction. I had to use bearer authentication and supply a valid access token to avoid the "unauthorised" error. Then it works.