ClientAuthError: Token renewal operation failed due to timeout. provided undefined token

[PraveenVerma17]

Describe the bug
MSAL Provider get access token failed but still went through the promise then instead of going to catch and provided undefined token

ClientAuthError: Token renewal operation failed due to timeout.
at t [as constructor] (https://xxxxxx/static/js/2.92d0259e.chunk.js?__WB_REVISION__=1364c7e14e5f9cb92371:1:810438)
at new t (https://xxxxxx/static/js/2.92d0259e.chunk.js?__WB_REVISION__=1364c7e14e5f9cb92371:1:812678)
at Function.createTokenRenewalTimeoutError

Expected behavior
we should receive error message instead of undefined token

[PraveenVerma17]

Is there anyone who is looking into this issue ? Even though i am logging out user after this error and login again then also we are keep getting undefined token. if i open chrome in incognito mode then i am able to access website and getting new token.

This is really bad. We need know how to properly logout so browser should not fail to get token.

[nmetulev]

@PraveenVerma17, could you provide repro steps or repro project for us to replicate the issue - the more details you can provide the faster we can try to assist.

[PraveenVerma17]

we can't share the project details as its private. I can give very small code snippet

authProvider.getAccessToken().then(token => {
  //Check if token is null, undefined, and empty
 if (token === null || token === undefined || token === "" || token === "undefined") {
    _logException(`Invalid token provided by msal ${token}`);
     this.logout();
 }

we are getting token as undefined.

in console we have seen this error.

ClientAuthError: Token renewal operation failed due to timeout.
at t [as constructor] (https://xxxxxx/static/js/2.92d0259e.chunk.js?__WB_REVISION__=1364c7e14e5f9cb92371:1:810438)
at new t (https://xxxxxx/static/js/2.92d0259e.chunk.js?__WB_REVISION__=1364c7e14e5f9cb92371:1:812678)
at Function.createTokenRenewalTimeoutError

if you need my config details i can send you that.

getMsalProviderConfig(response)
    {
        let config = {
            auth: {
                clientId: null,
                //authority: response.data.authority,
                redirectUri: window.location.origin,
                postLogoutRedirectUri: window.location.origin
            },
            cache: {
                cacheLocation: "sessionStorage",
                storeAuthStateInCookie: true
            }
        }

          return  {
                clientId: response.data.clientid,
                authority: response.data.authority,
                scopes: [response.data.scopes],
                loginType: LoginType.Redirect,
                options: config
            }
  
    }

[nmetulev]

Thanks. On the msal issue, I'm unable to repro it unfortunatly, but it sounds like there is already an issue open with the msal project (AzureAD/microsoft-authentication-library-for-js#699)

On the getAccessToken returning undefined tokens, would you prefer the function instead rejects the promise when we can't get a token? I agree that sounds like the right approach, but I want to confirm that is you request here

Created #114 to update this behavior

[PraveenVerma17]

@nmetulev Thanks for PR. That's the right way of doing it.
But i need solution also i want to know why am i getting undefined token. we have noticed few things.

We have seen this when gmail users who have multi-factor auth enabled in both gmail or tenant side we get undefined token and
also redirecturi sometimes in edge become base/null or base/# instead of base.

Few users gmail account works perfectly fine.
I am not able to identify actual root cause or pattern for this error.