Jan1503
commented
1 week ago Ok, I think I found the issue:
I'm using the updated code from Javier in App.razor
This creates a nonce in case it's null like this:
Span<byte> bytes = stackalloc byte[32];
RandomNumberGenerator.Fill(bytes);
nonce = Convert.ToBase64String(bytes);
Context.Items["nonce"] = nonce;
return nonce;The original code just return null in this case.
I think this interferes with the NonceMiddleware which causes the error, that the nonce was already defined (in the updated code in App.razor).
But even if I ignore this already defined nonce, the upcoming error message about the 'RemoteNavigationManager already initialized' seems strange to me.
damienbod
Hi Damien,
I have a weird issue here and can't find the initial error thats causing it:
My project is nearly an exact copy of your 'BlazorWebFormBlazorServerOidc' project and runs absolutely fine locally.
As soon as I deploy it to an Azure Windows WebApp, I get a Server Error 500 response saying "Nonce already defined" as stated in BlazorNonceService.cs. If I comment this line out, another error is raised: 'RemoteNavigationManager already initialized'.
Attached is the stacktrace from Application Insights, maybe you could find some hint. It looks like the Middleware chain is broken or something.
There is an error raised in line 11 in NonceMiddleware.cs which is line 19 in your repo 'await next.Invoke(context);' and in line 68 in NetEscapades SecurityHeadersMiddleware.cs which is 'await _next(context);'