Unplanned
Last Updated: 12 Aug 2024 10:50 by ADMIN
Scheduled for 2024 Q4
Jason
Created on: 02 Mar 2022 12:59
Type: Feature Request
1
Replace the deprecated StackExchange.Redis.StrongName with StackExchange.Redis in the Report Server

We are using Azure Redis Cache for the Report Server storage. Azure Redis stops the support for TLS 1.0 and 1.1 as stated in Remove TLS 1.0 and 1.1 from use with Azure Cache for Redis.

If I set Azure Redis to allow TLS 1.0 everything works fine.

If I switch the minimum TLS version in Azure to 1.2 (or 1.1 for that matter) I start to get the error:

No connection is available to service this operation: GET TRS\1\SV
   at StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl[T](Message message, ResultProcessor`1 processor, ServerEndPoint server)
   at StackExchange.Redis.RedisBase.ExecuteSync[T](Message message, ResultProcessor`1 processor, ServerEndPoint server)
   at StackExchange.Redis.RedisDatabase.StringGet(RedisKey key, CommandFlags flags)
   at Telerik.Reporting.Cache.StackExchangeRedis.RedisStorage.GetBytes(String key)
   at Telerik.Reporting.Services.Engine.PersistableObject.GetInt(String key)
   at Telerik.ReportServer.Engine.StorageUpgrader.UpgradeStorageVersion()
   at Telerik.ReportServer.Web.Models.ReportServerWebHost..ctor(IStorage storage)
   at Telerik.ReportServer.Web.WebApiConfig.ConfigureDependencyResolver()
   at Telerik.ReportServer.Web.WebApiConfig.Register(HttpConfiguration config)
   at System.Web.Http.GlobalConfiguration.Configure(Action`1 configurationCallback)
   at Telerik.ReportServer.Web.WebApiApplication.Application_Start()

The articles I can find all state that we should add "sslprotocols=tls12" in addition to "ssl=true" in the connection string to support TLS 1.2.  When I do this I get the error "Keyword 'sslProtocols' is not supported". 

This won't let me use Azure Redis Cache.

I suspect the issue is due to the deprecated package that you use for the Redis database connection.

For that reason, I would like it to be updated to the new one so that I may continue to use Azure Redis.

0 comments