In environments where a self-signed certificate is used for the hub (either behind a load balancer or a reverse proxy like nginx), the agents are unable to connect due to the default behavior of socket.io where it would reject connections to endpoints with self-signed certificate.
With this PR, agents can be configured to connect to a hub that is using a self-signed certificate.
Details
In environments where a self-signed certificate is used for the hub (either behind a load balancer or a reverse proxy like nginx), the agents are unable to connect due to the default behavior of socket.io where it would reject connections to endpoints with self-signed certificate.
With this PR, agents can be configured to connect to a hub that is using a self-signed certificate.
Does this PR introduce a breaking change?