Earlier this week during my TechDays presentation on Windows Identity Foundation, there was a part during the demo that I said would fail miserably after the user was authenticated and the token was POST’ed back to the relying party. Out of the box, ASP.NET does request validation. If a user has submitted content through request parameters it goes through a validation step, and by default this step is to break on anything funky such as angle brackets. This helps to deter things like cross site scripting attacks. However, we were passing XML so we needed to turn off this validation. There are two approaches to doing this.
The first approach, which is what I did in the demo, was to set the validation mode to “2.0”. All this did was tell ASP.NET to use a less strict validation scheme. To do that you need to add a line to the web.config file:
<httpRuntime requestValidationMode=”2.0” />
This is not the best way to do things though. It creates a new vector for attack, as you’ve just allowed an endpoint to accept trivial data. What is more preferred is to create a custom request validator. You can find a great example in the Fabrikam Shipping demo.
It’s pretty straightforward to create a validator. First you create a class that inherits System.Web.Util.RequestValidator, and then you override the method IsValidRequestString(…). At that point you can do anything you want to validate, but the demo code tries to build a SignInResponseMessage object from the wresult parameter. If it creates the object successfully the request is valid. Otherwise it passes the request to the base implementation of IsValidRequestString(…).
The code to handle this validation is pretty straightforward:
public class WSFederationRequestValidator : RequestValidator
protected override bool IsValidRequestString(HttpContext context,
string value, RequestValidationSource requestValidationSource,
string collectionKey, out int validationFailureIndex)
validationFailureIndex = 0;
if (requestValidationSource == RequestValidationSource.Form
SignInResponseMessage message =
if (message != null)
return base.IsValidRequestString(context, value, requestValidationSource,
collectionKey, out validationFailureIndex);
Once you’ve created your request validator, you need to update the web.config file to tell .NET to use the validator. You can do that by adding the following xml:
<httpRuntime requestValidationType="Microsoft.Samples.DPE.FabrikamShipping.Web.Security.WSFederationRequestValidator" />
You can find the validation code in FabrikamShipping.Web\Security\WSFederationRequestValidator.cs within the FabrikamShipping solution.
Just came across this on the Decrypt my World blog. It seems a lot of Microsoft developers are asked for code samples and for lots of valid reasons they can’t provide them. So Microsoft is fixing that by opening up a service where you can request code samples for any Microsoft technologies.
Here is the official word on what it is:
Developers are encouraged to submit code sample requests dealing with any Microsoft development technologies to our site. At the same time, developers can now vote for newly submitted or existing code sample topics. Here’s the exciting part! Microsoft engineers will then pick the requests with the highest number of votes and provide the code samples. It’s all FREE!
You can find the full write-up here: http://1code.codeplex.com/wikipage?title=NEW%2c%20FREE%20Code%20Sample%20Request%20Service%20from%20Microsoft%20All-In-One%20Code%20Framework