Skip to Content
Last modified by Tobias Wintrich on 2024/06/03 15:08
Show last authors
1 When using your own certificate infrastructure, it is necessary to make the root certificate known to the clients to ensure secure communication.
2
3 RangeeOS offers various options for deploying the certificate to a client or distributing it via a TCMS.
4
5 {{toc/}}
6
7 = Via the Thin Client's Kommbox =
8
9 Under {{status title="Tools"/}} -> {{status title="Certificates"/}}, you have the option "Install Certificates" to transfer a certificate to the client.
10
11 Here you can choose whether to install the certificates "Global" (distributable via TCMS) or only "Local" (usable only by this client).
12
13 [[image:01_zertifikate_installieren.png||height="316" width="600"]]
14
15 = Via a TCMS =
16
17 == Certificate as Part of the Group Configuration ==
18
19 The certificates installed as described under "Via the Thin Client's Kommbox" with the option //"Global"// (distributable via TCMS) can be transferred to other clients as part of the group configuration. To do this, pull a new group configuration from the respective client after installing the certificate.
20
21 == Distribute Certificates via a ZIP Archive ==
22
23 Alternatively, you can also distribute all certificates to your clients via a ZIP archive. To do this, proceed as follows:
24
25 === On the TCMS Side ===
26
27 Open the TCMS Kommbox (https://IP-hostname without /tcms) and navigate to {{status title="Tools"/}} -> {{status title="Certificates"/}} -> {{status title="Global Settings"/}}. At this point, you can upload an archive containing all the required certificates. The certificates must all be located in the root directory of the ZIP archive and be Base64 encoded (cert/pem).
28
29 === On the Thin Client Side ===
30
31 Navigate here as well to {{status title="Tools"/}} -> {{status title="Certificates"/}} -> {{status title="Global Settings"/}} and check the box "//Download the certificate archive from TCMS//". This will cause the certificate archive to be downloaded from TCMS again at each startup.