strange behavior - just checking - node-red admin hash-pw does not work when put in to the settings.js

[Laro88]

I don't see a bug on this - however it might as well be a raspberry / node.js problem The authentication for the editor is working, however the password is always rejected.

I get entries in the log that indicates the access attempt so I presume things are fine

1 Jan 20:47:06 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"d751713988987e9331980363e24189ce"},"retain":true}

I wrote the small snippet below (for some reason is required a package.json - the generated password did also not work. node -e "console.log(require('bcryptjs').hashSync(process.argv[1], 8));" your-password-here

It is a clean raspberry 3 with the small raspberry pi os (no ui) and ssh, mc, wifi and node 12.20.0 - and node.red seems fine without security. firmware is:

pi@pi3test:~/test $ uname -a
Linux pi3test 5.4.79-v7+ #1373 SMP Mon Nov 23 13:22:33 GMT 2020 armv7l GNU/Linux

If there are no known problems / wierd behaviors then just close this one - I can run without security for the time being.

[hardillb]

Please read the template you were shown when you opened this issue. It asks you to raise questions on the Forum, Slack or Stack Overflow first as we only use issues for actual defects in the code.

It also gathers all the required information we need to be able to make a start on debugging any issue.

We need to see the changes you made to settings.js and exactly which instance of the file you edited.

It's also not 100% clear what problems you are seeing here, is it

1. That you can sign into the editor, but you can't deploy?
2. You can't sign into the editor at all?

[Laro88]

I will switch to slack in the morning if I find the time @hardillb