custom authentication (static web app) its not working

Question

custom authentication (static web app) its not working

Dhiogo Acioli 0

Error enabling custom authentication (static web app + Blazor WASM)

Two errors occur:

1 - The "/.auth/me" API doesn't return a JSON file, but rather my HTML page (with some error).

2 - When trying to log in (.auth/login/google), it finds nothing and gives the error: Sorry, there's nothing at this address.

note1: It's worth noting that this error only occurs when I try to enable custom authentication in Azure. If I leave it in simple mode, it works normally.

note2: I tested this one month ago and it was working.

Vimal Lalani 170 Reputation points Microsoft External Staff Moderator

2025-08-11T11:02:38.1166667+00:00
Hi Dhiogo Acioli,

Thank you for posting your question on the Microsoft Q&A forum.

From your description, you are experiencing issues with custom authentication in Azure Static Web Apps when using Blazor WASM. Specifically, the /.auth/me endpoint is returning an HTML page instead of JSON, and the auth/login/google endpoint shows the message "Sorry, there's nothing at this address". You also mentioned that this issue only occurs in custom authentication mode, while simple mode works as expected, and it was working about a month ago.

To help resolve this:

Please ensure that your custom authentication configuration is set correctly. This includes allowedRoles, responseOverrides, and auth.identityProviders settings. These might have been altered when switching between simple and custom modes.

If you are using a custom ___domain, confirm that the callback URL is correctly listed in your identity provider settings.

Review the official documentation for Custom authentication in Azure Static Web Apps for detailed configuration guidance.

For further troubleshooting, could you share the following:

What changes, if any, were made to the configuration since the last time custom authentication worked? Your staticwebapp.config.json file setup.

Whether you are able to replicate the issue locally using the Azure Static Web Apps CLI.

Feel free to post back if you have more questions or need assistance with a possible workaround.
Dhiogo Acioli 0 Reputation points

2025-08-11T12:15:47.8+00:00

I said it works in simple mode to indirectly say my code is correct (precisely because it works in simple mode). I've been using the same code for three years and nothing has changed.

And when I mentioned it was working for a month, it was because: I tested it last month in custom mode because I was already thinking about switching to it, as I need to add Apple login (which isn't supported in simple (free) mode). But something changed in Azure that caused it to break. It's not related to my app or code.

To explain further: the "/auth/me" API endpoint and the ".auth/login/google" endpoint are part of Azure, and there's nothing in my code that prevents them from working (whether the code is correct or not), because it's something the static web app itself provides internally.

Your answer

Vimal Lalani 170 Reputation points Microsoft External Staff Moderator

2025-08-11T11:02:38.1166667+00:00

Hi Dhiogo Acioli,

Thank you for posting your question on the Microsoft Q&A forum.

From your description, you are experiencing issues with custom authentication in Azure Static Web Apps when using Blazor WASM. Specifically, the /.auth/me endpoint is returning an HTML page instead of JSON, and the auth/login/google endpoint shows the message "Sorry, there's nothing at this address". You also mentioned that this issue only occurs in custom authentication mode, while simple mode works as expected, and it was working about a month ago.

To help resolve this:

Please ensure that your custom authentication configuration is set correctly. This includes allowedRoles, responseOverrides, and auth.identityProviders settings. These might have been altered when switching between simple and custom modes.

If you are using a custom ___domain, confirm that the callback URL is correctly listed in your identity provider settings.

Review the official documentation for Custom authentication in Azure Static Web Apps for detailed configuration guidance.

For further troubleshooting, could you share the following:

What changes, if any, were made to the configuration since the last time custom authentication worked? Your staticwebapp.config.json file setup.

Whether you are able to replicate the issue locally using the Azure Static Web Apps CLI.

Feel free to post back if you have more questions or need assistance with a possible workaround.
Dhiogo Acioli 0 Reputation points

2025-08-11T12:15:47.8+00:00

I said it works in simple mode to indirectly say my code is correct (precisely because it works in simple mode). I've been using the same code for three years and nothing has changed.

And when I mentioned it was working for a month, it was because: I tested it last month in custom mode because I was already thinking about switching to it, as I need to add Apple login (which isn't supported in simple (free) mode). But something changed in Azure that caused it to break. It's not related to my app or code.

To explain further: the "/auth/me" API endpoint and the ".auth/login/google" endpoint are part of Azure, and there's nothing in my code that prevents them from working (whether the code is correct or not), because it's something the static web app itself provides internally.

Share via

custom authentication (static web app) its not working

Your answer