x Want to participate? Join the group to interact
  • Replies 5 replies
  • Subscribers 134 subscribers
  • Views 1408 views
  • Users 0 members are here
Browse Forums
Announcements
268
topics
260
replies
Databases and Operating Systems
758
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
851
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
876
topics
3k
replies
Sage CRM for Sage 300
182
topics
410
replies
wfnet

Which versions of Sage 300 support TLS 1.2 (i.e. for Avalara plugin)

Posted By

We have Sage 300 2020 update 2 and our Avalara plugin won't connect to the sandbox envionmnet (but it does connect to production). It appears to be because the Avalara Sandbox requires TLS 1.2 (but production doesn't until the end of this month).  

My question is whether Sage 300 2020 update 2 "supports TLS 1.2" for outgoing connections from plugins that presumably use their SDK.  And if not, what version do we need?  

We have the latest Avalara developed integration installed, on Windows Server 2016, and have verified that TLS 1.2 works from other applications.

Parents Reply Children
  • in reply to Jay Converse Acumen

    Our Sage reseller is saying "TLS 1.2 and 1.3" will be supported in an upcoming April update for supported versions.  That seems to imply it isn't supported in the current latest patch of any version, but that contradicts what Sage posted that said "Sage 300 currently supports TLS 1.2".   

    I think there may be some confusion about what kind of support we're talking about.  They might be talking about their own connection to Office 365 from wiithin thier code (MS also requires TLS 1.2 now for that).   Whereas I'm trying to find out if Sage's SDK somehow limits plugins from using TLS 1.2 to communicate with 3rd party services like AvaTax.

*Community Hub is the new name for Sage City