title: Non-claims-enabled ASP.NET applications and ADFS v2.0
body: <p>This <a href="http://www.theidentityguy.com/articles/2010/10/15/access-owa-with-adfs.html" rel="nofollow">article</a> got me thinking about what would happen with non-claims enabled ASP.NET applications when you federated them with ADFS via FedUtil.</p>
  
  <p>The article suggests that the key to getting this working is to turn on the Claims to Windows Token Service (C2WTS). This service effectively turns an ADFS token into a Windows token.</p>
  
  <p>So I built a quick ASP.NET application using Windows authentication, ran FedUtil and I can authenticate with ADFS using either the ADFS Windows authentication or StarterSTS. The problem is that C2WTS isn't running so it works although I expected that it wouldn't.</p>
  
  <p>Obviously you have no access to the claims objects inside the application but otherwise it works with no problems. </p>
  
  <p>This does, however, raise a problem. How do you sign out from ADFS since you have no access to FederatedPassiveSignOut etc?</p>
  
  <p>Are tokens being sent to the application? </p>
  
  <p>Is it just ignoring them without throwing any exceptions?</p>
  
  <p>Does C2WTS need to be part of the picture?</p>
  
  <p>Have I missed something? </p>