Testing should be done prior to Feb 4th 2016 when we make the change in API Sandbox. We have split up the preparation section to cover inbound calls to Zuora for browser based traffic as well as API based traffic. This change will impact all channels including SOAP APIs, REST APIs and browser based traffic (UI). Zuora will disable TLS 1.0 for all inbound calls to production on October 13th, 2016. Services environments with suffix ranging from 276-385 Services environments with suffix ranging from 101-266

For the specific implementation date for your service tenant, please submit a ticket through our Support Center. On February 4th 2016 from 7 AM PST - 11 AM PST, we will enforce TLS 1.1 or higher protocols only and disable TLS 1.0 connections for API Sandbox.įrom March 17th-31st 2016 7AM PST - 11AM PST, we will enforce TLS 1.1 or higher protocols only and disable TLS 1.0 connections for Services. Phase 1 - APISandbox and Services Environment We will take a phased approached to disabling TLS 1.0 for both inbound and outbound API calls to allow customers ample time to test and ensure your preparation.

This change will affect all incoming web browser based traffic as well as API traffic to both API Sandbox and Production. To maintain alignment with industry standard best practices and comply with PCI DSS requirements, Zuora will disable the use of TLS 1.0 for inbound connections to Zuora as well outbound callouts from Zuora. To maintain the highest security standards and promote the protection of your data, we occasionally need to make security improvements and deprecate older encryption protocols. At Zuora, our customers trust is our #1 value, and we take the protection of our customers' data very seriously.

App to test tls 1.2 .net 3.5