Attempting to use an incomplete authentication context

Radzen Blazor Studio
1

Hello,

After adding Windows Security to my Blazor App I got the follwing error on start:

InvalidOperationException: Attempting to use an incomplete authentication context.

  • Microsoft.AspNetCore.Authentication.Negotiate.NegotiateHandler.HandleAuthenticateAsync()

  • Microsoft.AspNetCore.Authentication.AuthenticationHandler.AuthenticateAsync()

  • Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(HttpContext context, string scheme)

  • Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)

  • Microsoft.AspNetCore.Builder.StatusCodePagesExtensions+<>c__DisplayClass7_0+<b__0>d.MoveNext()

  • Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)

  • Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)

Robert

2

It also gives the error for any new application build with Blazor Studio - before I add Windows Security it works but after it doesnt

3

Here is how to fix Program.cs - we will fix our template:

app.UseAuthentication();
app.UseStatusCodePagesWithReExecute("/not-found");
app.UseAuthorization();
4

still the same problem - here our Program.cs

using Radzen;
using ADO.Components;
using Microsoft.AspNetCore.Authentication;
using Microsoft.AspNetCore.Authentication.Negotiate;
using Microsoft.Identity.Web;
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Components.Authorization;

var builder = WebApplication.CreateBuilder(args);
// Add services to the container.
builder.Services.AddRazorComponents().AddInteractiveServerComponents().AddHubOptions(options => options.MaximumReceiveMessageSize = 10 * 1024 * 1024);
builder.Services.AddControllers();
builder.Services.AddRadzenComponents();
builder.Services.AddRadzenCookieThemeService(options =>
{
options.Name = "ADOTheme";
options.Duration = TimeSpan.FromDays(365);
});

builder.Services.AddAuthentication(NegotiateDefaults.AuthenticationScheme).AddNegotiate();
builder.Services.AddHttpClient();
builder.Services.AddAuthorization(options =>
{
options.FallbackPolicy = new AuthorizationPolicyBuilder().RequireAuthenticatedUser().Build();
});
builder.Services.AddHttpClient("ADO").AddHeaderPropagation(o => o.Headers.Add("Cookie")).ConfigurePrimaryHttpMessageHandler(() => new HttpClientHandler { UseDefaultCredentials = true });
builder.Services.AddHeaderPropagation(o => o.Headers.Add("Cookie"));
builder.Services.AddScoped<AuthenticationStateProvider, ADO.ApplicationAuthenticationStateProvider>();
builder.Services.AddControllersWithViews();
builder.Services.AddScoped<ADO.SecurityService>();

var app = builder.Build();
var forwardingOptions = new ForwardedHeadersOptions()
{
ForwardedHeaders = Microsoft.AspNetCore.HttpOverrides.ForwardedHeaders.XForwardedFor | Microsoft.AspNetCore.HttpOverrides.ForwardedHeaders.XForwardedProto
};
forwardingOptions.KnownNetworks.Clear();
forwardingOptions.KnownProxies.Clear();
app.UseForwardedHeaders(forwardingOptions);
// Configure the HTTP request pipeline.
if (!app.Environment.IsDevelopment())
{
app.UseExceptionHandler("/Error", createScopeForErrors: true);
// The default HSTS value is 30 days. You may want to change this for production scenarios, see Enforce HTTPS in ASP.NET Core | Microsoft Learn .
app.UseHsts();
}

app.UseStatusCodePagesWithReExecute("/not-found");
app.UseHttpsRedirection();
app.MapControllers();
app.UseHeaderPropagation();
app.UseStaticFiles();
app.UseAuthentication();
app.UseStatusCodePagesWithReExecute("/not-found");
app.UseAuthorization();
app.UseAntiforgery();
app.MapRazorComponents().AddInteractiveServerRenderMode();
app.Run();

5

This appears twice. It should appear only once - after app.UseAuthentication();

1 Like
6

Thanks now it works

Robert