You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
To Reproduce
Change the SignalR service Networking ACL to deny "Server Connection".
Using ManagementSDK, all the API calls look working, hubContext.Clients.All.SendCoreAsync does not throw, hubContext.ClientManager.UserExistsAsync("user1") returns false, although the ManagementSDK is not connected to the service.
Expected behavior
The API calls should throw because the SDK is not connected.
The text was updated successfully, but these errors were encountered:
vicancy
changed the title
Management SDK persistent mode does not fail when no server connection is connected
Management SDK persistent mode API calls does not fail when no server connection is connected
Oct 18, 2024
vicancy
changed the title
Management SDK persistent mode API calls does not fail when no server connection is connected
Management SDK persistent mode API calls do not fail when no server connection is connected
Oct 18, 2024
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Change the SignalR service Networking ACL to deny "Server Connection".
Using ManagementSDK, all the API calls look working,
hubContext.Clients.All.SendCoreAsync
does not throw,hubContext.ClientManager.UserExistsAsync("user1")
returns false, although the ManagementSDK is not connected to the service.Expected behavior
The API calls should throw because the SDK is not connected.
The text was updated successfully, but these errors were encountered: