As Sage has communicated to partners and customers for over a year, TLS 1.0 and 1.1 will no longer be supported by Sage License Servers beginning in October 2023. This means that Sage 100 subscription products using these older TLS protocols may not communicate with the Sage License Servers and could go into read-only mode.
Today, Sage announced they’ve developed a means to pace the impact on customers in batches. The timing of this change means that some customers will now have until March 1, 2024, when Sage expects to complete the TLS changes.
Which Sage 100 versions are already TLS 1.2 compliant?
- 2020.1 (PU1)
- 2019.4 (PU4)
- 2018.10 (PU10)
If you are on one of these releases or higher, your Sage 100 product is already compatible with TLS 1.2 and will not be impacted by this change.
What happens to customers not using a TLS 1.2 compliant version of Sage 100 or Sage 300?
Noncompliant customers will begin receiving warnings beginning with renewals dated October 2023. The notice will say that their product subscription has expired, and they have 45 days to upgrade their product to a TLS 1.2 compliant version before it goes into read-only mode.
How is Sage pacing the impact on customers?
To minimize any business impact, Sage is pacing the TLS 1.0/1.1 deprecation in batches, which they expect to finalize by March 1, 2024. These batches’ timing, size, and allocation are still being determined.
What can customers do to prepare for the TLS 1.2 compliance requirement?
If you use a version of Sage 100 that is not TLS 1.2 compliant, you should contact your Sage partner or reseller to discuss your upgrade options.
We encourage all customers to upgrade to a TLS 1.2 compliant version of Sage 100 as soon as possible to avoid disrupting their business.