Here I have talked about a technique to flow Forms Authentication cookie to a WCF service and using it as an authentication credential for the service. For this to work – service must be running in ASP.net compatibility mode and Forms Authentication must be configured in web.config.
Here is diagrammatic view of a simple case.
In the above diagram, website authenticates users using Forms authentication, which creates a cookie after successful authentication. When ASP.net sites calls the backend service (in response to users action) – it simply passes the Form Auth cookie as part of the call. Now because our service is running in asp.net compatibility mode and Forms Authentication module is also configured in web.config, cookie will successfully be validated and we will see correct identity in the HttpContext.User
Looking good so far. Yes?
I think, this is acceptable when you only have one to two services – however when we talk about SOA – we generally mean larger number of services and this is where this approach becomes clunky primarily due to following two reasons:
· Every service MUST run under asp.net compatibility mode, which is slower than the default native mode. So you incur some performance plenty.
· For the cookie flow to work, both participants MUST use the same <machineKey>. As your share single key among more and more participants – the overall security of solution is getting weaker as key will be duplicated across many places.
So there are some scalability & security issues in the above architecture.
Let’s see how we can improve this architecture by introducing an STS into picture. The goal here is to extract the authentication mechanism (FormsAuth cookie based) out of the services and move it to STS. Service will simply require a token from STS – it is STS’s responsibility to authenticate user using some mechanism (Forms Auth being the step one).
Here you can see ONLY STS is running in asp.net compatibility mode and services are running under native mode which will result in better performance.
Also now we are only sharing keys (<machineKey>) between two participants (STS & Website) regardless of the number of services. Services are simply configured to require a SAML token from the STS and are agnostic to the actual client authentication mechanism. We can easily change cookie based authentication with Kerberos without impacting services at all.
Now Step 1 isn’t really possible out of box – why?
Because it’s the wsFederationHttpBinding, which talks to STS rather your proxy (configured to use wsFederationHttpBinding). So setting cookie on the proxy will NOT send it to STS and the solution is to extend WCF security framework to enable cookie flow to the STS.
In next post, I will show how to implement Step 1 while still leveraging wsFederationHttpBinding. For now please see this post for background.