Just someone asked something and I may have a flow that does what they want. But one node's has a key in it.

Ok... I think I get it. The key you're referring to is your "license" if you will, to use that API - Most services offering access to data requires to know who is using that API (and to detect if that user is absuing the services provided) If exporting a flow that uses a key that is assigned to "You" - its best to redact that key. So the user "reusing" that flow - needs to get there own key. before pasting the flow, do a search and replace to remove your key replace("xxxxxxx","Get-Your-Own-Key") I hope this helps

[image] Trying_to_learn: I guess it confused me with the global declaration - me being anal - when it is more a flow. I use a global context variable because it is set on one editor tab and used on a different tab. When I export the entire flow that uses the variable, as I did above, you can see the name of the variable but not it's value. [image] Trying_to_learn: (Dunno if you could *cheat) and set/inject the credentials on one flow then link to that flow (if only used on one flow) and have the change node on that flow and set it to flow rather than global. Hmm On another machine I have multiple weather APIs all together on one editor tab. I can access them with links, passing in msg.latitude, msg.longitude and msg.apikey. In that case the API key[s] are set on the flow that links to this one. They could be flow context variables on that flow. [image]

Yeah, ok, I didn't read the first flow quite as well as I should. I took it as you entered the key in the inject node and sent it to the change node. MY MISTAKE - sorry. So, if I did it that way, I could link the inject to change node and put the change node on the other flow so the key would be flow and not global. Again, I am not trying to be petty, just the brain fog is sort of corrupting things and I am discussing it to help clear the fog.

As @GogoVega and myself have noted it is probably best to use environment variable credentials, as they are kept securely, these can be set by flow or group or globally in the setting.js. [chrome_screenshot_5 Aug 2024 11_30_52 BST] They are held in the flows_cred.json, in the .node-red directory and are encrypted You can access them in a change node, function node or template node. [chrome_screenshot_5 Aug 2024 11_44_55 BST] example [{"id":"613df62afc8a16bf","type":"tab","label":"testing","disabled":false,"info":"","env":[{"name":"my_api_key","type":"cred"}]},{"id":"9a35d547d76baf73","type":"inject","z":"613df62afc8a16bf","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":100,"y":80,"wires":[["f88999acad5cab67","1d928297cda93681","d26902a1a5af9bb6"]]},{"id":"56631130f4851387","type":"debug","z":"613df62afc8a16bf","name":"debug 2575","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"payload","targetType":"msg","statusVal":"","statusType":"auto","x":450,"y":60,"wires":[]},{"id":"1d928297cda93681","type":"function","z":"613df62afc8a16bf","name":"function 159","func":"msg.payload = env.get(\"my_api_key\")\nreturn msg;","outputs":1,"timeout":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":290,"y":120,"wires":[["56631130f4851387"]]},{"id":"f88999acad5cab67","type":"change","z":"613df62afc8a16bf","name":"","rules":[{"t":"set","p":"payload","pt":"msg","to":"my_api_key","tot":"env"}],"action":"","property":"","from":"","to":"","reg":false,"x":280,"y":60,"wires":[["56631130f4851387"]]},{"id":"d26902a1a5af9bb6","type":"template","z":"613df62afc8a16bf","name":"","field":"payload","fieldType":"msg","format":"handlebars","syntax":"mustache","template":"{{env.my_api_key}}","output":"str","x":320,"y":180,"wires":[["56631130f4851387"]]}] Enter your key in the flow properties environment var tab shown in first image. I have shared the flow and the my_api_key was set to above image value, you can see in the flow i posted that they have not been shared.

I'll have to look more into passing the key via the message. Alas I have a problem that I get weather for a few places so I am going to have to think about that a bit more.

Thanks. That way does look nicer. (No offense to @TotallyInformation or @jbudd ) I'm changing horses a bit just now but this way seems to feel nicer to me. I'll sit down and see if I can understand this way.

Small reminder :grin: [image] What is the purpose of starting the 'global' flow in the source code when starting Flows Core Development [image]

I'm now kinda more confused than before. I am sure the node I am using is openweathermap but when I look at the posts/flows just now, the node when opened looks way different to the one I have. Oh, ooops. So the newer flows are not using that node, but a http request node. But with the messages sent into it, it gets what I would get from the openweathermap node. Yes? And, despite a few attempts, I don't know what the correct address is I should be using, as every time I try I get an error back to me. :frowning:

This is what I have in my notes: OpenWeatherMap's OneCall API One Call API 3.0 - OpenWeatherMap - free tier gives 1000 calls per day. Icons: https://flows.nodered.org/flow/d7af9f5d6f6923324466c58ea4f0655f

Thanks. It wasn't your flow that threw me, but with the http request ones, nothing works. I use the actual node. It works. If I use the http request node and weak where I get the weather I get errors like crazy. I'm trying to go with that as it seems the easier way to go. (He said now kind of regretting it) This s to what I changed the function node just before the node: const owmid = global.get("myAPIkey") || "NoAPIkey" msg.url = "https://api.openweathermap.org/data/" msg.url += "city=" + msg.payload.city + "&country=" + msg.payload.country + "&units=metric" msg.url += "&appid=" + owmid return msg; note the change to the URL. msg.url = "https://api.openweathermap.org/data/3.0/onecall?" is the old/original one. If I use as was I get: {"cod":401,"message":"Please note that using One Call 3.0 requires a separate subscription to the One Call by Call plan. Learn more here https://openweathermap.org/price. If you have a valid subscription to the One Call by Call plan, but still receive this error, then please see https://openweathermap.org/faq#error401 for more info."} Which says I have not given a valid key - or it is there. I stuck a debug node and it is there. I don't know what kind of account @marcus-j-davies has. I tried to make it for my account - guessing. No luck. I'll have to try and find this out.

Openweathermap have upgraded to version 3 of their api, so you would need to sign up for a new subscription to get api-key to use V3. The update openweathermap node now use V3 also, that to will require a new subscription. As noted in the error message.

Node-RED

Node-RED Forum

If I post a node with a key, is that key included in the post?

General

GogoVega 5 August 2024 10:54 33

Small reminder

Topic		Replies	Views
How do you securely give credentials to a stand-alone Function node? General security , function-node	61	1603	8 December 2025
Your flow credentials file is encrypted using a system-generated key General	57	34043	28 July 2021
Flow credentials cannot be decrypted General	8	2726	31 May 2022
Email node IDs and openwethermap API KEY disappears when copy flow.json General	4	562	26 February 2022
Database location General	8	268	11 March 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

If I post a node with a *key*, is that key included in the post?

Related topics

If I post a node with a key, is that key included in the post?