Important Changes for External Applications Communicating with ProgressionLIVE - Removing support for TLS 1.0 and 1.1
To enhance the security of our servers, we must remove support for certain encryption algorithms that are considered weakened.
This change may require adjustments that we cannot implement directly for our clients. That’s why we have developed an action plan to inform our clients and give them sufficient time to make the necessary adjustments.
This change will come into effect on January 27, 2025.
If your ProgressionLIVE account is integrated with an accounting system (except QuickBooks Online) or if your ProgressionLIVE account has an API integration with another system, it is very important to read the rest of this article!
What are the impacts for your ProgressionLIVE account?
You are affected by this change if:
- You have developed one or more custom applications that communicate with ProgressionLIVE via an API.
- Your accounting system synchronization agent is installed on a version of Windows no longer supported by Microsoft (prior to Windows Server 2016 or Windows 10).
However, you are not affected if:
- You use ProgressionLIVE Web or mobile without relying on external applications via an API.
- Your accounting system synchronization agent is installed on a version of Windows that supports TLS 1.2 or 1.3, such as Windows Server 2016, Windows 10, or later versions.
What are the impacts for your ProgressionLIVE account?
If you are affected by these changes and do not apply them, here are the possible consequences:
- For clients with an accounting integration (all integrations except QuickBooks Online): The transfer of invoices between ProgressionLIVE and your accounting system will no longer work.
- For clients with an API integration: Communication between the API and ProgressionLIVE will be blocked. Interaction between your external applications and ProgressionLIVE will therefore be impossible.
What you should do to avoid these situations
For clients with an accounting integration (except QuickBooks Online):
-
You will need to update the workstation where the ProgressionLIVE synchronization agent is installed to ensure it is running a version supported by ProgressionLIVE (Windows 10 or Windows Server 2016 or later).
🔗 Support Resources
Upgrade to Windows 10
Overview of Windows Server upgrades
For clients with an API integration:
- You must ensure that your integration environment supports the TLS 1.2 or 1.3 protocol. If it does not, you will need to update your integration environment.
📞 Contact the person who performed your integration for assistance.
Summary of Changes
The removal of certain encryption algorithms will result in a reduced list of supported TLS versions by our servers:
|
Supported Versions |
---|---|
Before changes |
TLS 1.0, TLS 1.1, TLS 1.2 |
After changes |
TLS 1.2 et TLS 1.3 |
List of Changes
Effective January 27, 2025, support for the following encryption algorithms will be removed.
AES128-GCM-SHA256
AES128-SHA
AES128-SHA256
AES256-GCM-SHA384
AES256-SHA
AES256-SHA256
ECDHE-ECDSA-AES128-SHA
ECDHE-ECDSA-AES256-SHA
ECDHE-RSA-AES128-SHA
ECDHE-RSA-AES256-SHA
After the changes, only the following algorithms will be supported:
ECDHE-ECDSA-AES128-GCM-SHA256
ECDHE-ECDSA-AES128-SHA256
ECDHE-ECDSA-AES256-GCM-SHA384
ECDHE-ECDSA-AES256-SHA384
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-RSA-AES128-SHA256
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-SHA384
TLS_AES_128_GCM_SHA256 newly supported
TLS_AES_256_GCM_SHA384 newly supported
TLS_CHACHA20_POLY1305_SHA256 newly supported
Minimum Versions for Technical Support
Component |
Minimum version |
Reference |
---|---|---|
Microsoft Windows |
Windows 10 / Windows Server 2016 |
|
Microsoft .NET Framework |
.NET Framework 4.7 |
|
In conclusion
If for any reason you believe you will not be able to comply with these new requirements before January 27, 2025, or if you have any questions regarding these changes, please contact our technical support team via email at: support@progressionlive.com.
Leave a comment