Handle refresh token and failed requests retry when access token expires

[ghost]

I am trying to implement an OAuth authentication mechanism with refresh token and access token. I have searched for the solution a lot. But, still I haven't find any comprehensive solution that works for me.
I have different watchers for different actions. The main problem is when the access token expires. I want to have a solution for refreshing the token and more importantly re-try failed request with 401 code. What is the best solution for my case? I don't want to miss any failed request and want to retry them all.

[janhesters]

It would be cool to have an example in the docs for this.

[mattiassamskar]

+1

[janhesters]

@hadiranjbar25 Could you please leave the issue open, even if you solved your problem? I think this is still a neat addition to the docs.

[ghost]

@janhesters I got that we should handle it in axios level, not in redux-saga.

[estebanx64]

@janhesters I got that we should handle it in axios level, not in redux-saga.

i tried with interceptor in axios, but when the API responses 401 and interceptor capture and handle that response, the yield in saga is launched and then entry in the catch exception, before of the interceptor complete the flow and renew token.

do you solved it?

[ghost]

Yes, that's because you are resolving it even if it is unauthorized. While you have not resolved it, saga waits for the response. This is a great tutorial I have used to implement it:
https://www.techynovice.com/setting-up-JWT-token-refresh-mechanism-with-axios/

[le-blip]

How to handle multiple requests after refresh? My interceptor makes the calls but my state is not updated because saga is resolving promise as error due to token expiry. How do i control my saga response for refresh?
Two questions:

1. How to handle multiple requests after refresh correctly?
2. How do i control my saga response if refreshing?