clientCredentialsUserName | WCF Endpoing behavior for Username/password authentication

clientCredentialsUserName is a C# library. clientCredentialsUserName has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

WCF Endpoing behavior for Username/password authentication. Out of the box, WCF provides a variety of endpoint behavior extensions. Amomg them is (behavior that enables the client to declare its credentials which will be used when performing authentication against the service. It's important to note that such should be supplied in coordination with actual binding's security mode used. Because of securty resons, does not includes the option to specify username/password neither for wsHttpBings nor for basicHttpBinding (used primarily for development purpose, when username/password are passed over insecured http, not https). However, for some scenarios it is very important to have some kind of such functionality. For example, WCF Router may be configured to receive the messsages over, say, basicHttpBinding and route the to the endpoint in which userName security is used. In this case, we can not expect the client to pass the username simply because it calls the WCF Router intermediary with Windows credentials, but the destination service do expect the username authentication that must to use the values for this authentocation from somewhere. Logically, this "somewhere" may be an SSO system that matches Windows credentials passed to WCF Router to value pairs from affiliated app, but for simplier case these pair in non-production cases may be stored in WCF configuration file. Such configuration, then, should looks like: .