title: How to persist an OAuth2 token (or use a refresh token) in Postman collections?
body: <p><strong>The goal</strong></p>
  
  <p>Be able to run a collection without going through the authorization process of every call individually prior to running the collection.</p>
  
  <p><strong>What I've attempted/noticed</strong></p>
  
  <ol>
  <li><p>When using the OAuth2 authorization helper in Postman, I haven't discovered a method to save a returned refresh token, and thus use it when the access token expires to get a new one. (I've suggested this feature be placed into the helper in the Postman Github Issues.)</p></li>
  <li><p>I've tried creating a few steps at the beginning of the collection to replicate the helper, but cannot get past the step where user interaction is required to approve/deny (which makes sense as it's a security risk otherwise). However, I can't seem to figure out how to prompt the user either, the way the OAuth2 helper does.</p></li>
  <li><p>I've taken my expectations down a notch in regards to the refresh token and thought I could simply run the authentication on the first test in the list, saving the access token somehow in a global or environment variable, and then using that token in the all subsequent tests, but I have not found a way to save the access token generated via the OAuth2 helper.</p></li>
  </ol>
  
  <p>I would love to know if there is a solution to this which results in collections being able to be run with minimal effort put into authorization.  This becomes more important with the more tests written in a collection which all use OAuth2 authorization.</p>
  
  <p>Side note: I've been using the Postman mac client, in case there is a different in clients I'm unaware of.</p>