Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: a way to have variables available to flows\nodes without the value being visible as text #5065

Open
SynoUser-NL opened this issue Jan 30, 2025 · 1 comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do

Comments

@SynoUser-NL
Copy link

Description

Use case:
we have different people working on flows, for some of which they need access to resource credentials. For some credentials it is not desirable to have these generally available.
For this, a system like in Powershell where you can store credentials in an object and save and recall that object for later or other use and the password is protected, would be helpful.

Difficulty here is that the people working on flows are (and need to be) FF Admins as well. So there would need to be a kind of system where an admin could define credentials or a string, (for API keys or bearer tokens, or just a password) which can then be used by all admins in a team in flows. This "protected" string would then not ever reveal its content in a user interface (debug messages, on screen dashboards, etc,).

Also see:
https://discourse.nodered.org/t/managing-secrets-in-flowfuse/87786/10

Which customers would this be available to

Enterprise Tier Only (EE)

Have you provided an initial effort estimate for this issue?

I am not a FlowFuse team member

@SynoUser-NL SynoUser-NL added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do labels Jan 30, 2025
@knolleary
Copy link
Member

This is quite a hard problem to solve; it would require a whole new mechanism inside Node-RED itself and I'm not sure what that would look like.

The problem comes down to how these values would get used inside Node-RED.

Ultimately, these values need to be accessed by the Nodes so they can be used. So there will need to be an API available for Nodes to retrieve the values. With that API, anyone could write a node that grabs the value and attaches it to a msg - at which point we no longer have any control over what happens with that value.

Whilst this issue is pitched as a possible solution to a problem, I think we may want to think about the problem some more to see if there are alternative approaches to address it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do
Projects
Status: No status
Development

No branches or pull requests

2 participants