Support for TLS 1 2 in Windows App

Support for TLS 1 2 in Windows App



Support for TLS 1.2 in Windows applications

Introduced in TMS release version 8.25.0.1


TMS for Windows can now run against databases on systems where either the client or the server requires the use of TLS 1.1 or 1.2 encryption during database authentication. 
The TMS web application is not affected, it already supports database connections using TLS 1.2. 

Client updates 

Supporting the newer encryption methods requires SQL Native Client 11, which received support for TLS 1.2 around version 11.0.5592, however it is recommended that you update to the current version of the client.
Instruction for obtaining and installing the client can be found here:
https://docs.microsoft.com/en-us/sql/relational-databases/native-client/applications/installing-sql-server-native-client?view=sql-server-ver15

Also ensure that you are using the current version of the database driver bundled with TMS, dbexpsda40.dll. This should have happened automatically when you ran the installer or extracted the executables, but if you performed the process manually check that you have version 7.4.6.0 of this file. 

When this is installed, you must configure TMS to use the native client. To do this, run an up-to-date copy of localcfg.exe. A new option is available, SQL Native Client 11.0. 


 


When this option is checked, all the Windows TMS applications will attempt to use the SQL Native Client for database connections, instead of the standard OLE database driver. 


Server updates 


Ensure that your installation of SQL Server has been updated to a version that supports TLS 1.2. 

Windows updates 


Depending on the version of Windows you are running, on both the client and the server, you may need to make registry changes to support TLS 1.2. 

For a guide to setting the relevant registry entries, see:  https://docs.microsoft.com/en-us/windows-server/security/tls/tls-registry-settings



Change Compatibility level


Once the above is done, alter the database compatibility level to SQL 2014 (120) in SSMS, or by using the following SQL:

ALTER DATABASE {database name} SET COMPATIBILITY_LEVEL = 120

1





    • Related Articles

    • Best practice for raising a ticket with mitrefinch support

      Introduction The purpose of this article is to provide guidance on how best to raise mitrefinch support ticket. As a ticket with concise, useful information can be the difference between an instant solution and one that takes hours or days. Before ...

    • COVID-19 Support Services

      As the COVID-19 pandemic continues to expand in scale and severity, it’s of no surprise that it will be causing a lot of anxiety and concern to businesses worldwide who are trying to keep on top of the evolving situation, all while trying to keep ...

    • Support and Maintenance Information 2021

      At Mitrefinch we are committed to continually improving and evolving our services to you, our valued customers.  We’ve been busy over the last few months speaking with and visiting customers to find out what support you value the most. As a result, ...

    • Using TMS for Mobile as an App

      To add TMS for Mobile as an app on your mobile device, first you must open the Employee or Supervisor Dashboard in your device's browser. Navigate to the TMS Apps page to open TMS for Mobile on your mobile device.    Once the TMS for Mobile ...

    • Support for the Alabaster ruling

      Flexipay has introduced as part of the 2.56 upgrade support for the Alabaster ruling. The ruling applies for any pay rise from the start of the 8-week reference period up to the end of maternity leave. If the ruling is applicable, Flexipay will ...