To establish ongoing communications between its brokering components and the system components in participating Horizon pods, Universal Broker has specific port and protocol requirements. Also, some specific DNS names must be reachable by the Horizon Cloud Connector for an environment configured with Universal Broker.
The DNS requirements are described in DNS, Ports, and Protocols Requirements When Using Horizon Cloud Connector and a Horizon Pod.
The Universal Broker client on the Horizon Cloud Connector establishes a persistent WebSocket connection with the Universal Broker service through port 443. The Universal Broker client receives connection requests from the service through a randomly selected port.
The Universal Broker client then forwards the request through a different randomly selected port to the Universal Broker plugin on the Connection Server. The Universal Broker plugin listens for these incoming requests through the port that was specified during the installation of the plugin.
For more information about the system architecture and traffic flow of Universal Broker, see System Architecture and Components of Universal Broker.
|Source||Source Port||Target||Target Port||Protocol||Purpose|
|Universal Broker client on the Horizon Cloud Connector||Randomly selected from available ports||Universal Broker service||443||HTTPS initially, then WebSocket for ongoing connection||Used to establish a persistent WebSocket connection with the Universal Broker service|
|Universal Broker client on the Horizon Cloud Connector||Randomly selected from available ports||Universal Broker plugin on the Connection Server||As specified during installation of the Universal Broker plugin. If no port is specified, port 33443 is used by default.||HTTPS||Used by Universal Broker plugin to listen for incoming connection requests forwarded by the Universal Broker client from the Universal Broker service|