Currently Workbench supports TLS connections/communication between its Workbench IO Application(s).
For example a Workbench IO Application in APAC can communicate with a Workbench IO Application in EMEA, providing secure messaging of Alarm, Changes, Channel Monitoring and Auditing events across the WAN, to enable this Workbench IO "APAC" to Workbench IO "EMEA" connection/communication, the respective Workbench Host Objects must first be TLS Enabled.
NOTE
- TLS connections to Workbench IO and Kibana (essentially the main Workbench UI) is currently NOT supported
- TLS connections from Workbench IO Applications at different Data-Centers is supported
- TLS connections to Elasticsearch has to be enabled when enabling Elasticsearch Authentication
- TLS connections to ZooKeeper is NOT supported
- TLS connection from Workbench to Engage Configuration Server is supported
- TLS connection from Workbench to Engage Solution Control Server is supported
- TLS connection from Workbench to Engage Message Server is supported