Blazor app Reload after B2C authentication

Question

Why does a Blazor app completely reload/restart after B2C Authentication?

Here is the callback:

Thanks,
Mike

Answer 1

In standard OAuth authentication the browser is redirected to a remote token server where the login takes place. The token server redirects back to the application with an access token the Blazor application uses (Bearer) to access secured resources.

Answer 2

Hi @Michael Lambert , @AgaveJoe is correct in his answer. The app needs to reload in order to pull resources from Azure in order to display related data. Please let me know if you have any questions!

Best,
James

Answer 3

I kinda understand the cause, but it leads to a horrid user experience. When logging in, right after the login screen disappears you can see that the app reacts to the successful login by updating the <AuthorizeView><Authorized>view on the page but then immediately reloads the app. Its like ripping the rug right out from under the user and making them wait another few seconds while the app reloads..

Answer 4

The login code supports a pop up instead or redirect, but most browsers now block this, so the redirect is required. Security is also blocking iframe implementations.

If the hosting server supports authentication, you can do a simple api call to get a token instead of the oauth flow.