This post is a part of the series about how to enable and use OpenID/OAuth support that was added to the ASP.NET templates in Visual Studio 2012. In this post I am going to detail the instructions on configuring your application to use Microsoft account for authentication. I am going to be focusing on configuring the application for a development environment(using VS & IISExpress)
<site name="WebApplication5" id="6">
<application path="/" applicationPool="Clr4IntegratedAppPool">
<virtualDirectory path="/" physicalPath="pathtoapplication\WebApplication5" />
<binding protocol="http" bindingInformation="*:46178:localhost" />
Hope you have fun while integrating Microsoft Account into your applications
It is really unfortunate that Microsoft makes it so annoying for developer to test this. Why does it require a domain other than localhost, and why does it has to be port 80? Why not simply add like a debug-switch where we can freely chose what domain and what port.
Making port 80 accessible on my developer machine is a no go. This is horror for projects using IIS Express, and I have to add an "setup introduction" for every other developer using this project - instead of just "Load solution and start project".
I am getting 400 - Bad Request error with FaceBook as well as Microsoft logins at oAuth.VerifyAuthentication(redirecturl).
Can you please help out of this?
Microsoft seem to have moved the page where we set up an application - clientID and secret - I did this some time ago,but now the url above is a 404
It is still not working for me on my local machine. I used Foo123localtest.me. Not sure what mistake I am doing.