Skip to content

Commit 801b3b8

Browse files
Merge pull request #42 from OS2iot/feature/add-tls-documentation
Added a small section on tls in the installation guide
2 parents da3f296 + 21f94e2 commit 801b3b8

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

source/installation-guide/installation-guide.rst

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,12 @@ Once the path is added run:
100100

101101
More docker related troubleshooting can be found at: https://github.com/OS2iot/OS2IoT-docker#troubleshooting-faq
102102

103+
Security
104+
--------
105+
106+
OS2IoT only supports tls 1.2+. It is however recommended to only use tls 1.3.
107+
108+
103109
Running in Kubernetes
104110
---------------------
105111

@@ -292,9 +298,9 @@ Generate files:
292298
293299
4. Create the server key (for the broker) with the command: :code:`openssl genrsa -out server.key 2048`
294300
295-
6. Create the server signing request with the command: :code:`openssl req -new -out server.csr -key server.key`. You will be prompted to enter some informations. These values are not important, except one: "Common name". Common name HAS to be the ip/hostname of your broker. The rest of the values should not be exact the same as in step 4.
301+
5. Create the server signing request with the command: :code:`openssl req -new -out server.csr -key server.key`. You will be prompted to enter some informations. These values are not important, except one: "Common name". Common name HAS to be the ip/hostname of your broker. The rest of the values should not be exact the same as in step 3.
296302
297-
7. Create the server certificate (that is signed by the CA) with this command: :code:`openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt -days 360`. You will be prompted to enter the password from step 3.
303+
6. Create the server certificate (that is signed by the CA) with this command: :code:`openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt -days 360`. You will be prompted to enter the password from step 3.
298304
299305
If you want to get docker container with mosquitto running, then follow these steps:
300306
@@ -304,7 +310,7 @@ If you want to get docker container with mosquitto running, then follow these st
304310
305311
3. Copy the files ca.crt and ca.key and place them in OS2IoT-backend/resources.
306312
307-
4. Update the :code:`MQTT_BROKER_HOSTNAME` with the ip/hostname that you used for step 4 and 6, and :code:`CA_KEY_PASSWORD` with the password that you entered in step 3 in the docker-compose.yml file placed in OS2IoT-docker.
313+
4. Update the :code:`MQTT_BROKER_HOSTNAME` with the ip/hostname that you used for step 3 and 5, and :code:`CA_KEY_PASSWORD` with the password that you entered in step 2 in the docker-compose.yml file placed in OS2IoT-docker.
308314
309315
If you want to use kubernetes to host mosquitto then you need some futher steps.
310316
@@ -318,4 +324,5 @@ Prerequisites: kubectl installed and accesible from path
318324
319325
4. Update the empty values in OS2IoT-docker/helm/charts/mosquitto-os2iot/values.yaml
320326
321-
5. Update the :code:`MQTT_BROKER_HOSTNAME` with the ip/hostname that you used for step 4 and 6 in the steps above, and :code:`CA_KEY_PASSWORD` with the password that you entered in step 3 in the steps above, in the file "OS2IoT-docker/helm/charts/os2iot-backend/deployment.yaml".
327+
5. Update the :code:`MQTT_BROKER_HOSTNAME` with the ip/hostname that you used for step 3 and 5 in the steps above, and :code:`CA_KEY_PASSWORD` with the password that you entered in step 2 in the steps above, in the file "OS2IoT-docker/helm/charts/os2iot-backend/deployment.yaml".
328+

0 commit comments

Comments
 (0)