Debug node when logged in as read only users

iot.regenesis · 26 January 2024 04:07

Hello everyone,

I am working in a team, and I am the one who is developing the flows in node-red on remote PC.
I do not want other team mates messing-up the flows/codes.
I want them only to see the output of debug messages, thus I created for them logins as read-only user.

I noticed that when login as read-only users, I can not see the debug node output messages.

This is what I did:
I opened two browsers. On one window I logged in as admin, and on other window I logged in as read-only. Both browsers were opening the same flow.
On read-only window I can click to activate/deactivate debug nodes but did not effect the debug message viewer. Only when I activate/deactivate debug nodes in admin browser the debug message window on both browsers were effected.

Questions:

is that the normal behavior of debug node when logged in as read-only user?
how do I allow read-only user to see debug messages if not using debug nodes?

This is the version I use:

└─▪  node-red -v
26 Jan 03:45:08 - [info] 

Welcome to Node-RED
===================

26 Jan 03:45:08 - [info] Node-RED version: v3.1.3
26 Jan 03:45:08 - [info] Node.js  version: v18.19.0
26 Jan 03:45:08 - [info] Linux 6.5.0-0.deb12.1-rt-amd64 x64 LE
26 Jan 03:45:08 - [info] Loading palette nodes

Best regards to you all!

marcus-j-davies · 26 January 2024 18:25

Welcome @iot.regenesis.

As a Read Only user - You cannot modify the state of a node, and enabling the debug node is a form of modification.

The permission needed is actually debug.write.

github.com

node-red/node-red/blob/9bd71319143a26f654810d0d05ccc08c7603a95d/packages/node_modules/@node-red/nodes/core/common/21-debug.js#L269


      
                      if (node !== null && typeof node !== "undefined" ) {
                          setNodeState(node, state === "enable");
                      }
                  })
                  res.sendStatus(state === "enable" ? 200 : 201);
              } else {
                  res.sendStatus(400);
              }
          })
          
          RED.httpAdmin.post("/debug/:id/:state", RED.auth.needsPermission("debug.write"), function(req,res) {
              var state = req.params.state;
              if (state !== 'enable' && state !== 'disable') {
                  res.sendStatus(404);
                  return;
              }
              var node = RED.nodes.getNode(req.params.id);
              if (node !== null && typeof node !== "undefined" ) {
                  setNodeState(node,state === "enable");
                  res.sendStatus(state === "enable" ? 200 : 201);
              } else {

So maybe you as admin - just deploy the flow with the debug node enabled?
or add the permission to the read only user to allow them to enable the debug node?

Note: I have not tested this myself
@knolleary - would this be correct?

permissions: ["read","debug.write"]

iot.regenesis · 9 February 2024 16:21

hi @marcus-j-davies

Thanks for the explanation!

I had made their work easier by using flogger node .. no need for them to login to nodered,

system · 23 February 2024 16:22

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Debug does not show outputs General debug	10	93	15 September 2024
Node-RED Flow tabs General	7	175	12 August 2023
Permissions read should allow "inject" button General	5	994	23 April 2020
Troubleshooting what triggered a flow General	7	799	16 June 2021
[Announce] Easy way of preview live data in your flows Share Your Nodes	7	1485	4 April 2023

Debug node when logged in as read only users

Related topics