Just like several other threads in this forum discuss, I grabbed the article Code! MVC 5 App with Facebook, Twitter,
LinkedIn and Google OAuth2 Sign-on and immediately run into a conflict that looks like new ASP.NET Identity design restriction. If that is indeed true, perhaps someone can explain to me why is that restriction necessary.
Here is the story: as soon as I created the basic app I immediately created the account
fred@acme.com and verified that I can login with this account. Only after that I followed the rest of this article (beatifully crafted by Rick Anderson and Erik Reitan), by setting up SSL and enabling Google based authentication.
I was pleasantly surprised seeing the use of Google Developers Console, as it provides a very slick integrated experience in the ...
Go to the complete details ...