Extending ASP.NET Identity

Question

It seems this has been asked many times, in many ways, none of which seem to fit my exact situation.

Here's a line from my _LoginPartial.cshtml file:

@Html.ActionLink("Hello " + User.Identity.GetUserName() + "!", "Manage", "Account", routeValues: null, htmlAttributes: new { title = "Manage" })

See the part that says User.Identity.GetUserName()?

I want to change it to User.Identity.FirstName or User.Identity.GetFirstName().

I don't want it to say "Hello email address", but rather "Hello Bob"

My thought is that I'm simply wanting to show a new property (or method) on the Identity class. Obviously it must be more than that.

I've added the FirstName property and it is available in the AccountController.

public class ApplicationUser : IdentityUser
    {
        public string FirstName { get; set; }
        public string LastName { get; set; }

It does not get exposed in the _LoginPartial file. I want it exposed there!

Thank you for your help

you could always to a db call where Email is User.Identity.GetUserName(); — jbutler483
– jbutler483, Commented Aug 20, 2014 at 15:00

ryanyuyu · Accepted Answer · 2015-06-12 12:53:12Z

11

Even though your answer wasn't "exactly" what I wanted, your comments led me to this solution:

@using Microsoft.AspNet.Identity
@using YourModelnameHere.Models
@if (Request.IsAuthenticated)
{
using (Html.BeginForm("LogOff", "Account", FormMethod.Post, new { id = "logoutForm", @class = "navbar-right" }))
{
    @Html.AntiForgeryToken()

    <ul class="nav navbar-nav navbar-right">
        <li>
            @{
                var manager = new UserManager<ApplicationUser>(new Microsoft.AspNet.Identity.EntityFramework.UserStore<ApplicationUser>(new ApplicationDbContext()));
                var currentUser = manager.FindById(User.Identity.GetUserId()); 
            }
            @Html.ActionLink("Hello " + currentUser.FirstName + "!", "Manage", "Account", routeValues: null, htmlAttributes: new { title = "Manage" })

            @Html.ActionLink("Hello " + User.Identity.GetUserName() + "!", "Manage", "Account", routeValues: null, htmlAttributes: new { title = "Manage" }) // I no longer need this ActionLink!!!
        </li>
    </ul>
    }
}

And in my IdentityModel.cs file, I added the two properties FirstName and LastName

public class ApplicationUser : IdentityUser
{
    public string FirstName { get; set; }
    public string LastName { get; set; }
}

edited Jun 12, 2015 at 12:53

ryanyuyu

6,50611 gold badges53 silver badges56 bronze badges

answered Aug 20, 2014 at 14:42

user1241166

3532 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Crismogram Over a year ago

You can add @using Microsoft.AspNet.Identity.EntityFramework for a shorter code at the bottom. Good Answer Though!

JustJohn Over a year ago

oh, thanks for doing the work for me. Diffenetly don't want to show email address to someone walking by. That is half the login.

Steven Yong Over a year ago

This is useful. Added a reference here: blogs.msdn.microsoft.com/webdev/2013/10/16/…

vaheeds Over a year ago

I was confused searching all over the web. I've just forgotten to add a @using MyProj.Models to access ApplicationUser. I've added custom properties already!! Thanks for the solution!

Brendan Green · Accepted Answer · 2014-08-20 12:38:55Z

8

I've done this by adding the First and Last Name to the claim when the user logs in, and then writing my own extension method.

When the user logs in, add the details you want to the set of claims (AccountController):

private async Task SignInAsync(ApplicationUser user, bool isPersistent)
{
    AuthenticationManager.SignOut(DefaultAuthenticationTypes.ExternalCookie);
    var identity = await UserManager.CreateIdentityAsync(user, DefaultAuthenticationTypes.ApplicationCookie);

    // Add the users primary identity details to the set of claims.
    var pocoForName = GetNameFromSomeWhere();

    identity.AddClaim(new Claim(ClaimTypes.GivenName, pocoForName));

    AuthenticationManager.SignIn(new AuthenticationProperties() { IsPersistent = isPersistent }, identity);
}

The extension method, which just pulls the details from the set of claims for the user:

public static class IdentityExtensions
{
    public static IdentityName GetGivenName(this IIdentity identity)
    {
        if (identity == null)
            return null;

        return (identity as ClaimsIdentity).FirstOrNull(ClaimTypes.GivenName);
    }

    internal static string FirstOrNull(this ClaimsIdentity identity, string claimType)
    {
        var val = identity.FindFirst(claimType);

        return val == null ? null : val.Value;
    }
}

Now in the partial, just call the new extension method to get the details you want:

@Html.ActionLink("Hello " + User.Identity.GetGivenName() + "!", "Manage", "Account", routeValues: null, htmlAttributes: new { title = "Manage" })

EDIT: updated to match more closely the original posters version of the SignInAsync() method

private async Task SignInAsync(ApplicationUser user, bool isPersistent) 
{ 
    AuthenticationManager.SignOut(DefaultAuthenticationTypes.ExternalCookie);  

    var identity = await user.GenerateUserIdentityAsync(UserManager);
    //add your claim here

    AuthenticationManager.SignIn(new AuthenticationProperties() 
        { 
            IsPersistent = isPersistent 
        }, identity);
}

edited Aug 20, 2014 at 12:38

answered Aug 20, 2014 at 1:24

Brendan Green

11.9k5 gold badges47 silver badges82 bronze badges

8 Comments

user1241166 Over a year ago

Thank you for the quick response. Suppose I want to retrieve a value that already exists, such as EmailConfirmed? Is that much different?

Brendan Green Over a year ago

No. All you need to do is add additional claims in the SignInAsync method (pulling the data from wherever you have it stored), and then create corresponding extension method(s) to retrieve them.

user1241166 Over a year ago

private async Task SignInAsync(ApplicationUser user, bool isPersistent) { AuthenticationManager.SignOut(DefaultAuthenticationTypes.ExternalCookie); AuthenticationManager.SignIn(new AuthenticationProperties() { IsPersistent = isPersistent }, await user.GenerateUserIdentityAsync(UserManager));

user1241166 Over a year ago

Thanks for your responses. This does not work for me - no surprise there - not placing blame at all, but I will keep looking. Have a good evening.

Brendan Green Over a year ago

What is your SignInAsync doing? Is that what you posted above? If so, you are not setting any claims to the identity.

|

Giulio Fronterotta · Accepted Answer · 2016-11-14 22:59:29Z

0

answer updated for Asp .net Core ! Hope this save some time to other users.

@if (SignInManager.IsSignedIn(User)){

<form asp-area="" asp-controller="Account" asp-action="LogOff" method="post" id="logoutForm" class="navbar-right">
    <ul class="nav navbar-nav navbar-right">
        <li>
            @{

                var currentUser = await UserManager.FindByEmailAsync(User.Identity.Name);
            }

            <a asp-area="" asp-controller="Manage" asp-action="Index" title="Manage">Hello @currentUser.FirstName </a>
        </li>
        <li>
            <button type="submit" class="btn btn-link navbar-btn navbar-link">Log off</button>
        </li>
    </ul>
</form>

}

answered Nov 14, 2016 at 22:59

Giulio Fronterotta

293 bronze badges

Collectives™ on Stack Overflow

Extending ASP.NET Identity

3 Answers 3

4 Comments

8 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

4 Comments

8 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related