-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Labels
✔️ Resolution: DuplicateResolved as a duplicate of another issueResolved as a duplicate of another issueStatus: Resolvedarea-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and servers
Description
In a scenario when server needs to have 100% control over SignalR clients (which in my view - must be always :)) for security and business logic sake (eg a subscription expired or user tries to hack connection by manipulating client side etc) - having something like the below would really help (in fact - I think this is the only way to do it properly):
hub.Clients.Client(connectionId).Close();
Additional context
it appears that implementing authorization on SignalR using Angular with IdentityServer is unfeasible without re-writing client side completely and taking all the security responsibility for the whole app, while you only need to authorize signalr,
see here: #34948 (comment)
Metadata
Metadata
Assignees
Labels
✔️ Resolution: DuplicateResolved as a duplicate of another issueResolved as a duplicate of another issueStatus: Resolvedarea-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and servers