Base solution for your next web application
Open Closed

SignalR multiple hub discrimination regression issue #12322


User avatar
0
slamj1 created

ASPNETZERO Version info:

13.1.0, 14.0.0, ASP.NET Core + Angular

Greetings,

It seems the following commit has broken multiple SignalR hubs with respect to Hub connection discrimination:

Commit 30b70e9a7f4395a2103219cdfd4b9499d35ebf3b Author: İsmail ÇAĞDAŞ [email protected] Date: March 21, 2024 4:12 AM Parent: 842a0d93 Remove generic IOnlineClientManager and its implementation

The removal of the generic versions of OnlineClientManager, OnlineClientStore, InMemoryOnlineClientStore and RedisOnlineClientStore has caused IOnlineClinetManager.GetAllByUserIdAsync to get all connections from all hubs, regardless if a generic discriminator is used.

Background: We have 4 independent hubs that rely on segregation of connection ids. This commit broke that functionality.

To reproduce and verify the issue, we re-created the generic versions of the above classes and registered them appropriately. This did fix the issue and restore Hub connection discrimination.

Cheers, Sam.


No answer yet!