You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to have the /ui (dashboard) accessible by read-only user accounts but I have no idea how to do that :)
I tried to setup SK for read-only access, made a read-only user but still no success.
It seems the readApi/ui is accessible only by admin users
Also, it seems the signal-node-red does not have the same settings as a stand alone node-red installation and no documentation available...
At least I couldn't find it.
There is any way to have /ui accessible by non-admin users? Or even for non-authenticated users
Thank you,
Seb
The text was updated successfully, but these errors were encountered:
Sorry, there's currently no way to do it that I know of. Does node-red support read only users? If it does, then it could probably made to work, but not something that would be high on my TODO list.
All the existing docs are what you see in the GitHub repositories.
Because I am totally beginner with node-red I tried a standalone installation on a Pi Zero W.
By default, i have totally free access to admin and ui areas. Following this I was able to setup an admin account (for admin area) and a user account for ui
I just had to uncomment few lines and generate some passwords...
I also tried read only permissions account, for admin area. It is working, too
Hello,
I am trying to have the /ui (dashboard) accessible by read-only user accounts but I have no idea how to do that :)
I tried to setup SK for read-only access, made a read-only user but still no success.
It seems the readApi/ui is accessible only by admin users
Also, it seems the signal-node-red does not have the same settings as a stand alone node-red installation and no documentation available...
At least I couldn't find it.
There is any way to have /ui accessible by non-admin users? Or even for non-authenticated users
Thank you,
Seb
The text was updated successfully, but these errors were encountered: