Why does the heartbeat with TLS encryption not work with default settings?

We changed some settings to meet modern IT compliance guidelines:

One of the most significant changes is that the services at the CS141 & BACS systems are now OFF by default, except the web server (you need it to access the CS141 web interface).

At “Devices > Setup”, you need to enable the UNMS & RCCMD Trap Service – this will enable the RCCMD Heartbeat function. Within RCCMD, open connections and take a look at “Protocol”:

Accept only SSL/TLS connections is enabled by default.

If you intend to use “heartbeats”, you will get a communication loss issue until both, CS141/BACS and RCCMD use a harmonized configuration:

Both endpoints need to use “SSL/TLS ON or OFF” or it won’t work. Depending on which certificate you use, you may also choose “ Reject expired SSL/TLS certificates”.

Please keep in mind:

It is in the nature of using default (or example) certificates to be rejected in case of “reject expired certificates” is selected. If this function is wanted, a set of valid certificates is needed. For valid certificates, please contact the local system administrator and ask for appropriate certificates.