PasswordSignInAsync works locally, but not in Azure

Question

I have a web application working with .Net 4.5.1 and Identity 2.

In my WebApi, I have iOSLoginController.cs using code grafted from the main .NET Identity AccountController.cs. It loads from my iOS app using AFNetworking 2.0.

It works fine locally in my local iis. Magazines are fine. But when it is published in Azure, it actually does not log in, but still talks about success:

var result = await SignInManager.PasswordSignInAsync(usernameToCheck, model.Password, false, shouldLockout: false); // switch on result switch (result) { case SignInStatus.Success: <-- it says it successful ?!? 

But then, if I check AFNetworking immediately in WebView, it won’t log in and redirect to Login? ReturnURL = .. c (My application is hybrid and uses Webviews for information / statistics and for logging in for login / registration and works fine in Identity 1, this is an update site)

This is not an iOS application, it works fine with my local IIS and another regular physical server. But when I change the place where the base url for the API points to the Azure machine, it just does not register the person in ... but talks about success ... I confirmed joining the process in VS2015

I installed the machine key manually and in web.config so that it does not spin or exit the system when IIS starts the recycling process.

Any ideas?

Answer 1

Modern browsers link to the Public Suffix List for cookie domains that are considered public.

The idea of ​​the list was originally based on the need for secure top-level domains such as .com , as it would be possible for someone to set cookies for all domains ending with .com , which would affect all sites from the top level of .com .

The list also contains other domains that are considered public. This list is maintained by the community, and the azurewebsites.net domain, located among others, is part of this list.

Due to this, a person cannot configure the azure application and prohibit cookies in other applications for people in the shared domain.