(adminAuth)unable to login node-red

#1

my problem is unable to login in node-red.the node-red is normal running if remove the adminAuth in setting.js files.


But if I set adminAuth in setting.js file with username/password:admin/admin

then I restart the node-red. the node-red is normal starting.

But i can't login in the node-red editor

#2

Have you purposely not removed the // from the start of the sessionexpiry line?

#3

That's an optional field so won't have an bearing here.

#4

if i don't remove the "//", the node-red login web will be missing, and can editor the flow directly. The Node-red flows work normally.


Now i want to use adminAuth. i have already test adminAuth settting successfully in CPU:ARMv7 Processor rev 5 (v7l) platform, But i test adminAuth setting failed in CPU:MIPS 1004Kc V2.15.

I don't know how to find the Error for this problem?

#5

could you give me some advices for how to find the error and solve it.

#6

could you give me some any reply?

#7

Do you have any good idea for this problem? thanks very much!

#8

It is hard to tell from the screenshots exactly what error you hit.

Is it:

  1. you cannot enter a password in the dialog (known issue: https://github.com/node-red/node-red/issues/1982)
  2. you can enter a password and click login but the request hangs (you last screenshot looks like that)
  3. you can enter a password and click login, but it returns a 'login failed' type message?

Have you looked at the JavaScript console for any errors?

#9

i can enter a password and click login but after i click login the web request hangs continuous about 40 seconds,then it returns a 'login failed' type message. i have also use a error username or error password to test , there are same phenomenon.About the JavaScript console without any errors printing.
This is the Caught file.

#10

Can you edit your settings.js file and set the logging.audit value to true and the logging.level to "trace". Then restart Node-RED and try again. Then see what the Node-RED log shows.

It is odd for it to take 40 seconds to respond - I'm not sure what could cause that. What type of machine is this running on?

#11

#12

I think that the username and password did not work .

#13

#14

#15

What hardware is this running on? The uname command says Linux router - so is this a low powered, low memory router type device? That could explain why it takes so long to respond - the bcrypt password hashing can be quite slow on slow devices. But it doesn't explain why the login fails.

When node-red is installed, it tries to install the bcrypt module to handle the password hashing. This is a binary module that doesn't always successfully install. As a fall back, we also install bcryptjs - a pure javascript implementation that will install cleanly, but is much slower than the binary module.

Can you try reinstalling the bcrypt module; in the directory /mnt/sd/node-js-app/node-red-0.19.5/ run npm install bcrypt

#16

Node-red run in embedded Router device(Linux operating system), i know the bcrypt module that doesn't always successfully install.i have checkout that bcrypt is install Success.