TLS 1.0 and 1.1 Deprecation for Intuit Developers

Here at Intuit Developer, we’re focused on continually helping our developers improve their application security by using the latest security protocols. In July of 2017, we let you know you needed to upgrade to TLS 1.1.  In August of 2017, we let you know you needed to upgrade to TLS 1.2 by December 31, 2017.

Today we are announcing the deprecation timing for TLS 1.0 and 1.1.  All apps must be upgraded to TLS 1.2 by September 20, 2018.

What is happening? And, when?

  • On or before September 20, 2018, Intuit is requiring that your application upgrade to TLS 1.2 in order to align with industry best practices for security and data integrity.  On September 20, 2018, Intuit will disable both the TLS 1.0 and TLS 1.1 encryption protocols, which will prevent apps still using them from accessing Intuit and QuickBooks APIs and Services.

What is TLS?

  • TLS stands for “Transport Layer Security.” It is a protocol that provides privacy and data integrity between two communicating applications. It’s the most widely deployed security protocol used today, and is used for web browsers and other applications that require data to be securely exchanged over a network. TLS ensures that a connection to a remote endpoint is the intended endpoint through encryption and endpoint identity verification.

What do you need to do?

  • Please upgrade your application to TLS 1.2 before September 20, 2018. If you are currently using TLS 1.0 or TLS 1.1 to access the QuickBooks Accounting API, QuickBooks Payments API, or the QBMS Payments API, you will need to upgrade to TLS 1.2 before September 20, 2018. 

I have questions!

Help is available and we will answer any concerns or questions you may have.
Additional information on how to upgrade to TLS 1.2 can be found here.   

Thank you!

The Intuit Developer Group








One response to “TLS 1.0 and 1.1 Deprecation for Intuit Developers”

  1. Avetik Avatar

    I’m using .NET SDK IppDotNetSdkForQuickBooksApiV3.3.2.1 for my .NET application which runs on .NET 4.5.2 Framework.

    Does it already use TSL 1.2 ?

Leave a Reply

Your email address will not be published. Required fields are marked *