TypeScript - @azure/msal-node - accessToken type on AuthenticationResults

Library

• @azure/msal-node@1.x.x

Description

I am using the latest version of the @azure/msal-node module. I have a small typescript lambda that is creating an accessToken using the OAuth 2.0 Client Credentials Grant flow.

High level, I import the module:

import * as msal from '@azure/msal-node';

Setup my config:

  const config = {
    auth: {
      clientId: client_id,
      authority,
      clientSecret: client_secret,
    },
    system: {
      loggerOptions: {
        loggerCallback(loglevel: any, message: any, containsPii: any) {
          core.info(`${loglevel}:${message}:${containsPii} `);
        },
        piiLoggingEnabled: false,
        logLevel: msal.LogLevel.Verbose,
      },
    },
  };

Create the App & set scopes:

  const cca = new msal.ConfidentialClientApplication(config);

  const clientCredentialRequest = {
    scopes: ['api://xxxx/.default'],
  };

I then attempt to deconstruct the accessToken from the request by doing:

  try {
    const { accessToken } = await cca.acquireTokenByClientCredential(clientCredentialRequest);
    return accessToken;
  } catch (error) {
   log(error)
  }
}

However, I am getting the error:

Property 'accessToken' does not exist on type 'AuthenticationResult | null'.

On this line:

 const { accessToken } = await cca.acquireTokenByClientCredential(clientCredentialRequest);

I have tried finding the @azure/msal-node types library but I can’t find one.

I have got this working in Vanilla JS, but must admit I am new to TypeScript a little, so this is likely not a bug but on me, where about am I going wrong here, if you don’t mind me asking?

Source

• Internal (Microsoft)
• Customer request

[sameerag]

@NickLiffen Closing this issue. We will follow up on strict null checks enhancement, I just do not have a clear timeline at this point. Marked it internally.

[sameerag]

We added strict null checks in our code and hence had to support | null in cases where it applied. I do think that some of the changes can be refined and possibly remove this for certain return types, but this would need changes in a lot of code. We will take it up eventually and I will mark this as an enhancement in our backlog.

Hopefully we will get to it sooner than later 😃