Making multiple calls to acquireTokenSilent, may result in multiple requests to service POST /token, is there a way to use whichever request succeeded?

Library

• msal@1.x.x or @azure/msal@1.x.x
• @azure/msal-browser@2.6.1
• @azure/msal-node@1.x.x
• @azure/msal-react@1.x.x
• @azure/msal-angular@0.x.x
• @azure/msal-angular@1.x.x
• @azure/msal-angular@2.x.x
• @azure/msal-angularjs@1.x.x

Description

Currently in our app, we make a call to acquireTokenSilent before any api request. We can make api requests in parallel which result in parallel calls to acquireTokenSilent. When needed, acquireTokenSilent will make network calls to POST /token to get a new token. Currently this results in multiple calls to POST /token.

In some of our logs, we see that one or two of them will fail with status code 0: Failed to fetch.

1. I’m not sure why status code 0 is happening for some requests, but other requests succeed
2. In the same batch of parallel requests to POST /token, if only 1 fails, does the library return the result of any previously successful request?
3. For example say request A and request B both start at the same time. Request A succeeds first, and then request B fails. Can the acquireTokenSilent method return the result of request A for both calls?

Source

• Internal (Microsoft)
• Customer request

[JWess]

I am very excited to hear this will be implemented. Hopefully soon!

[jo-arroyo]

@thoo1 That’s a reasonable request and we will look into it.