Blazor Server Authentication not working after publishing to Azure (linux)

[drma-tech]

https://site.azurewebsites.net/
signin-google
?state=xxx
&code=yyy
&scope=email+profile+openid+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email+https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.profile
&authuser=0
&prompt=none

Sorry, there is nothing at this address.

This error occurs after trying to log in to google in a blazor app after publishing in azure linux (the same did not happen in the windows environment).

logging in normally (user + password) works, but cannot communicate with the API.

[javiercn]

@drma-dev thanks for contacting us.

@blowdart this is not Blazor server specific since auth happens before the Blazor application starts (this is server-side Blazor). From what I can tell, the callback is not hitting the auth endpoint and going through the catch-all route that SSB defines instead. Note that it if goes there is because no other endpoint/handler was available.

[drma-tech]

It started after a certain time. I'm not sure if it was from a certain version of blazor or something that happened on azure.

another mistake is that if you log in with email and password (without google), it cannot call the API, because it cannot recognize the user's token or authentication.

[blowdart]

This doesn't sound generic to me @javiercn - perhaps something with the identity server integration give the inability to call the api.

regardless, @drma-dev what's in the server logs? Can you up the verbosity and try?

[javiercn]

@blowdart Blazor server doesn't use Identity Server (at least our templates). We only use it on Blazor WebAssembly.

Blazor server apps use whatever auth mechanism you want to use for a regular Web Application, all the auth happens before the Blazor Server app starts.

What is likely happening there is what I mentioned above, the auth callback endpoint is somehow not correctly configured, and it's going through the fallback route that server-side Blazor defines, but the issue is that the auth handler is not correctly configured in some way.

[blowdart]

OK in that case, startup.cs pleas @drma-dev

[drma-tech]

Even using the template (with authentication option) without changing anything in the code (forgetting this google issue), it will give an error when accessing the api with [Authorize].

And it only happens in azure (linux environment), if I publish in azure (windows environment) it works normally.

I believe that both errors (API and google) are related to the same thing.

[blowdart]

OK what template, what error? What's in the server logs?