Blazor .NET 8 Local AD Auth issue with render mode se to InteractiveServer

Question

I am working with a new Blazor app, where we use local AD to authenticate the user. I have seen very little examples on this out there, but I managed to get it to work. The problem that I have run into, is when the render mode is set to InteractiveServer.

When this is set, the page gets rendered once at the server, then again at the client. In the OnInitializedAsync() method, I am checking a user's rights to determine what information to show. On the first fire of this event, the user is obtained correctly and everything is set up correct. However, on the second call, the user information is gone, so the information will always be hidden.

I have tested it using the normal user account template, and it works. I feel like there is an issue where the user information is not getting set on the client, but I am having issues pinpointing what I am doing wrong.

Program.CS

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddRazorComponents()
    .AddInteractiveServerComponents();
builder.Services.AddServerSideBlazor();
builder.Services.AddCascadingAuthenticationState();
builder.Services.AddTransient();
builder.Services.AddAuthentication(NegotiateDefaults.AuthenticationScheme)
    .AddNegotiate(options =>
    {
        options.Events = new NegotiateEvents
        {
            OnAuthenticated = context =>
            {
                // Example: Retrieve WindowsIdentity and AD groups
                var windowsIdentity = context.Principal.Identity as WindowsIdentity;
                var adGroups = windowsIdentity?.Groups.Translate(typeof(NTAccount));

                // Add role claims to the user's identity based on AD groups
                if (adGroups != null)
                {
                    foreach (var group in adGroups)
                    {                       
                        context.Principal.Identities.FirstOrDefault().AddClaim(new Claim(ClaimTypes.Role, group.Value));
                    }
                }

                return Task.CompletedTask;
            },
            // You can handle other events as needed
        };
    }).AddIdentityCookies();

builder.Services.Configure(options =>
{
    options.DefaultScheme = NegotiateDefaults.AuthenticationScheme;
});
var connectionString = builder.Configuration.GetConnectionString("DefaultConnection") ?? throw new InvalidOperationException("No connection string in config.");

builder.Services.AddDbContextFactory((DbContextOptionsBuilder options) => 
    options.UseSqlServer(connectionString));
builder.Services.AddDatabaseDeveloperPageExceptionFilter();
builder.Services.AddRazorComponents(options => options.DetailedErrors = true);
builder.Services.AddTelerikBlazor();
var app = builder.Build();

// Configure the HTTP request pipeline.
if (app.Environment.IsDevelopment())
{
    app.UseMigrationsEndPoint();
}
else
{
    app.UseExceptionHandler("/Error", createScopeForErrors: true);
    // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
    app.UseHsts();
}

app.UseHttpsRedirection();
app.UseAuthentication();
app.UseAuthorization();
app.UseStaticFiles();
app.UseAntiforgery();

app.MapRazorComponents()
    .AddInteractiveServerRenderMode();

app.Run();

The page I am working with


@inject AuthenticationStateProvider AuthenticationStateProvider
@inject IPersonSvc PersonService
@attribute [Authorize]
@rendermode InteractiveServer
@page "/PhoneDirectory"

Page Content here
@code {

    [CascadingParameter]
    private Task? authenticationState { get; set; }

    [CascadingParameter]
    private HttpContext HttpContext { get; set; } = default!;

    List? GridData;

    private bool ViewAdditionalInfo { get; set; }
    private bool isInitialized = false;
    private ClaimsPrincipal user;
    
   protected override async Task OnInitializedAsync()
   {
       if (!isInitialized)
       {
           var authenticationState = await AuthenticationStateProvider.GetAuthenticationStateAsync();
           user = authenticationState.User;
           //First time through I have the user info, second time through it is not authenticated and the isInitialized is false again.

           // Initialization logic here
           await LoadData();
           isInitialized = true;
       }
      

       await base.OnInitializedAsync();
   }
}

App.Razor

I have tried both setting the render mode to interactive server here and leaving it and setting it at the page.

I have tried various things with no solution. Any help would be much appreciated.

Blazor .NET 8 Local AD Auth issue with render mode se to InteractiveServer

Answers (1)

Related Questions