Releases: Azure/azure-signalr
Releases · Azure/azure-signalr
Release v1.15.1
Release v1.15.0
Fixes
- Fix negotiation error when using AAD and multiple endpoints. #1530
- Fix Newtonsoft.Jsonversion conflicts which might cause some failures such as AAD auth and REST API calls. #1520
- Fix a bug in the RestClientthat causes REST API calls error. #1519
- Fix security issues by updating package versions: Microsoft.AspNetCore.Http2.1.0 -> 2.1.22,Microsof.tAspNetCore.Http.Connections1.0.0 -> 1.0.15,Microsoft.AspNetCore.WebSockets2.1.0 -> 2.1.7,System.Net.WebSockets.WebSocketProtocol4.5.0 -> 4.5.3
Release v1.14.0
Known issue with this version
- We have a bug in this version that would affect:
- AAD authentication
- In Management SDK Transient transport type (the default one) : group management (such as adding users to groups, removing users from groups), client management (such as checking if user is in group).
 
Management SDK
- In persistent mode, adding a user to a group, removing a user from a group, removing a user from all groups are confirmed to be finished once the methods in ServiceHubContext.UserGroupsare returned.
- Supports a more flexible way to customize JSON serialization. You can use ServiceManagerOptions.UseJsonObjectSerializer(...)method to specify a JSON object serializer.System.Text.JsonorNewtonsoft.Jsonare both supported. See Customizing Json Serialization in Management SDK for details.
Release v1.13.0
Server SDK and Management SDK
- Attempt to fix timeout when adding to group: change ackable messages to go through random connections to reduce the burden of a single connection. #1492
Management
- Now you can get a hub context for a strongly typed hub. See details here.
Release v1.12.0
Features
Server SDK
- You can use ServiceOptions.TransportTypeDetectorto set theHttpTransportTypefor your SignalR clients. #1469
Management SDK
- In persistent transport type, adding a user to group is no more a "fire-and-forget" action now. When the task finishes, the user is in the group.
Protocols
- New CloseWithAckMessagetypes are added, including subclassesCloseMultiConnectionsWithAckMessage,CloseConnectionWithAckMessage,CloseConnectionsWithAckMessage,CloseUserConnectionsWithAckMessage,CloseGroupConnectionsWithAckMessage.
Release v1.11.0
Features
Management SDK
- ServiceHubContextnow implements- IDisposable.
- All methods in ServiceHubContext.ClientManagerare supported with persistent transport type.
- Remove limitation on setting ServiceManagerOptions.ServiceEndpointswith transient transport type. Now no matter what transport type is, you can useDefaultAzureCredentialas follows:
    var serviceManager = new ServiceManagerBuilder().WithOptions(option =>
    {
        option.ServiceEndpoints = new ServiceEndpoint[] { new ServiceEndpoint(new Uri("https://<your-signalr-name>.service.signalr.net"), new DefaultAzureCredential()) };
    })
    .BuildServiceManager();
Protocol
- Add more property to GroupBroadcastMessage (#1429)
Bug fixes
- Fix a bug in ServiceManager.IsServiceHealthythat throws exception. (#1430)
Release v1.10.0
Features
- Management SDK publishes a new set of APIs to replace the old APIs mainly to support multiple Azure SignalR instances, but the new set of APIs also provide additional benefits.
- Check Migration guide from version 1.9.x and below to 1.10.0 for migration benefits and steps.
- For users who haven't used Management SDK before, you can read this doc directly for an introduction about Management SDK.
- ServiceManagerBuilder.Build(),- IServiceManagerBuilderare obsolete.
 
- SDK client will also send AccessKeyrequest via server connection when using aad auth. [ #1361 ]
- Add ServiceEndpointconstructor for aad scenario.var endpoint = new ServiceEndpoint(new Uri("https://canary-aad-test.service.signalr.net"), new DefaultAzureIdentity()); 
- ServiceEndpoint.Endpointwill convert its hostname into lowercase even when the given hostname is in uppercase. It will also influence the generated accessToken and URL. RFC4343
- ServiceEndpoint.Endpointwill automatically add a port postfix if port=xxx was in the connection string and was not equal to 80 when HTTP or 443 when HTTPS.
- According to 5, endpoints with the same hostname but have different ports will NOT be considered equal.
Bug fixes
- Fix a bug that will let migrated connections dropped unexpectedly when the app task on the old server could not stop immediately. [ #1376 ]
Known issues:
- In Management SDK / Serverless SDK, ServiceHubContext.ClientManageris not ready withPersistenttransport type.
Release v1.9.2
Release v1.9.1
Improvements
- For ASP.NET Core SignalR, the SDK no longer cancels long-running client hub logic when the client disconnects, this behavior change makes the behavior consistent with the self-host SignalR, the discussion leading to this change is #1318 (#1332)
Bug fixes
- Workaround fix for connection migration (#1342)
Release v1.9.0
- Remove Microsoft.Azure.Services.AppAuthenticationdependency.
- Add Azure.Identitydependency to support modern AAD features.