Cannot add additional claims to Blazor WebAssembly 3.2.0 Preview 4 application

[bancroftway]

I created a Asp.Net Core hosted Blazor webassembly 3.2.0 Preview 3 application with the authentication option of In-App accounts. I then added a few additional attributes to the ApplicationUser class, and migrated these changes to the database, and registered a few users, which was successful. I then implemented a custom claims factory like so:

public class MyCustomUserClaimsPrincipalFactory : UserClaimsPrincipalFactory<ApplicationUser>
{
    public MyCustomUserClaimsPrincipalFactory(
        UserManager<ApplicationUser> userManager,
        IOptions<IdentityOptions> optionsAccessor)
            : base(userManager, optionsAccessor)
    {
    }
    protected override async Task<ClaimsIdentity> GenerateClaimsAsync(ApplicationUser user)
    {
        var identity = await base.GenerateClaimsAsync(user);
        identity.AddClaim(new Claim(ClaimTypes.GivenName, user.FirstName ?? string.Empty));
        .....

        return identity;
    }
}

and registered the claims factory in the server application like so:

services.AddDefaultIdentity<ApplicationUser>(options => options.SignIn.RequireConfirmedAccount = true)
            .AddEntityFrameworkStores<ApplicationDbContext>()
            .AddClaimsPrincipalFactory<MyCustomUserClaimsPrincipalFactory>();

However, when I list the claims in a client web app component, I do not see any of the additional claims I added in the custom claims factory. The code I am using to list the claims is:

<AuthorizeView>
   <Authorized>
    <ul>
        @foreach (var claim in context.User.Claims)
        {
            <li><span>@claim.Type</span><span>@claim.Value</span></li>
        }
    </ul>
   </Authorized>
</AuthorizeView>

I verified that the claims factory code is being called. How can I get the additional claims in the client web app?
Note: I have even tried using ClaimsTransformer (as suggested here) but I still do not see the additional claims

[guardrex]

@bancroftway ... There's one more change that @javiercn supplied to me for the documentation. He has a JsonPropertyName attribute for the claim name in the UserAccount model. See the PR diff for his example ...

https://github.com/dotnet/AspNetCore.Docs/pull/17653/files#diff-bdc81c494716be6b883c9f5da3fb2f0fR143

[bancroftway]

Hey guys, this issue is getting very confusing. Could you please provide a quick step by step guide on how to achieve adding a property to ApplicationUser and show this as an additional claim on the client web app.

[guardrex]

@bancroftway ... What I have from engineering thus far is on the PR. Start with Line 132 ...

https://github.com/dotnet/AspNetCore.Docs/pull/17653/files#diff-bdc81c494716be6b883c9f5da3fb2f0fR132

That PR has to be reviewed/updated/approved, then we can merge it and take it live in the topic. For now, work from the PR diff.

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!

[dfkeenan]

I was also trying to add custom claims ("DisplayName") for the Blazor WASM (Hosted) project. I had already got Identity and AzureAD working following this guide: https://docs.microsoft.com/en-us/aspnet/core/security/blazor/webassembly/hosted-with-identity-server?view=aspnetcore-3.1&tabs=visual-studio

I had also found another article about adding custom claims for asp.net core by creating a custom IUserClaimsPrincipalFactory and registering it. i.e.

public class ApplicationClaimsPrincipalFactory :UserClaimsPrincipalFactory<ApplicationUser, ApplicationRole>
{
    public ApplicationClaimsPrincipalFactory(UserManager<ApplicationUser> userManager, RoleManager<ApplicationRole> roleManager, IOptions<IdentityOptions> optionsAccessor)
    : base(userManager, roleManager, optionsAccessor)
    {
    }


    protected override async Task<ClaimsIdentity> GenerateClaimsAsync(ApplicationUser user)
    {
        var identity = await base.GenerateClaimsAsync(user);
        identity.AddClaim(new Claim("DisplayName", $"{user.FirstName} {user.LastName}"));
        return identity;
    }
}


//.... register it. If using a custom SignInManager do it before that
services.AddDefaultIdentity<ApplicationUser>(options => options.SignIn.RequireConfirmedAccount = true)
    .AddRoles<ApplicationRole>()
    .AddEntityFrameworkStores<ApplicationDbContext>()
    .AddClaimsPrincipalFactory<ApplicationClaimsPrincipalFactory>()
    .AddSignInManager<ApplicationSiginInManager>();

This claim is available server side but not in the client. I tried many things without success but then I remembered the guide linked above tells your to create and register a IProfileService. So I thought I would see what would happen if I modified that.

public Task GetProfileDataAsync(ProfileDataRequestContext context)
{
   //...

    context.IssuedClaims.AddRange(context.Subject.FindAll("DisplayName"));

    return Task.CompletedTask;
}

Doing this worked. The claim was now available in the client. Not sure if this is the correct way to do it.

[JeepNL]

I'm trying to add and retrieve additional claims as well.

When I follow this https://docs.microsoft.com/en-us/aspnet/core/security/blazor/webassembly/hosted-with-identity-server?view=aspnetcore-3.1&tabs=visual-studio#configure-identity-server

I even can't get the "Profile Service" to work, I only see the additional roles when I use "API authorization options" of the two options. Update: just got this working, it's all about the order of statements.

Now about adding and retrieving additional Blazor WASM claims, this is a problem. Not only here but at Stack Overflow as well.

3 unanswered questions:

• https://stackoverflow.com/questions/61105563/userclaimsprincipalfactory-not-working-in-blazor-webassembly-3-1-client
• https://stackoverflow.com/questions/61178681/how-to-add-additional-claims-to-blazor-webassembly-3-2-0-preview-3-application
• https://stackoverflow.com/questions/62434400/blazor-webassembly-identityserver-eventsink-and-httpcontext

[JeepNL]

With your example @dfkeenan I got it working too, but I too don't know this is the correct way to do it. Anyone? Even this issue is already closed?

[javiercn]

We have docs for this here.

The same thing that is applied to roles can be applied to any other claim