Prerendering client-side blazor and authorization

[Infactum]

I'm trying to use prerendering in client side application. Some pages uses http requests to backend REST service which requires authorization. Authorization itself is based on AspNet Identity.
It seems that there is no way to archeive valid client auth state during prerendering now.

[mkArtakMSFT]

Thanks for contacting us, @Infactum.
We plan to provide guidance about this in the future.
For now, here is some high level guidance.
Because the prerendering is happening on the server, you can have all your auth-related logic exposed through some interface and different implementations registered in the DI. Your actual app should then consume that service to run auth logic, and based on whether it's prerendering or not it will use the right implementation to work.

[sabitertan]

@Infactum If I understand right this repo should be answer : https://github.com/MV10/BlazorOIDC

I am also using MV10's idea in a conjuction with

https://github.com/IdentityModel/IdentityModel.AspNetCore

to add token sharing/management with 3rd party HttpClients.
Also this is an experimental Hybrid solution that uses oidc-client-js with JSInterop:
https://github.com/sabitertan/BlazorAspnetHostedOidcJS

I am working on a sample using IdenityModel only. Hope to finish up and share :)