Hi @linda.monincx ,

what do you mean by “the new TLS 1.2 version"? TLS 1.2's current definition has been around for more than 10 years I think. As the default for Azure SQL DB is to enforce TLS 1.2 as a minimum and SQL Server 2022 is stricter with security it has been working for a while.

There might be issues if you are wanting to use cipher suites that are outside of the default.

Hi Rory,

You are right it is not new but I am faced with the situation that by the end of this month only TLS 1.2 can be used and older versions will no longer work, I need to know if this will have any impact on my system with TimeXtender, I have no clue where I can see if TX is using TLS and in case it does where to see what version is currently being used

Hi,

whether enforcing TLS 1.2 or higher will have an impact in your infrastructure depends on the settings of your infrastructure. If you are communicating with remote hosts that only accept TLS 1.1, you will run into issues. The only way to really know is to test each host: https://stackoverflow.com/questions/40557031/command-prompt-to-check-tls-version-required-by-a-host

All Azure resources, modern Windows versions, TimeXtender should work with TLS 1.2 but your source systems may not.

Hi @linda.monincx 

We have gotten similar questions throughout the years. The simple answer is yes that version of TimeXtender supports TLS 1.2.

I found this message which explains it.

TimeXtender and ODX are applying security in accordance with the general security framework of the Windows system running the applications. So, the application is protocol agnostic – we only enforce security on an abstract level and therefore expect this to work.

Just be aware of the capability of the server endpoints being able to support the required protocols.