I had noticed a getTokenSilently fail on page refreshes when on most non-chromium browsers (i.e. firefox), which I investigated and partially rectified by enabling refresh tokens and their corresponding fallback. Now, page refreshes don’t require the user to re-authenticate, but as part of my application’s functionality I require the issuing of a new token to the user, which I had called through getTokenSilently(cacheMode='off')
. This works as desired on chromium-based browsers, but on firefox has the same failure that requires re-authentication on triggering this action (redirecting the user to the log-in page). What are my options here? My configuration is as follows:
useRefreshTokens='true'
useRefreshTokensFallback='true'
cacheLocation='localstorage'
authorizationParams={{
redirect_uri: window.location.origin
audience: <myaudience>
scope: "openid profile email offline_access"
}}