Why is Context.User.Identity.Name always empty?

Question

Context.User.Identity.Name is always empty, currently I am using WebForms:

HttpCookie cookie = new HttpCookie("jamal");
cookie.Value = "bilal";
HttpContext.Current.Response.Cookies.Add(cookie);

Here I want username:

public override Task OnConnected()
{
    AddUser(Context.User.Identity.Name, this.Context.ConnectionId);
}

private static void AddUser(String username, String connectionId)
{
    ISet<String> connections;

    if (users.TryGetValue(username, out connections) == false)
    {
        connections = users[username] = new HashSet<String>();
    }

    connections.Add(connectionId);
}

Where do you call the `Context.User.Identity.Name` ? Also, is the user authenticated? — Haitham Shaddad, Nov 01 '16 at 11:50

score 1 · Answer 1 · answered Nov 01 '16 at 11:39

1

This happens because you haven't required authentication for this action.
Require that the user is authorized for the action by decorating it with the Authorize attributeclass - which will initiate the authentication negotiation. I never tried with webform but it should work if you add in the web config this rule:

<authentication mode="Forms" />

answered Nov 01 '16 at 11:39

Tinwor

7,765
6
35
56

– bilal Nov 01 '16 at 12:08

score 0 · Answer 2 · answered Nov 01 '16 at 11:26

0

Try to call this on Page_Load event, you are probably calling it too soon.

answered Nov 01 '16 at 11:26

HoTTab1CH

199
3
20

score 0 · Answer 3 · edited May 23 '17 at 12:16

The way you are creating your cookie, it is not an authentication cookie. Asp.net handles the authentication process for you if you create a new asp.net web forms project. But if you want to create your own authentication cookie, these are the steps that you have to follow.

The FormsAuthenticationModule from asp.net authenticates the user by checking the authentication ticket. Your cookie has only one name. You have to create the ticket. Also check this link.

Why is Context.User.Identity.Name always empty?

3 Answers3