Skip to main content

Username authentication in WCF

Imagine following requirements:

  • You want to send data to a WCF service in a secure way
  • To maximize compatibility you have to use basic HttpBinding
  • You want to authenticate using a username/password combination

In WCF the only option you have based on these requirements is the use of SSL.

On server side you have to configure your service using the TransportWithMessageCredential security mode. Configure your binding as specified below:

   1:  <bindings>
   2:        <basicHttpBinding>
   3:          <binding name=”SecureHttps>
   4:            <security mode=”TransportWithMessageCredential>
   5:              <message clientCredentialType=”UserName/>
   6:            </security>
   7:          </binding>
   8:        </basicHttpBinding>
   9:  </bindings>


Verification of the client credentials can be done using for example the ASP.NET membership provider or you can specify your own custom authenticator.

   1:  <serviceCredentials>
   2:              <userNameAuthentication userNamePasswordValidationMode=”Custom
   3:                customUserNamePasswordValidatorType="Services.CustomUserNamePasswordValidator, Services/>
   4:  </serviceCredentials>

Create then the following class:

   1:   
   2:  public class CustomUsernamePasswordValidator : UserNamePasswordValidator 
   3:  {
   4:          public override void Validate(string userName, string password)
   5:          {
   6:              //your validation here
   7:          }
   8:  }



And if you are using the generated proxy on the client side, the only remaining thing you have to do is specifying some client credentials:

   1:  using(var serviceProxy=new SecureService())
   2:  {
   3:        serviceProxy.ClientCredentials.UserName.UserName="Test";
   4:        serviceProxy.ClientCredentials.UserName.Password="Test";
   5:       //Call service operation
   6:  }

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...