kaangoksal
commented
1 year ago I have the same problem, it works flawlesley on Edge, but broken on chrome, here are my important bits
Sorry, but we’re having trouble signing you in.
AADSTS900144: The request body must contain the following parameter: 'client_id'.
/*! @azure/msal-browser v3.0.0-alpha.2 2023-05-22 */
// Config object to be passed to Msal on creation
const msalConfig = {
auth: {
clientId: "<client id>",
authority: "https://login.microsoftonline.com/<hidden tenant>",
},
cache: {
cacheLocation: "sessionStorage", // This configures where your cache will be stored
storeAuthStateInCookie: false, // Set this to "true" if you are having issues on IE11 or Edge
},
system: {
loggerOptions: {
logLevel: msal.LogLevel.Trace,
loggerCallback: (level, message, containsPii) => {
if (containsPii) {
return;
}
switch (level) {
case msal.LogLevel.Error:
console.error(message);
return;
case msal.LogLevel.Info:
console.info(message);
return;
case msal.LogLevel.Verbose:
console.debug(message);
return;
case msal.LogLevel.Warning:
console.warn(message);
return;
default:
console.log(message);
return;
}
},
},
},
telemetry: {
application: {
appName: "MSAL Browser V2 Default Sample",
appVersion: "1.0.0",
},
},
};
// Add here scopes for id token to be used at MS Identity Platform endpoints.
const loginRequest = {
scopes: ["<hidden scope>"]
};
const logoutRequest = {}const myMSALObj = new msal.PublicClientApplication(msalConfig);
myMSALObj.initialize().then(() => {
// Redirect: once login is successful and redirects with tokens, call Graph API
myMSALObj.handleRedirectPromise().then(handleResponse).catch(err => {
console.error(err);
});
signIn('redirect');
});
async function signIn(method) {
console.log("Will redirect!");
signInType = method;
if (signInType === "popup") {
return myMSALObj.loginPopup({
...loginRequest,
redirectUri: "/redirect"
}).then(handleResponse).catch(function (error) {
console.log(error);
});
} else if (signInType === "redirect") {
return myMSALObj.loginRedirect(loginRequest);
}
}
function handleResponse(resp) {
console.log(resp);
if (resp !== null) {
accountId = resp.account.homeAccountId;
myMSALObj.setActiveAccount(resp.account);
handleTokenAnswer(resp);
} else {
// need to call getAccount here?
const currentAccounts = myMSALObj.getAllAccounts();
if (!currentAccounts || currentAccounts.length < 1) {
return;
} else if (currentAccounts.length > 1) {
// Add choose account code here
} else if (currentAccounts.length === 1) {
const activeAccount = currentAccounts[0];
myMSALObj.setActiveAccount(activeAccount);
accountId = activeAccount.homeAccountId;
console.log("Active account", activeAccount);
myMSALObj.acquireTokenSilent(loginRequest).then(handleTokenAnswer).catch(error => {
console.log(error);
});
}
}
}
Drsela
jo-arroyo
grosch-intl
SirMrJames
tnorling
nelsonmontano
Stewz00
Mr-Vinti
MStrannik
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.0.0-beta.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
3.0.0-beta.0
Public or Confidential Client?
Public
Description
Chrome is unable to get a token. If I open my site with Edge everything works as expected. The app is published to an IIS website.
Error Message
AADSTS900144: The request body must contain the following parameter: 'client_id'.
Msal Logs
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Just going to the website in Chrome will fail.
Expected Behavior
Should get a token and work, as it does in Edge.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome
Regression
No response
Source
External (Customer)