Logging configuration not working

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

• msal@1.x.x or @azure/msal@1.x.x
• @azure/msal-browser@2.2.0
• @azure/msal-angular@0.x.x
• @azure/msal-angular@1.x.x
• @azure/msal-angularjs@1.x.x

Description

Logging is not triggered with configuration.

Error Message

Logging is not triggered with configuration object PublicClientApplication

Security

• Is this issue security related? no

Regression

• Did this behavior work before? yes (msal version, it just worked) Version:

MSAL Configuration

const AZURE_CONFIG: Configuration = {
  auth: {
    authority,
    clientId: AZURE_ID,
  },
  cache: {
    cacheLocation: 'localStorage',
  },
  system: {
    loggerOptions: {
      loggerCallback: () => {
        console.log('triggered');
      },
      piiLoggingEnabled: false,
      logLevel: LogLevel.Verbose,
    },
  },
};

const azureProvider = new PublicClientApplication(AZURE_CONFIG);

Expected behavior

Log all stuff happening in Verbose mode. In the case of the configuration above, it should log ‘triggered’.

Browsers/Environment

• Chrome
• Firefox
• Edge
• Safari
• IE
• Other (Please add browser name here)

[tnorling]

@vinceve Looks like you’re calling acquireTokenByRefreshToken. This function always makes a network call and is intended to only be used internally by msal. You should not call this directly as it is subject to change or be removed at any time. You should use acquireTokenSilent instead which will first do a cache lookup, then attempt to refresh if the token is expired or can’t be found in cache.

[github-actions[bot]]

This issue has been closed due to inactivity. If this has not been resolved please open a new issue. Thanks!