Hello X3 Family! Today, will be an informational session about the status of Avalara's TLS 1.0 and 1.1 Deprecation and how this affects Sage X3.
If you're unfamiliar with the TLS (Transport Layer Security) protocol, this short YouTube - TLS Basics video provides a brief introduction.
I understand that the information presented may be confusing and I hope to provide clarity today about what we expect to occur as of 03/31/22 and beyond.
Avalara sent out a notification regarding the TLS deprecation around late January 2022. The announcement can be accessed HERE.
Starting with V7, in which Sage Sales Tax was implemented in the core of Sage X3. Until 2021R3 (12.0.27), the Avalara connection has utilized REST API v1 URLs indicated below:
- Test URL: https://development.avalara.net
- Production URL: https://avatax.avalara.net
Note: There may be instances where your URLs do not match those referenced above, which indicates you are utilizing custom URLs provided by Avalara. Please contact your Avalara representative for more information regarding your TLS status.
The REST v1 URLs indicated above should still allow TLS 1.0 and 1.1 until 12/31/22 according to Avalara's announcement.
Therefore, no immediate action or change is necessary. You can continue to utilize the REST API v1 URLs.
However, Sage and Avalara has been proactive in testing and provided resolutions (see Sage KB 115017) for in maintenance versions of X3.
Please review the Sage X3 Lifecycle Policy and Sage KB 105518 in relation to the maintenance phases of Sage X3.
So, what change will occur as of 03/31/22 regarding the Avalara TLS deprecation, you may ask......
Avalara will discontinue support for TLS 1.0 and 1.1 for REST API v2 URLs.
As of 2021R4 (12.0.28) and above. Sage X3 utilizes REST API v2 URLs indicated below:
- Test URL: https://sandbox-rest.avatax.com
- Production URL: https://rest.avatax.com
Note: The STANDARD REST v1 URLs referenced above are automatically replaced to the STANDARD REST v2 URLs when upgrading or patching to 2021R4 (12.0.28) and above. However, if you are utilizing custom v1 URLs, you would need to contact your Avalara representative regarding your TLS status for your custom URLs. Then, manually update the URLs via LTPAR (Setup, Usage, Sage Sales Tax connection) if necessary. Please review Sage KB 114325 as well.
Well, that concludes our information session regarding Avalara's (Sage Sales Tax/SST) TLS deprecation. Hopefully, this information has provided the necessary guidance to avoid any interruptions in processing your Sage Sales tax service.
Into X3........................ annnnnndddd Beyond!