BrowserAuthError: user_cancelled: User cancelled the flow.

[arslan-ideawake]

Core Library

MSAL.js v2 (@azure/msal-browser)

Core Library Version

2.18.0

Wrapper Library

MSAL Angular (@azure/msal-angular)

Wrapper Library Version

None

Public or Confidential Client?

Public

Description

Currently, I'm working on an angular v8 project which is using @azure/msal-browser, previously it was working fine locally, in testing and production environments as well, but now when loginPopup of msal function call, it still opens an authentication window in a new tab, but automatically trigger user cancel event, even if user does not close auth tab, but on localhost still working fine.

MSAL Configuration

{
    auth: {
      clientId: environment.azure.clientId,
      authority: 'https://login.microsoftonline.com/common',
      redirectUri: environment.azure.redirectURI
    },
    cache: {
      cacheLocation: 'sessionStorage',
      storeAuthStateInCookie: false
    }
}

Relevant Code Snippets

MSAL_CONFIG: Configuration = {
    auth: {
      clientId: environment.azure.clientId,
      authority: 'https://login.microsoftonline.com/common',
      redirectUri: environment.azure.redirectURI
    },
    cache: {
      cacheLocation: 'sessionStorage',
      storeAuthStateInCookie: false
    }
  };

  private myMSALObj: PublicClientApplication = new PublicClientApplication(
    this.MSAL_CONFIG
  );
  private loginRequest?: PopupRequest;
  
  azureLogin() {
    this.loginRequest = {
      scopes: [
        'user.read',
        'profile',
        'email',
        'openid',
      ],
    };
    return this.myMSALObj.loginPopup(this.loginRequest);
  }

Identity Provider

None

Source

External (Customer)

[jo-arroyo]

@arslan-ideawake Can you provide verbose logs of this behavior? See here for how to enable verbose logs.

[arslan-ideawake]

@jo-arroyo Thanks for your response, this is how verbose logs look like when I turned them on.
(point to note here is that I did not cancel the flow).

[jo-arroyo]

@arslan-ideawake Can you try upgrading to the latest version of msal-browser and see if you still see the error? We have made changes to popups since v2.18.0.