Determine Whether the User Identity Is Available
In the described groov AR1 workflow, a user enters data on a groov page and Node-RED sends that data to a database. The available evidence establishes that Node-RED cannot also capture the name or ID of the user logged into that page. Store the entered values independently of user identity unless the application supplies an identity through another supported mechanism.
Understand Why Node-RED Audit Logging Does Not Solve It
Enabling Node-RED audit logging does not associate groov users with audit events. The groov environment does not use Node-RED’s built-in authentication, so Node-RED has no authenticated-user context to attach to page activity or database records.
| Data item | Availability to Node-RED | Engineering implication |
|---|---|---|
| Values submitted by the page | Available through the configured flow | Node-RED can log the submitted process data. |
| groov logged-in user name or ID | Not available in the described integration | Do not treat the Node-RED audit log as a user-attribution record. |
| Node-RED audit events | Available after audit logging is enabled | Events still lack groov user identity. |
Handle the Settings File Scope Correctly
For groov EPIC or RIO systems with shell access enabled, the Node-RED settings file is located at /usr/share/nxtio/services/node-red/settings.js. This path is evidence-supported only for EPIC or RIO; the evidence does not confirm that it applies to the groov AR1.
Editing that file to enable audit logging can provide audit events, but it does not bridge the authentication boundary. Verify the result by generating an event, inspecting the resulting audit record, and confirming that no groov user field is attached. If traceable attribution is mandatory, treat user identification as an unresolved application requirement rather than inferring identity from the audit event.
FAQ
Can Node-RED capture the user logged into a groov page?
No. In the described groov integration, Node-RED cannot collect the logged-in user’s name or ID with the submitted page data.
Does enabling Node-RED audit logging record groov usernames?
No. Audit events do not include groov users because the environment does not use Node-RED’s built-in authentication.
Where is the Node-RED settings.js file on groov EPIC or RIO?
With shell access enabled, it is available at /usr/share/nxtio/services/node-red/settings.js. The evidence does not establish this path for the groov AR1.