User is logged in, has a valid refresh token but an outdated access token. If he now initiates two HTTP requests at the same time, then the http interceptor will trigger the refreshment twice. Probably adding a BehaviorSubject to the Interceptor and delaying the execution will resolve this issue.
Fixed when:
[ ] two simulations requested http calls will only result in one refreshment
[ ] the second http request will be delayed until the refreshment is done.
Given the following situation:
User is logged in, has a valid refresh token but an outdated access token. If he now initiates two HTTP requests at the same time, then the http interceptor will trigger the refreshment twice. Probably adding a BehaviorSubject to the Interceptor and delaying the execution will resolve this issue.
Fixed when: