WebSocket does not connect to a broker with an invalid SSL certificate

[kubeliv]

This is currently a problem that cannot be addressed until we find a suitable workaround. .NET Standard 2.0 does not have the new callback for certificate validation which allows us to bypass all certificate validation for a WebSocket. .NET Standard 2.1 is the first version that adds this new API, but 2.1 removes .NET Framework compatibility entirely.

More details about this issue are available here:
https://github.com/dotnet/corefx/issues/12038
dotnet/corefx#28141

Possible solutions include:

• Rolling our own WebSocket implementation
• Using the .NET Standard fork of WebSocketSharp (not sure as of yet if this shims the native ClientWebSocket or ideally a port of the standard WebSocketSharp)
• Drop .NET Framework support and jump to .NET Standard 2.0