Выполнение действия webbrowsersettings ошибка обращения к instance clearcookie

Ответить в теме

Development discussion of all things related to creating and publishing games with Unreal Engine 4.

Members

Online

I do have an Asp.Net MVC Application (version 6.0.0-rc1-final) with custom role and user stores. After some struggling I finally could create a working login mechanism. However I do have now troubles to create a clean logout. What my logout code in the controller currently looks like:

public async Task<ActionResult> Logout()
{
    if (User.Identity.IsAuthenticated)
    {
    await SignInManager.SignOutAsync();

    }

    return RedirectToAction("Index", "App");
}

The problem with this code is, that one cookie is not deleted: .AspNet.Microsoft.AspNet.Identity.Application

As long as I don’t delete the cookie manually the application is in a dirty state and throws null pointer exceptions because User.Identity is null.

I have found a question on stackoverflow describing a similar scenario. But the solution there is not appropriate for me because I am using MVC 6 which does not have System.Web any more.

I do also have a sample solution which just works fine. In this solution the mentioned cookie is never created. Perhaps the right solution is not to delete the cookie after logout, but rather to prevent somehow the creation of the cookie.

In addition to everything already mentioned, also make sure you are not omitting the scheme argument in the calls to SignInAsync and SignOutAsync, and that you are passing the same value to both. For example:

HttpContext.SignInAsync(CookieAuthenticationDefaults.AuthenticationScheme, principal);

and

HttpContext.SignOutAsync(CookieAuthenticationDefaults.AuthenticationScheme);

So in this example the scheme is CookieAuthenticationDefaults.AuthenticationScheme. In my case I was forgetting to pass this to SignOutAsync, and while obvious after the fact, it took longer than I’d like to admit for me to track down.

answered Mar 29, 2018 at 18:39

Another gotcha that could leave the identity server cookies on the client is a logout failure. One typical cause of logout failures is a misconfiguration of the client’s PostLogoutRedirectUris.

The logout failures are not visible from the client side, the endsession call returns 200 OK, as well as the logout call.

There will however be traces on your identity server logs that the logout failed.

answered Mar 23, 2019 at 9:39