Reputation: 20717
For a customer, I've to use WCF to communicate between a client and a server application.
My application was using a WSHttpBinding to communicate, but now, the customer doesn't to install any SSL certificate, because:
So I started to look how to don't use any SSL certificate, but I got some problems:
I saw that I should use a "TransportCredentialOnly" settings for the security mode, but this settings isn't available for "WsHttpBinding". So I decided to use the basicHttpBinding, which has this option, but it seems that the basicHttpBinding doesn't offer the possibility to use CustomUserNamePasswordValidator.
So how can I do this? Every search result I found are either using a SSL certificate or don't have customUserNameValidator.
Thank you very much for any help.
Upvotes: 2
Views: 1161
Reputation: 364269
This is very rare scenario where sending unsecured username and password make sense. You need custom binding for this because default bindings don't allow this. This answer contains two options you can use. Just be aware that first option will allow you to send plain text user name and password over unsecured transport but it will break WSDL generation (that is a bug in WCF).
Upvotes: 2