title: OAuth: Storing Access Token and Secret
body: <p>We have a number of clients that use our API to power their websites. </p>
  
  <p>I have started a conversation at work about using OAuth to make authenticated API Calls.
  We will have both, two and three legged flows.</p>
  
  <p>For the 3-legged flow, we still have not come to a consensus on how to store the access token and secret. </p>
  
  <p>The common approach to this problem would be to have the clients store the access token and secret in their own DB, but that is out of the question as the clients don't want to deal with code changes and implementation issues.</p>
  
  <p>The other options we are considering: </p>
  
  <p>1) Saving the access token and secret in a cookie</p>
  
  <p>2) Saving them in the session.</p>
  
  <p>I'm not sure whether either of these is a good idea. Does anyone have any suggestions?</p>
  
  <p>Thank you.</p>