Microsoft-authentication-library-for-js: Renewal of IdToken

[WardGubbi]

I'm using Msal for Azure B2C authentication & API authorization. When using acquireTokenSilent for the Id Token (scope being the application id). It always resolves unless the id_token has expired. A renewal never resolves and leaves an error in the console that cannot be caught (doesn't even have a stacktrace).

Uncaught (in promise) Please call ResolveEndpointsAsync first

I can see the HTTP request to openid-configuration being resolved in my network logs, so I don't really get why ResolveEndpointsAsync is causing issues. The acquire process is started, since I can see msal_acquireTokenUser entries pile up in the sessionStorage & I also see the msalIdTokenFrame being an empty Iframe (since it has no url assigned to it)
AccessTokens to for my API scopes are being renewed properly.

Am I doing something wrong, or is this a bug in the library? If the latter, any ETA on a new release resolving this? Or if available a quick workaround that I can implement?

[trbngr]

I'm also stuck on this.

[trbngr]

authContext.acquireTokenSilent(ad.scopes, null, authContext.getUser())

@WardGubbi passing authority as null to the acquireTokenSilent constructor will force it to reuse the AuthorityInstance to contains the tenant information. Otherwise a new instance is created without the endpoints.

Hope that made sense. 😜

Short story, pass authority as null.

[WardGubbi]

Makes total sense! Thanks @trbngr

[rohitnarula7176]

Closing this issue as it is resolved by the application above.

[AndrewCraswell]

For those coming across this issue from Google, the current way to renewing an IdToken is slightly different as far as I can tell. According to the comments in the code base, the standard is to call the acquireTokenSilent and pass the clientId of the app as the only scope:

const clientId = 'xxxxxxxxxxxxxxxxxxxxx';
const authParameters = { scopes: [clientId] }
const response = await authContext.acquireTokenSilent(authParameters);