# Core node to store credentials

**URL:** https://discourse.nodered.org/t/core-node-to-store-credentials/23774
**Category:** Feature Requests
**Created:** [28 March 2020 09:17 UTC](https://discourse.nodered.org/t/core-node-to-store-credentials/23774 "2020-03-28T09:17:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![hklages](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hklages/32/23899_2.png) [@hklages](https://discourse.nodered.org/u/hklages)
#### Post date: [28 March 2020 09:17 UTC](https://discourse.nodered.org/t/core-node-to-store-credentials/23774/1 "2020-03-28T09:17:39Z")

</div>

Hi.

**Request**  
Provide a node similar to [credential node](https://flows.nodered.org/node/node-red-contrib-credentials) in the **core** node set. Another option could be to have a tic in the change/inject node to identify a string as a credential.

**Background**  
I thought to be safe because all my tokens, bearer, passwords are stored in permanent global variables. So there is no risk to use projects and publish flows to github.

Recently I had to change my AWS root key several times - using inject node to update the global variable. And I did commit and push ☹

After a short time I got an email from githhub, then multiple email and calls from Amazon - my AWS root key was exposed on the internet.

**Point of view**  
NodeRED is in the core of internet and IoT - a lot of REST API and bearers/tokens/credentials.

Furthermore, security is extremely important. A credential node in the core package is very useful and would make all users more aware of the importance of security.

---

<div class="post-metadata">

### Author: ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)
#### Post date: [28 March 2020 09:34 UTC](https://discourse.nodered.org/t/core-node-to-store-credentials/23774/2 "2020-03-28T09:34:42Z")

</div>

> [@hklages](#):
>
> Provide a node similar to [credential node](https://flows.nodered.org/node/node-red-contrib-credentials) in the **core** node set.

Why do we need it in the core node-set? It's easy enough to add it from the library if users want to use it.

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [28 March 2020 09:50 UTC](https://discourse.nodered.org/t/core-node-to-store-credentials/23774/3 "2020-03-28T09:50:03Z")

</div>

We have already spoken to the maintainer of the credentials node about incorporating its functionality in the core. It will happen. Just needs time and bandwidth along with everything else.

---

<div class="post-metadata">

### Author: ![hklages](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hklages/32/23899_2.png) [@hklages](https://discourse.nodered.org/u/hklages)
#### Post date: [30 March 2020 06:25 UTC](https://discourse.nodered.org/t/core-node-to-store-credentials/23774/4 "2020-03-30T06:25:40Z")

</div>

@Paul: because its sensitive - similiar arguments as in  
[forumdiskussion](https://discourse.nodered.org/t/how-to-assure-that-some-flow-constants-like-api-keys-also-become-stored-in-the-credentials-file/962/4)

@knolleary: good decision 🙂 Thanks

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [29 May 2020 06:25 UTC](https://discourse.nodered.org/t/core-node-to-store-credentials/23774/5 "2020-05-29T06:25:42Z")

</div>

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