ClientAuthError: access_token_entity_null: Access token entity is null, please check logs and cache to ensure a valid access

Core Library

@azure/msal-browser

Core Library Version

2.14.1

Wrapper Library

Not Applicable

Wrapper Library Version

0

Description

on handleRedirectPromise() after login

ClientAuthError: access_token_entity_null: Access token entity is null, please check logs and cache to ensure a valid access token is present.

Error Message

No response

Msal Logs

No response

MSAL Configuration

this.app = new Msal.PublicClientApplication({
                auth: {
                    clientId: `${BaseConfig.AppClientID}`,
                    authority: `${BaseConfig.AppLoginAuthority}`,
                    knownAuthorities: [`${BaseConfig.AppLoginAuthority}`],
                    validateAuthority: false,
                    navigateToLoginRequestUrl: true,
                    redirectUri: `${BaseConfig.AppUrl}login`,
                    postLogoutRedirectUri: `${BaseConfig.AppUrl}login`,
                },
                cache: {
                    cacheLocation: "sessionStorage",
                    storeAuthStateInCookie: true,
                    secureCookies: true
                }
            });

Relevant Code Snippets

this.app.handleRedirectPromise().then(response => {
                console.log("response", response);
                if (response) {
                    this.handleResponse(response);
                }
            }).catch(error => {
                console.log(error);
            });

Reproduction Steps

1. immediately after login

Expected Behavior

should return object with correct data.

Identity Provider

Azure B2C Basic Policy

Browsers Affected (Select all that apply)

Edge

Regression

2.13.1

Source

External (Customer)

[kberawala]

Below is the workaround, worked for me.

signin() {
  var request = {
      redirectStartPage: `${BaseConfig.AppUrl}login`,
      scopes: ["openid", "profile", `${YourAppClientID}`] // this line wasn't there before, this for AD B2C
  }
  this.app.loginRedirect(request);
}

[brriann]

I saw this issue as well. Solution was to update @azure/msal-browser 2.11.2 to 2.14.0 as @DmytroKuznyetsov mentioned. Ideally we would update to latest, but maybe best to hold off is this bug is present in 2.14.1 as well.