Changing base href in web assembly blazor has undesired results

[jDover01]

Describe the bug

After changing the base href tag in web assembly client project authentication no longer works correctly.

To Reproduce

Create new web assembly project change base href to "/client/" in index.html and add app.UsePathBase("/client") to server-side project startup.cs file

client now receives a 401 after successful login

Further technical details

• Blazor WebAssembly 3.2.0 Preview 2
• Visual Studio 2019 16.4.5

[mkArtakMSFT]

Thanks for contacting us.
Have you tried to use /client/ instead?

[jDover01]

If you are referring to server-side blazor app.UsePathBase("/client/"), yes. I have tried that as wel, with no good resultsl. It seems to be a problem with the built in Identy Server URI's and callbacks, once the base uri has changed. IMO.

[jDover01]

I have also tried using "/client/" as the docs point out here: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/blazor/?view=aspnetcore-3.1&tabs=visual-studio#app-base-path, but "/cient/" or "/client" do not fix the issue. In fact leaving off the trailing slash the web assembly client behaves as if the base href is "/".

[jDover01]

My network capture console errors after successful login and trying to call var tokenResult = await AuthenticationService.RequestAccessToken(); inside fetchdata.razor page.

The first line in the console errors is me logging the 'tokenResult' from above statement in javascript .

[jDover01]

It is also worth noting that I also tried "dotnet run --pathbase=/client" and recieve same results as above after successful login.

[javiercn]

dotnet run --pathbase=/client

This is not a thing in asp.net core apps afaik. You need to explicitly map the path.

[jDover01]

Correct. Yes, I have explicitly set the base path on client and server blazor project, but thought I would try the command and see if there was any different results. But unfortunately no.