BlazorWebAssemblyStandaloneWithIdentity - AddRoles

[adrianjcalvert]

Should this sample work fine with .AddRoles?

I've downloaded the sample and changed to a persistent DbContext, registered a user and then added the relevant records to AspNetRoles and AspNetUserRoles, but when I log in on the WASM app I don't get any role claims.. The cookie increases in size by ~100 chars so my guess is the API responding with a cookie that contains the role claim but the WASM app doesnt see it for some reason.

builder.Services.AddDbContext<AppDbContext>(options =>
{
    options.UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=Testdb;Trusted_Connection=True", assembly => assembly.MigrationsAssembly(typeof(AppDbContext).Assembly.FullName));
});

// add identity and opt-in to endpoints
builder.Services.AddIdentityCore<AppUser>()
    .AddRoles<IdentityRole>()
    .AddEntityFrameworkStores<AppDbContext>()
    .AddApiEndpoints();

Should they be sent in the response to manage/info?

---

Issue Details

⚠ Do not edit this section. It is required for issue processing.

• Content Source: dotnet/blazor-samples
• GitHub Login: @guardrex

[guardrex]

Hello @adrianjcalvert ... Pinging @JeremyLikness for assistance.

[JeremyLikness]

@adrianjcalvert the claims are not sent back for security reasons, @halter73 can explain in more detail but the behavior is by design. You can stand up your own endpoint to return them or create an API to validate claims.

[guardrex]

Thanks @JeremyLikness ... I've opened dotnet/AspNetCore.Docs#31045 to add a bit to the doc on that point.

@adrianjcalvert ... I'm going to close here and use the other issue that I opened to track it. I hope I can add a really quick basic code example for the app, but no promises on that ... I'm absolutely swamped with work right now. At a minimum, I'll call out what Jeremy just stated, and I'll try to do that today.