OIDC/Okta, Aspire and Blazor

[sp00ky]

We have an Okta developer account which we're using to authenticate our Blazor WASM app via OIDC for local debugging. Because Aspire wants to launch (the proxy?) on random ports, we have no idea what to put for our signin redirect. When the browser that Aspire launches tries to initiate a login session with Okta, Okta doesn't allow it because it doesn't recognize the signin redirect port.

We specify the port that should be used in our web app's launchsettings.json but that doesn't seem to be respected. I can go to that port and indeed the app is running there. However, Blazor debugging does not work there.

We're interested in moving from Docker Compose to Aspire for our local loop but this is blocking us.

[davidfowl]

Here's the longwinded explanation about how it works https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/networking-overview.

We specify the port that should be used in our web app's launchsettings.json but that doesn't seem to be respected

Are you using blazor WASM as a standalone project running a development server or a Blazor Web app?

[sp00ky]

Blazor Web App.

[sp00ky]

I think we've found a solution. Manually specifying the return port in OnRedirectToIdentityProvider seems to do the trick

[davidfowl]

You can turn off the proxy but if you have a launch settings, ports will be used from there. I’m a bit confused on why the proxy port changes from run to run in that case