You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used oauth go package, and it seemed to automatically refresh token if request failed on 401 unauthorized.
But it's not working, maybe oauth package needs more information to be able to refresh automatically.
If it doesn't work, I could refresh 42 API token manually, and if it still doesn't work, I'll remove 42 API token refresh and only 42 Tutor API token.
The text was updated successfully, but these errors were encountered:
gmarcha
changed the title
Refresh 42 API Token seems to failed under certains circumstances
[Bug] Refresh 42 API Token seems to failed under certains circumstances
May 17, 2022
Currently, there is a refresh inception, myAPI pings authAPI (with accessToken stored internally):
if success, accessToken from authAPI is not expired, and everything works as expected, myAPI refresh accessToken from myAPI;
if fail, accessToken from authAPI is expired, and myAPI fail to refresh that token with authAPI.
A workaround could be to avoid refreshing myAPI token with authAPI token.
It is not really useful at this step (login already enforces user information retrieving).
42 API token seems to fail to refresh.
I used oauth go package, and it seemed to automatically refresh token if request failed on 401 unauthorized.
But it's not working, maybe oauth package needs more information to be able to refresh automatically.
If it doesn't work, I could refresh 42 API token manually, and if it still doesn't work, I'll remove 42 API token refresh and only 42 Tutor API token.
The text was updated successfully, but these errors were encountered: