RadzenUpload Antiforgery token validation failed. {Message}

Radzen.Blazor Components
1

I've updated my blazor server app to the new .NET 6.0 and I'm using the latest Radzen.Blazor library version 4.2.2. I have a page where I'm using the RadzenUpload component, all the code used to work properly but now I'm getting this error:

Antiforgery token validation failed. "The required antiforgery request token was not provided in either form field \"__RequestVerificationToken\" or header value \"RequestVerificationToken\"."
Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The required antiforgery request token was not provided in either form field "__RequestVerificationToken" or header value "RequestVerificationToken".     at Microsoft.AspNetCore.Antiforgery.DefaultAntiforgery.ValidateRequestAsync(HttpContext httpContext)     at Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.ValidateAntiforgeryTokenAuthorizationFilter.OnAuthorizationAsync(AuthorizationFilterContext context)

I've tried a few different approaches in an attempt to disable the validation of the token or settting it using:

 <RadzenUploadHeader Name="RequestVerificationToken" Value="@token" />

I also tried disabling the validation globally using:

            services.AddMvc().AddRazorPagesOptions(options =>
            {
                options.Conventions.ConfigureFilter(new IgnoreAntiforgeryTokenAttribute());
            });

Or on the mvc controller method that handles the file upload, using the attribute:

IgnoreAntiforgeryToken(Order = 1001)

This one also does not work:

 services.AddAntiforgery(options => { options.SuppressXFrameOptionsHeader = true; });

None of the options worked.

Any ideias?

Thanks

2

There are no changed in RadzenUpload that can cause such error. You can try any previous version for reference.

3

I downgraded to 4.0.0 but the problem remains.

4

@Jose_Mauricio Hi, I have the same problem. But I only have it in Edge, when I switch to Chrome the authentication works. Deleting all cookies did not help. Did you find out how to resolve this?

5

Appendix: after cleaning all cookies and the session cache for the user in the Azure Active Directory the problem did not re-appear after ~2 hours. If others could confirm how they were resolving this issue, this would help to find out how to avoid it.