Add more hints about close connection reason.

Author: Y-Sindo

samples/Management/NegotiationServer/Controllers/NegotiateController.cs

@@ -40,7 +40,11 @@ private async Task<ActionResult> NegotiateBase(string user, ServiceHubContext se
                 return BadRequest("User ID is null or empty.");
             }
 
-            var negotiateResponse = await serviceHubContext.NegotiateAsync(new() { UserId = user });
+            var negotiateResponse = await serviceHubContext.NegotiateAsync(new()
+            {
+                UserId = user/*,
+                EnableDetailedErrors = true*/
+            });
 
             return new JsonResult(new Dictionary<string, string>()
             {

samples/Management/NegotiationServer/README.md

@@ -35,19 +35,19 @@ namespace NegotiationServer.Controllers
 
 ### Create instance of `ServiceHubContext`
 
-`ServiceHubContext` provides methods to generate client endpoints and access tokens for SignalR clients to connect to Azure SignalR Service. Wrap `ServiceHubContext` into a [`IHostedService`](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-5.0) called `SignalRService` so that `ServiceHubContext` can be started and disposed when the web host started and stopped.
+`ServiceHubContext` provides methods to generate client endpoints and access tokens for SignalR clients to connect to Azure SignalR Service. Wrap `ServiceHubContext` into a [`IHostedService`](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host?view=aspnetcore-5.0) called `SignalRService` so that `ServiceHubContext` can be started and disposed when the web host starts and stops.
 
-In `SignalRService` class, create the `ServiceHubContext`.
+In `SignalRService` class, create the `ServiceHubContext`. In the sample we have two hub, message hub and chat hub to demostrate how to set up multiple hubs. The chat hub is actually not used.
 
 ```C#
 public async Task StartAsync(CancellationToken cancellationToken)
 {
     using var serviceManager = new ServiceManagerBuilder()
         .WithConfiguration(_configuration)
-        //or .WithOptions(o=>o.ConnectionString = _configuration["Azure:SignalR:ConnectionString"]
         .WithLoggerFactory(_loggerFactory)
         .BuildServiceManager();
-    HubContext = await serviceManager.CreateHubContextAsync(Hub, cancellationToken);
+    MessageHubContext = await serviceManager.CreateHubContextAsync(MessageHub, cancellationToken);
+    ChatHubContext = await serviceManager.CreateHubContextAsync(ChatHub, cancellationToken);
 }
 ```
 
@@ -63,7 +63,6 @@ public Task StopAsync(CancellationToken cancellationToken) => HubContext?.Dispos
 In the `NegotiateController` class, provide the negotiation endpoint `/negotiate?user=<User ID>`.
 
 We use the `_hubContext` to generate a client endpoint and an access token and return to SignalR client following [Negotiation Protocol](https://github.com/aspnet/SignalR/blob/master/specs/TransportProtocols.md#post-endpoint-basenegotiate-request), which will redirect the SignalR client to the service.
-
 ```C#
 [HttpPost("negotiate")]
 public async Task<ActionResult> Index(string user)
@@ -83,6 +82,16 @@ public async Task<ActionResult> Index(string user)
 }
 ```
 
+The sample above uses the default negotiation options. If you want to return detailed error messages to clients, you can set `EnableDetailedErrors` as follows:
+
+```C#
+var negotiateResponse = await serviceHubContext.NegotiateAsync(new()
+{
+    UserId = user,
+    EnableDetailedErrors = true
+});
+```
+`EnableDetailedErrors` defaults to false because these exception messages can contain sensitive information.
 ## Full Sample
 
 The full negotiation server sample can be found [here](.). The usage of this sample can be found [here](<https://github.com/aspnet/AzureSignalR-samples/tree/master/samples/Management#start-the-negotiation-server>).

samples/Management/README.md

@@ -44,13 +44,17 @@ dotnet run
 Once the message publisher get started, use the command to send message
 
 ```
-send user <User ID List (Separated by ',')> <Message>
-send users <User List> <Message>
+send user <User Id> <Message>
+send users <User Id List (Seperated by ',')> <Message>
 send group <Group Name> <Message>
-send groups <Group List (Separated by ',')> <Message>
-usergroup add <User ID> <Group Name>
-usergroup remove <User ID> <Group Name>
+send groups <Group List (Seperated by ',')> <Message>
+usergroup add <User Id> <Group Name>
+usergroup remove <User Id> <Group Name>
 broadcast <Message>
+close <Connection ID> <Reason>
+checkexist connection <Connection ID>
+checkexist user <User ID>
+checkexist group <Group Name>
 ```
  For example, type `broadcast hello`, and press keyboard `enter` to publish messages.
 

samples/Management/SignalRClient/Program.cs

@@ -4,7 +4,6 @@
 using System;
 using System.Collections.Generic;
 using System.Linq;
-using System.Runtime.CompilerServices;
 using System.Threading.Tasks;
 using Microsoft.AspNetCore.SignalR.Client;
 using Microsoft.Extensions.CommandLineUtils;
@@ -62,8 +61,13 @@ static HubConnection CreateHubConnection(string hubEndpoint, string userId)
 
             connection.Closed += ex =>
             {
-                Console.WriteLine(ex);
-                return Task.FromResult(0);
+                Console.WriteLine($"The connection of '{userId}' is closed. Exception: {ex}");
+                if (ex == null)
+                {
+                    Console.WriteLine("If you expect non-null exception, you need to turn on 'EnableDetailedErrors' option during client negotiation.");
+                }
+
+                return Task.CompletedTask;
             };
 
             return connection;