Why Request.IsAuthenticated is false

Question

I have the following script:

function OpenIdLogon(e) {
        $.post(\"/Account/OpenIdLogOn/\", { token: e }, function (data) {
            $(\"#userNavigat         


        

Answer 1

The problem is the following:

At the time of making the request ($.post("/Account/OpenIdLogOn/"...) the user it not authenticated.

Then in your action method you authenticate the user, but on the Request object that represents the request the user made before you create the Auth cookie, the user was not authenticated. However, as you say on the next request it works since at that time the user has the Authentication cookie when he makes the request.

One solution here can be to create a viewmodel object to send from your controllers action method to your view. This viewModel can have a field called authenticated, and you can set it properly from the action method. Then check this value instead inside your view. I haven't checked this in Visual Studio, but it should be something like this:

Create the viewmodel:

public class LoginViewModel{
  public bool Authenticated{ get; set; }
}

Your action method:

    public ActionResult OpenIdLogOn(string token)
    {
        WebClient cli = new WebClient();
        string json = cli.DownloadString(new Uri("http://ulogin.ru/token.php?token=" + Request.Params["token"] + "&host=" + Request.Url.Host));
        var obj = JObject.Parse(json);
        var viewModel = new LoginViewModel{ Authenticated = Request.IsAuthenticated };

        if (obj["error"] == null)
        {
            var userName = obj["nickname"].Value();
            var email = obj["email"].Value();
            FormsAuthentication.SetAuthCookie(userName, true);        
            viewModel.Authenticated = true;            
        }

        return PartialView("UserNavigation");
    }

And your view

@model LoginViewModel
@if (Model.Authenticated)
{
  @Context.User.Identity.Name
  

    
Profile
    

        @Html.ActionLink("Logg Off", "LogOff", "Account", null, new { @class = "exit"     })
  
}
else
{    
  

    
Register
    
Log On
  
}

Creating a viewmodel instead of just sending a bool as model is just because I like to always put the data I send to a view inside a viewmodel. Makes it much easier to extend later on, and makes it easier to read inside the view (you can write @if (Model.Authenticated) instead of @if (Model) for example)