This might be specific to NYC licensees but is anyone else dealing with First Data disabling TLS v1.0 next month? If so, did they or Vantiv provide any way to test your configuration to insure that CC processing will still function on Feb 15th with that change? I haven't had much luck getting any assistance with Vantiv. Any help or contacts would be much appreciated.
I got a letter about this today as well. We are on RAMP and TNEW And Vantiv. Please share this information.
Jason Song
Scottsdale Arts
Adding an update here, we're a non-RAMP client running Tessitura v12.5.1.
We've disabled TLS v1.0 in our DEV environment which is a single server running the full application, DB, App, IIS, and reporting. The Tess client passed UAT and successfully auth'ed CC using Vantiv's emulation site.
In our QA environment, we've disabled TLS v1.0 on our app server(CC gateway) as well as our separate IIS server and we successfully auth'ed CC using Vantiv's emulation site as well. Regression testing here was also successful.
We're planning to make the changes in our STG environment today which will be our first opp to test our site, TNEW, and Ingenico's. Will update with results.
Thank you for this info Michael Johnson
We disabled TLS v1.0 on our STG IIS and CC gateway servers and also successfully auth'ed using Vantiv's emulation site. Ingenico was good as well. Thought we could test NScan in STG but forgot that we run it over http in STG so we'll have to wait until next week when we test PROD.
We tested the change in Production last night, again disabling TLS v1.0 on the CC gateway server and the IIS servers, and successfully auth'ed on all channels. Waiting to confirm the transactions settle with FDMS but I expect they will. Current plan is to make the change in PROD permanent next week.
Hi Michael,
How do you determine if TLS 1.0 is enabled on your system? When checking the registry it looks like we are not using tls1.0 at all, but we're not sure how to check which SChannel is being used for which connections.
In our Tessitura_Master.ini file it looks like we're using OLE DB ([sqlca] dbms=OLE DB), which in theory is a step up from ODBC. Is OLE DB the OLE referred to in the "Enable ODBC Connections to the database" documentation?
Glad to hear the change went well in production!
Hi Caitlin,
I can't seem to find the MS link I used to get this information but hopefully this screenshot will help. This is what the registry looks like with TLS v1.0 disabled. Let me know if you have any other questions.
Best, Michael
Thank you Michael, this is helpful. Have a good week!