title: OAuth 2.0 for REST Web services
body: <p>i'm implementing a REST layer for an existing application. I have my userid and passwords stored in database and i would like to authenticate these credentials while calling my REST services. Note that this is a standalone application.</p>
  
  <p>After investigation, I figured out 2 ways.</p>
  
  <ul>
  <li>Basic implementation with HTTPS - this approach makes sure that
  userid and password passed is not tampered by Man in middle attack.</li>
  <li>Using Authentication Token(JWT) -  user initially passes his userid
  and password and server gives back an Authentication token.Once user
  have an authentication token that could be used for subsequent
  request.</li>
  <li>Using OAuth 2.0 - I'm very confused in this approach. After reading the docs and specification, I found that since my application
  is standalone, I need to implement Authorization Server, Resource
  Server etc.</li>
  </ul>
  
  <p>I'm asked to implement OAuth here, but i'm not convinced that OAuth is required in this scenario. I'm more inclined towards just implementing JWT(tokens)</p>
  
  <p>Is OAuth really mandated in this scenario. What i understand about OAuth is it is used when you already have a service like Facebook/ Google.</p>
  
  <p>Could someone pls confirm if my train of thoughts are correct and if OAuth 2.0 is required in this case?</p>