All this CSRF auto-magic is nice but poses a problem when you cannot resolve where an error comes from

[Rhywden]

[EDIT by guardrex to change the article and update the Document ID]

[EDIT by guardrex to clarify that this is a doc request, probably covered by https://github.com/dotnet/AspNetCore.Docs/issues/30647]

Description

I added an OIDC provider as an authentication source to the new Blazor Web App. Redirecting to the login page works, logging in an redirecting back works as well.

Only then I get an error that the antiforgery-token is missing. That's nice. And for the life of me, I cannot figure out how to configure or disable this issue because you actively hid the token validator somewhere.

I'm talking about the included default "Blazor Web App" with "Individual Accounts" enabled. I have no chance to override the issue (or analyze anything really) because I cannot see where the problem is coming from. There are no visible "RequireAntiforgery" attributes anywhere.

Page URL

None

Content source URL

None

Document ID

None

Article author

Rick-Anderson

[guardrex]

Stand-by @Rhywden ... I'll get back to you shortly.