MSAL Conflict with Infopath in Sharepoint 2013 on premise

Library

• `@azure/msal-browser@2.13.0

Framework

None

Description

We have a javascript SPA using MSAL to display users Office 365 mail and calendar inside Sharepoint 2013 On Premise. The app works on dev and test servers, on production it throws auth related error for some users.

Error Message

Uncaught (in promise) TypeError: t.scopes.add is not a function at msal-browser.min.js:32 at Array.forEach (<anonymous>) at new e (msal-browser.min.js:32) at t.addScopes (msal-browser.min.js:32) at r.createAuthCodeUrlQueryString (msal-browser.min.js:32) at r.<anonymous> (msal-browser.min.js:32) at msal-browser.min.js:32 at Object.next (msal-browser.min.js:32) at msal-browser.min.js:32 at i.e._execute (bluebird.min.js:29) at i._resolveFromExecutor (bluebird.min.js:30) at new i (bluebird.min.js:30) at d (msal-browser.min.js:32) at r.getAuthCodeUrl (msal-browser.min.js:32) at a.<anonymous> (msal-browser.min.js:32) at msal-browser.min.js:17

MSAL Configuration

Reproduction steps

Expected behavior

User is authenticated and call to graph mail and calendar returns user’s mail and calendar data to display in app.

Identity Provider

• Azure AD

Browsers/Environment

• Chrome
• Firefox
• Edge

Regression

• Did this behavior work before? It works on our own DEV and TEST servers.

Security

N/A

Source

Internal

[jasonnutter]

@bbarnwell Yep, pages that are loaded inside iframes cannot auth via redirects. Apps running in iframes can only silent and popup based requests.

[github-actions[bot]]

This issue has not seen activity in 14 days. If your issue has not been resolved please leave a comment to keep this open. It will be closed in 7 days if it remains stale.