Certificate-Weakening TlsOptions have no effect on web socket connections

[wexman]

I noticed that the "certificate weakening" TlsOptions like IgnoreCertificateChainErrors, IgnoreCertificateRevocationErrors, AllowUntrustedCertificates and CertificateValidationCallback have no effect when using web socket connections.

I understand this is because the underlying api (System.Net.WebSockets) does not support this (at least not in all target frameworks), but I think it should be noted somewhere - that would have saved me several hours of trial and error...

[JanEggers]

the issue here is that for websockets we delegate the handling to kestrel. I didnt investigate how to flow the mqttnet tls options into kestrel so maybe there is a way to get that done.

I just googled a bit and found:

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-3.1#listenoptionsusehttps