microsoftgraph / mgtLap-TryItOut

MIT License
19 stars 14 forks source link

AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application #8

Open westerdaled opened 4 years ago

westerdaled commented 4 years ago

I got inspired by @hugoabernier 's Integrate Graph in your solutions using Microsoft Graph Toolkit but then quickly realised I haven't got his supper PnP Powers 🤨

I followed a lap around the graph toolkit day 2 registered my app and updated the index.html with my client id

Attempted to login using my MFA Work account

Login error the reply specified does not match

Had a look on google and the general advice seems to see what redirects fiddler reports.

Fidler errors

So changing the redirect URL from https://localhost:3000/

to

http://localhost:3000/02%20-%20Zero%20to%20Hero/index.html

Will get me passed the error though took a bit of refreshing to actually see the welcome screen and not the directory of the root. Am I the only one experiencing these issues?

hugoabernier commented 4 years ago

@westerdaled I had the same issue when I first started. You probably opened the Visual Studio Code workspace from the root of the repository, which adds the 02%20-... stuff to your URL.

Can you try opening your Visual Studio Code workspace from the 02 folder? (I usually right-click on the folder and select Open with Code.

That may be all you need to do.

Let us know if that works for you?

simonagren commented 4 years ago

Not sure off the specifics here. And maybe look at what Hugo said. Regarding the redirect URL I would just remove the trailing "/" https://localhost:3000 that should work as far as my experiences go 🙂

westerdaled commented 4 years ago

@hugoabernier , @simonagren

Looks like both of your suggestions are valid. I think the issue is, out of habit I was pasting the the url : http://localhost:3000/02%20-%20Zero%20to%20Hero/index.html . rather than simply: right-click on the folder and select Open with Code. I wanted to test against a dev tenant running in an edge chromium profile ( not my default browser ). Now I can't get it to break - it even caches my access token after a reboot.