[checkmk-commits] [tribe29/checkmk] db4dce: Disentangle CA and Liveproxy config domains

Branch: refs/heads/2.0.0 Home: https://github.com/tribe29/checkmk Commit: db4dce98521852434f2eb6c651d1a30b352aa4c1 https://github.com/tribe29/checkmk/commit/db4dce98521852434f2eb6c651d1a30b3… Author: Joerg Herbel <joerg.herbel(a)tribe29.com> Date: 2021-11-19 (Fri, 19 Nov 2021) Changed paths: M cmk/gui/watolib/config_domains.py Log Message: ----------- Disentangle CA and Liveproxy config domains The CA config domain called the activation function of the Liveproxy config domain, which had no effect anyway (since the CA config domain cannot change the config of the lpd). Change-Id: Ie3ea8492c37378d32d1480b21dc46b1df977aa79 Commit: fd6273267e78738f961e1b700f0aa187943abff2 https://github.com/tribe29/checkmk/commit/fd6273267e78738f961e1b700f0aa1879… Author: Joerg Herbel <joerg.herbel(a)tribe29.com> Date: 2021-11-19 (Fri, 19 Nov 2021) Changed paths: A .werks/13518 Log Message: ----------- 13518 FIX Liveproxy Daemon: React to changes in CAs without manual restart When using encrypted connections, the CAs trusted by the Liveproxy Daemon (LPD) can be administrated via the global setting "Trusted certificate authorities for SSL". Depending on the current state of the LPD, a manual restart was necessary for the LPD to take changes in this setting into account. In particular, removing a CA of a remote side to which the LPD was currently connected to did not result in a loss of connection without a restart. CMK-8933 Change-Id: Ieb3025b64ee4474625d453afa1c3692c138d9e7d Compare: https://github.com/tribe29/checkmk/compare/3ff1353dff5b...fd6273267e78