Wcf: NetHttpBinding with WebSockets doesn't allow custom Certificate handling
This involves:
- Calling any custom X509CertificateValidator.Validate class that a user has set on their credentials for verifying the server cert.
- Using the ClientCertificate that a user has provided on the credentials to authenticate against the server.
- Most likely adding functionality to the System.Net.WebSockets.Client.ClientWebSocket class to enable certificate handling.
mconnew
All 4 comments
The System.Net.WebSockets.Client and System.Net.WebSockets contracts do not facilitate any certificate handling. This will be addressed post RTM by the team which owns those contracts, until then we are blocked.
mconnew
on 3 Dec 2015
Thanks @mconnew. Can we add related System.Net.WebSockets.* issues here?
zhenlan
on 3 Dec 2015
There is no customer vote on this. Moving it to future. To implement, we will build on top of SocketHttpHandler.
Lxiamail
on 10 Apr 2019
I hope it is ok to ask a question here: Is it correct that it is currently not possible to use a self-signed certificated for a WebSockets connection based on a WCF client in a .Net Core 3.1 Application?
I need to migrate an existing .Net 4.6 WPF Application to .Net Core 3.1 (and later to .Net 5) and this problem might prevent me from doing so. Is there any chance this will be fixed in the not too distant future?
stefanegli
on 10 Sep 2020
Related issues
weitzhandler
路
6Comments
martinspasovski
路
3Comments
IGx89
路
6Comments
kevinoid
路
6Comments
mconnew
路
5Comments
Most helpful comment
I hope it is ok to ask a question here: Is it correct that it is currently not possible to use a self-signed certificated for a WebSockets connection based on a WCF client in a .Net Core 3.1 Application?
I need to migrate an existing .Net 4.6 WPF Application to .Net Core 3.1 (and later to .Net 5) and this problem might prevent me from doing so. Is there any chance this will be fixed in the not too distant future?