In your course, "Complete Web API in .NET 5 Consumed with Blazor WebAssembly" , do you create Identity Server 4 as an external auth app provider where a standalone Blazor WebAssembly app will use the oidc service to connect to it or as part of a hosted Blazor WebAssembly app?
Not the one you create with visual studio. I created the web assembly app first for working with the web API and then created a separate identity server 4 project used as a auth provider. Hope I answered your question.
@@FrankLiuSoftware So you create a Web Api application that is protected using an auth provider which is a standalone Identity Server 4 application. Then, you create a standalone Blazor WebAssembly app that uses the oidc service to connect to the auth provider for authentication and access the protected resources in the Web Api app. A total of 3 running applications, right?
Great, that's exactly what I wanted to learn. I also wanted to know if your course covers refreshing tokens in Blazor WebAssembly. If not, based on the setup of the course, how can we handle refreshing expired tokens in Blazor WebAssembly app so users stay signed in. My understanding is that Blazor does not support silent token refresh out of the box.
@@FrankLiuSoftware afaik it is IL code which gets sent over the wire to be interpreted by dotnet.wasm (formerly mono). Are there any plans to compile serverside wasm from C# and use that directly?
Thank you for these informative shorts.
In your course, "Complete Web API in .NET 5 Consumed with Blazor WebAssembly" , do you create Identity Server 4 as an external auth app provider where a standalone Blazor WebAssembly app will use the oidc service to connect to it or as part of a hosted Blazor WebAssembly app?
Not the one you create with visual studio. I created the web assembly app first for working with the web API and then created a separate identity server 4 project used as a auth provider. Hope I answered your question.
@@FrankLiuSoftware So you create a Web Api application that is protected using an auth provider which is a standalone Identity Server 4 application. Then, you create a standalone Blazor WebAssembly app that uses the oidc service to connect to the auth provider for authentication and access the protected resources in the Web Api app. A total of 3 running applications, right?
That is correct.
Great, that's exactly what I wanted to learn. I also wanted to know if your course covers refreshing tokens in Blazor WebAssembly. If not, based on the setup of the course, how can we handle refreshing expired tokens in Blazor WebAssembly app so users stay signed in. My understanding is that Blazor does not support silent token refresh out of the box.
Is it okay to say that blazor web assembly is equivalent to Next js?
Not the same at all
@@FrankLiuSoftware so which type of blazor uses server side rendering?
@@geepy5708im new to dotNet thing but i think blazore server is similar to nextjs server side rendering
Does it still use the Mono Runtime?
With .NET 5, it uses dotnet.wasm instead.
@@FrankLiuSoftware thank you!
You are welcome!
@@FrankLiuSoftware afaik it is IL code which gets sent over the wire to be interpreted by dotnet.wasm (formerly mono). Are there any plans to compile serverside wasm from C# and use that directly?
I am not aware of it. It would be cool though.