title: Angular Refresh Token Authorization Issue
body: <p>I have an Angular client.I created a Bearer Token Authorization system using Asp.Net WebApi. It uses access tokens with a short-lived specified time and refresh tokens with a long-lived specified time. I have a problem when an access token expires and a request is made to a page with multiple $http requests. I have a service set up for retrieving data where, if the first response comes back 401 it goes and gets a new token from the refresh token server and then makes a second request for the data. What is happening is two secured requests are firing almost simultaneously, they both fail 401, they both got to get a new token and the first token retrieval is invalidated by the second. </p>
  
  <p>Two fixes jumped out at me. 1.) Chain the calls to my data service. 2)Arrange my request in a way where the page makes one request for all the data. I am not going to go into detail why these two approaches are unacceptable, I am sure you know why. </p>
  
  <p>I thought about "locking" requests to the token server while other requests are in progress to it or setting up a queue service for token request, I am obviously trying to avoid bottlenecks while also maintaining the integrity of my promise chain.</p>
  
  <p>I am sure other's have experienced this, just wondering what approached others have taken.</p>
  
  <p>Thanks in advance!</p>