# IBM Bluemix node red HTTP security issues

**URL:** https://discourse.nodered.org/t/ibm-bluemix-node-red-http-security-issues/35653
**Category:** General
**Created:** [10 November 2020 07:12 UTC](https://discourse.nodered.org/t/ibm-bluemix-node-red-http-security-issues/35653 "2020-11-10T07:12:50Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![mako](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@mako](https://discourse.nodered.org/u/mako)
#### Post date: [10 November 2020 07:12 UTC](https://discourse.nodered.org/t/ibm-bluemix-node-red-http-security-issues/35653/1 "2020-11-10T07:12:50Z")

</div>

Hi.

We are running Node-red on a local machine "ComputerA" with port forwarding enabled. make changes in the settings.js file to add the HTTP node security. as per the Node-red docs

```auto
httpNodeAuth: {user:"user",pass:"$2a$08$zZWtXTja0fB1pzD4sHCMyOCMYz2Z6dNbM6tl8sJogENOMcxWV9DN."},

```

We have generated credentials using bycrpt generator. make a simple HTTP in flow with response node.

On another computer "Computer B" on a different network, i can send a post request to computer A with the basic authentication and it works OK.

OK.  
I try the same thing with IBM bluemix. Altering the bluemix-settings.js. push the changes, the delivery pipeline completes.  
I then send the request to the bluemix node-red version. doesn't matter if I have the basic auth enabled or not the message gets through. Its like it doesn't pick up the settings.js.  
I restarted the app as some other people have done according to this forum, still no change.

Any ideas?

Thanks

---

<div class="post-metadata">

### Author: ![mako](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@mako](https://discourse.nodered.org/u/mako)
#### Post date: [12 November 2020 12:36 UTC](https://discourse.nodered.org/t/ibm-bluemix-node-red-http-security-issues/35653/2 "2020-11-12T12:36:11Z")

</div>

Issue was solved.  
I had deleted the deploy stage in the delivery pipeline as it was failing.  
After some researching i found that you have to stop node red to free up resources so the delivery stage can complete.

- I added the deploy sage back to the tool chain

- Stopped NodeRED

- Run the deploy stage, it passed, finally!

- Restarted node red, and bingo the HTTP Auth worked.

---

<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: [26 November 2020 12:36 UTC](https://discourse.nodered.org/t/ibm-bluemix-node-red-http-security-issues/35653/3 "2020-11-26T12:36:16Z")

</div>

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