John Waters

I found that if the client specifies HttpTransportType WebSockets, I dont get any connection events. If I leave it unspecified, I do.

Mu code is kind of in ripped up floorboards state right now. I will check it again in the next few days and let you know what I see. Sorry...

So got back into this now.. if I use local SignalR, it works, if I use Azure SignalR it doesnt. The hub is authorized, i.e. it has an [Authorize] attribute....

I found it I remove the Authorize attribute on my Hub it works. But of course, I dont want to do that. I am looking at the wss connection to...

Thanks! To sum up the findings so far: when using Authorize and SignalR Azure OnConnectedAsync is not called. When using plain vanilla signalr, it is. If I remove Authorize, it...

"Then SignalR Service will pass all claims in the JWT back to your app server to build a new connection" - how does it pass them back - the way...

And looking at the debug console I dont see any token authentication failing. I dont see any failures at all. On the middle tier or the client.

I looked at the token too and it has all the correct claims in it.

Its not the same auth scheme though. You are using github and cookies... my auth pipeline uses JwtBearer

How about you see if your code works with a JWT and Bearer Auth, no cookies or GitHub oauth? Also - how does the Azure SignalR service establish it's connection?...