# Self signed SSL on IBM Cloud platform?

**URL:** <https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599>\
**Category:** General\
**Tags:** security\
**Created:** [11 November 2021 20:45 UTC](https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599 "2021-11-11T20:45:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MegalomaniacGT](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/megalomaniacgt/32/39045_2.png) [@MegalomaniacGT](https://discourse.nodered.org/u/MegalomaniacGT)\
**Post date:** [11 November 2021 20:45 UTC](https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599/1 "2021-11-11T20:45:49Z")

</div>

Dear Users,

**Is it possible for me to generate a self-signed SSL/TLS certificate using the IBM Cloud platform?**  
I learned how to generate one using OpenSSL on raspberry pi but I am unfamiliar in the cloud realm.

some context:  
I am using IBM Cloud for the MQTT broker(using their IoT platform) and the NodeRed starter pack for the app part. I got the broker working fine, I am able to successfully send messages(from a pi) and it shows up on the event log, but now I am trying to send from the cloud version of nodered. The only part I am missing is the SSL/TLS certificate.

edit: I can see there is an import option, can I generate one using the IBM cloud terminal?

edit 2: looks like I was able to use the same certificate I used on the pi as long as they are different client id. you may mark this as resolved, unless someone can suggest a more optimal solution. this is project is merely for self learning of the IBM Cloud platform

---

<div class="post-metadata">

**Author:** ![MegalomaniacGT](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/megalomaniacgt/32/39045_2.png) [@MegalomaniacGT](https://discourse.nodered.org/u/MegalomaniacGT)\
**Post date:** [11 November 2021 21:13 UTC](https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599/2 "2021-11-11T21:13:20Z")

</div>

to expand on the client id concern, **how can multiple devices connect to the broker that's on IOT IBM cloud instead of one?** (I am trying to send messages from nodered(IBM cloud) to the broker, and have a pi subscribe to the topic to retrieve the message.)

---

<div class="post-metadata">

**Author:** ![MegalomaniacGT](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/megalomaniacgt/32/39045_2.png) [@MegalomaniacGT](https://discourse.nodered.org/u/MegalomaniacGT)\
**Post date:** [11 November 2021 21:23 UTC](https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599/3 "2021-11-11T21:23:07Z")

</div>

[https://cloud.ibm.com/docs/IoT?topic=IoT-ts](https://cloud.ibm.com/docs/IoT?topic=IoT-ts)

looks like I found out why, it requires unique IDs which is not possible to do in the way I am attempting, I have to use the API key instead for the subscriber

---

<div class="post-metadata">

**Author:** ![MegalomaniacGT](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/megalomaniacgt/32/39045_2.png) [@MegalomaniacGT](https://discourse.nodered.org/u/MegalomaniacGT)\
**Post date:** [11 November 2021 22:26 UTC](https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599/4 "2021-11-11T22:26:20Z")

</div>

heck yeah! I got it figured out after reading the documentation from IBM. I had to generate an API Key and use that for the client credentials. It now performs as I expected the way I want!

[https://www.ibm.com/docs/en/watson-iot-platform?topic=applications-communicating-mqtt](https://www.ibm.com/docs/en/watson-iot-platform?topic=applications-communicating-mqtt)

---

<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:** [25 November 2021 22:26 UTC](https://discourse.nodered.org/t/self-signed-ssl-on-ibm-cloud-platform/53599/5 "2021-11-25T22:26:34Z")

</div>

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