Everything breaks when TLS1.0 is disabled

Hello All,

We recently upgraded to Tessitura v14.02 and we are currently going through our PCI certification process.

We have a web server we use for the ticketing website running Server 2012R2, another web server running Server 2012R2 for the API websites, a Windows 2016 server running SQL 2016 (Impresario DB in 2014 mode).  When we modify the windows registry to disable the TLS 1.0 protocol for both client and server keys, everything stops communicating.  Pulling an event detail on the ticketing website causes an exception (SSL/TLS related) and running the Tessitura application produces an error trying to connect to the DB.

Has anyone else experienced similar issues? This makes PCI compliance quite difficult and Vantive is not liking this fact too much.

Much Thanks!

Parents
  • This may or may not help, but what I would try would be to use this free GUI utility to modify these settings rather than modifying the registry yourself: https://www.nartac.com/Products/IISCrypto

    There are templates for PCI compliance that will make sure TLS 1.0 is disabled but 1.1 and 1.2 are still available. So perhaps if the issue involves disabling too much while not enabling the right things to replace it, this could solve your problem. This utility has worked just perfectly for me in the past.

Reply
  • This may or may not help, but what I would try would be to use this free GUI utility to modify these settings rather than modifying the registry yourself: https://www.nartac.com/Products/IISCrypto

    There are templates for PCI compliance that will make sure TLS 1.0 is disabled but 1.1 and 1.2 are still available. So perhaps if the issue involves disabling too much while not enabling the right things to replace it, this could solve your problem. This utility has worked just perfectly for me in the past.

Children
No Data