title: How does 2-legged oauth work in OAuth 2.0?
body: <p>In OAuth 1.0, 2-legged is pretty easily: Simply send the request as usual and omit the <code>access_token</code> header.</p>
  
  <p>Things seems to have changed in OAuth 2.0 (drastically, as I found out today :)). In OAuth 2.0, the request no longer has headers such as the nonce, consumer key, timestamp etc. This is just replaced by:</p>
  
  <pre><code>Authorization: OAuth ya29.4fgasdfafasdfdsaf3waffghfhfgh
  </code></pre>
  
  <p>I understand how 3 legged authorizations work in OAuth 2.0 and the application flows. But how does 2-legged work in 2.0? Is it possible to design an API that can support both 2-legged and 3-legged OAuth 2.0?</p>
  
  <p>I have been searching for information regarding this, but I have been finding a lot of stuff on 2-legged for 1.0 and almost nothing for 2.0.</p>