As part of our ongoing commitment to platform security and compliance, we’re updating our supported connection protocols for the Clarus WMS API.

What’s changing?

Due to evolving regulatory requirements and known vulnerabilities in older versions of TLS, we’re phasing out support for TLS 1.0 and TLS 1.1.

From this point forward, all systems connecting to the Clarus WMS API must use TLS 1.2 or higher.

Why are we doing this?

TLS 1.0 and 1.1 have not been recommended for use since 2018, and are no longer considered secure or in regular operation across most modern systems.

This update ensures Clarus WMS continues to meet the latest security and compliance standards, protecting your data and maintaining the integrity of all API communications.

Will there be any downtime?

No downtime is expected. However, any systems still attempting to connect using TLS 1.0 or 1.1 will no longer be able to establish a secure connection.

What should you do?

• Check your integration, middleware, or API client configuration to confirm it supports TLS 1.2 or TLS 1.3.
  
• If possible, we strongly recommend upgrading to TLS 1.3 to benefit from improved security and performance.
  
• If you use third-party tools or middleware to connect, please ensure they’re configured to use a compliant TLS version.

Impact assessment

We’ve evaluated the impact of this change across our customer base and found that the vast majority of integrations already use TLS 1.2 or higher, so most customers will not be affected by this update.

Thank you for your cooperation as we continue to enhance the security of our platform.