2.Sends request to refresh token 3.send request #1 to fetch

I‘d say using an access_token in combination with a refresh_token is quite normal for secure api development. Considering of course both is implemented correctly. That one request really should not hurt. Theoretically the app could even know (time) that the token is no longer valid before sending the request, that should prevent most requests. And then if there still are a couple requests and the BE returns a 401 it would also not hurt... But let‘s ask from the other side first. How would you do it?

Похожие чаты

2.Sends request to refresh token 3.send request #1 to fetch

3 ответов

Похожие вопросы