title: Web API Token authentication vs Custom token authentication
body: <p>Very much new to Web API's. Trying to implement the <code>token</code> method the <code>Web API</code> uses to authenticate a user against database and use the <code>token</code> for all successive API calls. But i am finding it very difficult to follow the steps to do the same for <code>mysql DB</code> . I also feel it is a complex process for a simple login. </p>
  
  <p>So my question is instead of using the <code>Web API token</code> method. Why not have a traditional Login function(<code>web api</code>) which checks the <code>userid/pwd</code> against <code>db userid/pwd</code> ? Which generates a token similar to <code>AuthenticationTicket</code> in <code>ApplicationOAuthProvider</code>, and send it as <code>response</code> to an ajax call and store in javascript <code>sessionStorage</code> for successive calls.</p>
  
  <p>What is the difference in terms of security/general in both cases?</p>