Feb 23, 2019 10:52 PM|Roberto1001|LINK
I have an MVC5 website app deployed as an Azure cloud service.
Using Owin for a Facebook login flow. All the latest Nuget packages (4.0.1 other than Identity.Owin 2.2.2 and Owin (startup components) 1.0). The app uses Owin cookie authentication (traditional logins work fine).
Testing using Chrome on Windows 10, the production server GetExternalLoginInfoAsync is returning null in the callback from signin-facebook.
- It works fine testing on localhost (both debug and release).
- On the Facebook end, everything looks normal and the app is added to the user's list of apps, with all the permissions. It's not a facebook rejection.
Looking at DevTools in Chrome:
- Cache control looks normal for everything, all no-cache.
- The .AspNet.Correlation.Facebook cookie is set and is being returned (same value) to the signin-facebook endpoint on completion from Facebook. Note that there is no other Owin related cookie.
And yet... the big null. Guys & Gals I am running out of ideas. Owin is a black box.. is there any way to get diagnostics or an error code? Everything seems to be lined up correctly, and yet... null. Most mystifying is that everything works great on localhost.
Any ideas are greatly appreciated!