Blazor WebAssembly Standalone app can't authenticate when deployed to Azure Static Web App

Question

I've created a Fluent Blazor WebAssembly Standalone App in Visual Studio. I've also done all the work inside AAD B2C with providers and flows and "connected" it to my app. When I run the app locally it performs flawlessly and I can register new users, log in, log out etc.

However, when I Publish this to an Azure Static Web App, the authentication fails. When I try to log in I get a 404 not found, pointing to /login-callback#?. I've checked, and my appsettings.json file containing the B2C details has been deployed correctly.

Do I need to do additional work in the Static Web App to get this working? Seems odd if that's the case. I started on the Free tier, but upgrading to the Standard tier doesn't help.

I can also confirm that both local and remote successfully hit the correct /.well-known/openid-configuration endpoint in B2C, but only the local then redirects correctly to the login page. — Chris Arnold
– Chris Arnold, Commented Apr 10 at 7:33

Chris Arnold · Accepted Answer · 2025-04-10 08:20:41Z

0

Brain fade! I'd gotten the redirect uri slight wrong in B2C. As you were :).

answered Apr 10 at 8:20

Chris Arnold

5,7735 gold badges39 silver badges56 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Blazor WebAssembly Standalone app can't authenticate when deployed to Azure Static Web App

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related