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
Whenever an access token refresh request/operation fails, it counts in the RefreshWindow. Using a RefreshWindow will eventually cause excessiveRefresh errors to be thrown. If the errors refreshing the access token are related to network problems (as it will come to pass on a mobile platform), the RefreshWindow can fill up rather quickly. I like the idea of excessiveRefresh errors, but only when it's related to actual errors concerning authentication - not timeouts and reachability.
Feature Request
It could be nice to be able to configure what types of errors count in the refresh window. A suitable default would obviously be all errors, so that not-configured RefreshWindows continue to operate as they do already.
The text was updated successfully, but these errors were encountered:
I’ve begun resolving this issue and have developed a feature that allows users to configure which types of errors count towards the refresh window. The default behavior remains unchanged, counting all errors, while users can now provide a closure to specify their error handling logic.
I'm in the process of writing tests and updating the documentation to reflect this new feature. I plan to submit a draft PR soon to get feedback on the implementation.
Could this issue be assigned to me to avoid duplicate work?
Problem
Whenever an access token refresh request/operation fails, it counts in the RefreshWindow. Using a RefreshWindow will eventually cause excessiveRefresh errors to be thrown. If the errors refreshing the access token are related to network problems (as it will come to pass on a mobile platform), the RefreshWindow can fill up rather quickly. I like the idea of excessiveRefresh errors, but only when it's related to actual errors concerning authentication - not timeouts and reachability.
Feature Request
It could be nice to be able to configure what types of errors count in the refresh window. A suitable default would obviously be all errors, so that not-configured RefreshWindows continue to operate as they do already.
The text was updated successfully, but these errors were encountered: