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
Not sure if this is a bug or some configuration I'm missing, but is there a way to stop the withAuthenticationRequired hoc from retrying (seemingly endlessly) to call the authorization server when there's a network error (or if the server isn't responding)?
I have requestTimeoutInSeconds setting set to 3, and if I'm e.g. on the login page (which calls auth.signinRedirect), the useAuth hook is able to reach the oidc client, which respects the timeout and returns with an error "Failed to fetch".
But if I'm on a route that's protected with the withAuthenticationRequired hoc, it goes into some redirecting loop, and tries to reach the authorization endpoint repeatedly.
The text was updated successfully, but these errors were encountered:
Not sure if this is a bug or some configuration I'm missing, but is there a way to stop the
withAuthenticationRequired
hoc from retrying (seemingly endlessly) to call the authorization server when there's a network error (or if the server isn't responding)?I have
requestTimeoutInSeconds
setting set to 3, and if I'm e.g. on the login page (which callsauth.signinRedirect
), theuseAuth
hook is able to reach the oidc client, which respects the timeout and returns with an error "Failed to fetch".But if I'm on a route that's protected with the
withAuthenticationRequired
hoc, it goes into some redirecting loop, and tries to reach the authorization endpoint repeatedly.The text was updated successfully, but these errors were encountered: