PaulAndLobo
PaulAndLobo
I am also seeing this. It does not happen from the Microsoft sample, but it happened when I attempted to integrate the same code into an AddIn I've been working...
I've gotten nowhere with the AddIn, but have gotten a proof-of-concept SPA working with the MSAL javascript library, talking to our backend REST API (.NET Core on Azure with controllers...
It is trying to load the /auth page from the local Express Server. If you add routing for that, it should work. In my case, I'm able to skip this...
Here is the relevant part of the method (hacked up from the Microsoft sample). Note that it returns the so-called bootstrap token: export async function getGraphData(): Promise { console.log("getGraphData()"); try...
So the above is the abbreviated version that doesn't call MSGraph, for example, to get user info such as email. Rather, I pick apart the token over on the server...
And hah! I just realized the function name "getGraphData" is now a misnomer since it doesn't call MsGraph :^)