webutilities | improve client side performance of your Java EE web

After a lot of headaches, I have now reached a conclusion to my problem. I solved it by implementing my own token provider and registering it with the system. In case anyone else crashes into the same wall as I did, I leave my solution here.

Step 1: Implement IUserTwoFactorTokenProvider

Seems your register failed (maybe the user already exists), so it return back to the current page instead of going to confirm, while you didn't show the error message in the view, so you don't know if the account is successfully registerd.

Add this line to your custom Register view to show the error message:

Minor correction of URL syntax methodology

You have:

I think you might need to move the environment variable from env in your .vscode/launch.json file to environmentVariables in the "Web" property in Web/Properties/launchSettings.json.

docs.microsoft.com reference

I have confirmed if I search for FormFileValueProviderFactory in the ValueProviderFactories in my DisableFormValueModelBindingAttribute, I can find it by simply doing a Where(p => p.GetType().Name == "FormFileValueProviderFactory").FirstOrDefault(). Then if I remove it from the factories list, everything just works.

So the question now becomes why cannot I reference that type. Since I have the type pulled up I can look at the assembly being referenced and it is C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App\3.1.10\Microsoft.AspNetCore.Mvc.Core.dll. This means it is not even using the NuGet at all, but is using this assembly. So I began removing older and unnecessary NuGet references when I discovered why this project is set up this way. There are some ASP.NET Core MVC utilities in a helper library, including the DisableFormValueModelBindingAttribute. This library is currently configured to be netstandard2.1, which is why the ASP.NET Core stuff cannot be referenced.

To fix this, all I had to do was change the target framework to be netcoreapp3.1 and add this to reference ASP.NET Core:

You are not actually adding roles to the token. Each role should be a claim, like this.

new Claim(ClaimTypes.Role, "));

Eg.

A range of solutions is described at Dealing with large file uploads on ASP.NET Core 1.0.

There is one important thing though that is not mentioned there - you have to remove the default binders. Otherwise buffering will kick in. Here is is how - Upload large files with streaming.

I was missing this option in startup:

I created another solution and it works. I don't know why :D