title: Moving from Web API 2 Claim-Based-Authentication to ThinkTecture
body: <p>I am finding that Microsoft's implementation of <em>Claim-Based Authentication</em> is not really up to the expectation of the true Claim-Based setup, and I seems like <em>ThinkTecture</em> is doing a good job of replacing <em>Web API implementation</em>. </p>
  
  <p>I am wondering if anyone has a guide or blog post for people <strong>to move from the default SPA Template for VS2013 for AccountController to the ThinkTecture approach</strong>. </p>
  
  <p>I also like that default Microsoft Web API AccountController that will create the tables  for AspNetUsers and Roles, but I am not sure if ThinkTecture does the same thing or not.</p>
  
  <p>I guess I am a little confused between all of the <a href="https://github.com/thinktecture" rel="nofollow">repositories that ThinkTecture</a> have. Does any one have a solid guidance in terms of what to use, <code>IdentityServer</code>, <code>IdentityModel.45</code>, or <code>AuthorizationServer</code>? </p>
  
  <p>I am just looking to drop the whole Microsoft approach and open to use a proper true Claim-Based approach, but I kinda need help in terms of <code>EF6 migrations</code> for the Identity tables, and what projects to use, or how to drop the the whole AccountController approach in SPA-Template for VS2013. I have looked at <a href="http://leastprivilege.com/" rel="nofollow">Dominick's blog</a> and it seems to be really good, but I haven't found a post that kinda helps <strong>moving from Web API approach to ThinkTecture way of thinking</strong>.</p>