Blazor (WASM) SignalR AccessTokenProvider issue (3.2.0-preview1)

[MitchellNZ]

I have recently updated my Blazor project to latest preview version (3.2.0-preview1) and I am implementing the newly provided SignalR functionality for Client Side Blazor apps.

However, I have ran into an issue when using SignalR with auth.

Following this documentation (or this) I have configured my SignalR Client to use the AccessTokenProvider.
I would expect this to send the access_token as a query param (since the web-sockets do not support Headers), but this is not happening.

---

For anyone else who might read this and want a temporary work-around, thanks to @szmalec from the Blazor gitter chat. You can do something like the following:
.WithUrl(NavigationManager.ToAbsoluteUri("/chatHub?access_token=XXXX"))

But please be aware, this should only be temporary until the issue is fixed, as this method does not support WithAutomaticReconnect().

[BrennanConroy]

Basically a dupe of #18694

[MitchellNZ]

@BrennanConroy ahh, yes it is.
@anurse was who recommend I raise the issue (on the aspnet blog post), but I see he beat me to it!

[analogrelay]

Oops! Let's dupe mine to yours since I did in fact ask you to file it 😝.

[analogrelay]

From my issue:

We can use the following code to detect Blazor WASM:

var isWasm = RuntimeInformation.IsOSPlatform(OSPlatform.Create("WEBASSEMBLY"));

[campersau]

Detecting wasm like this might change in the future mono/mono#18627

[analogrelay]

I think we should look at including SignalR Client in the "3.2" release as part of this so we don't have to patch it.

[mkArtakMSFT]

Added to our project for tracking the progress