shawty / blazor.jwttest Goto Github PK

If one were to use server-side Blazor, how would this affect the use of JWT? I'm starting with a server-side project with the intention of later switching to webassembly. In other words, besides changing the .js file referenced and the startup plumbing, what would have to change regarding JWT when .NET Core would host the client app, rather than webassembly?

I'm assuming it's a problem with the 0.7.0 release of Blazor, but if I update the Client part of the project to 0.7.0 from the 0.6.0 version that it's running on at the moment, this occurs at start up of the app:

I've mentioned this in the Blazor GItter channel, and it may end up as an issue report for Blazor.

I'm making a note of it here, so anyone cloning this repo to experiment with, will see it if they do an update.

The version of the tooling in Visual Studio seems to have no effect on this, I have the latest tooling in VS, but this also happens when executed using "dotnet run" at the CLI.