3.2 KiB
| title | author | description | monikerRange | ms.author | ms.custom | ms.date | uid |
|---|---|---|---|---|---|---|---|
| Manage users and groups in SignalR | bradygaster | Overview of ASP.NET Core SignalR User and Group management. | >= aspnetcore-2.1 | bradyg | mvc | 06/04/2018 | signalr/groups |
Manage users and groups in SignalR
SignalR allows messages to be sent to all connections associated with a specific user, as well as to named groups of connections.
View or download sample code (how to download)
Users in SignalR
SignalR allows you to send messages to all connections associated with a specific user. By default, SignalR uses the ClaimTypes.NameIdentifier from the ClaimsPrincipal associated with the connection as the user identifier. A single user can have multiple connections to a SignalR app. For example, a user could be connected on their desktop as well as their phone. Each device has a separate SignalR connection, but they're all associated with the same user. If a message is sent to the user, all of the connections associated with that user receive the message. The user identifier for a connection can be accessed by the Context.UserIdentifier property in your hub.
Send a message to a specific user by passing the user identifier to the User function in your hub method as shown in the following example:
[!NOTE] The user identifier is case-sensitive.
[!code-csharpConfigure service]
Groups in SignalR
A group is a collection of connections associated with a name. Messages can be sent to all connections in a group. Groups are the recommended way to send to a connection or multiple connections because the groups are managed by the application. A connection can be a member of multiple groups. This makes groups ideal for something like a chat application, where each room can be represented as a group. Connections can be added to or removed from groups via the AddToGroupAsync and RemoveFromGroupAsync methods.
[!code-csharpHub methods]
Group membership isn't preserved when a connection reconnects. The connection needs to rejoin the group when it's re-established. It's not possible to count the members of a group, since this information is not available if the application is scaled to multiple servers.
To protect access to resources while using groups, use authentication and authorization functionality in ASP.NET Core. If you only add users to a group when the credentials are valid for that group, messages sent to that group will only go to authorized users. However, groups are not a security feature. Authentication claims have features that groups do not, such as expiry and revocation. If a user's permission to access the group is revoked, you have to manually detect that and remove them from the group.
[!NOTE] Group names are case-sensitive.