Sage Issues Important Alert to Sage 100 Users About OAuth and TLS
By October 1, 2021 clients of Sage 100 ought to be on forms 2021.4/2022.1 or higher assuming they are utilizing Microsoft to send email through paperless office. This is because of Microsoft requiring OAuth for all API endpoints, for example, Exchange on-line and Office 365 email occupants. Likewise, Sage will never again uphold TLS 1.0 or 1.1 compelling toward the finish of the late spring 2023. This might be of more worry since a more extensive cluster of combinations - including permitting servers- may require TLS 1.2. Visit- Sage Issues Important Alerts to Sage 100 Users about OAuth and TLS The two conventions are ordinarily used to work with the sending of email from inside Sage paperless office. Sage 100 2021.4/2022.1 and higher have OAuth abilities currently set up. Sage 100 2020.1 and higher have TLS 1.2 abilities. Sage won't give any patches for more established variants to refresh their OAuth or TLS similarity.
Sage 100 and 300 Alert Censure of Microsoft Basic Authentication and TLS 1.0 and 1.1 There are two significant specialized refreshes moving toward that will influence Sage 100 and Sage 300 clients in the event that they are not on a new item discharge. These clients should move up to not be affected in a bad way. We will start to tell on-plan clients of this one week from now. Further subtleties will be posted on the Partner Hub, coming up next is an outline: Read Also-: Sage 50 on Virtual Desktop Infrastructure Compelling October 1, 2022: Microsoft will impair Basic verification and will require the utilization of current validation (OAuth) for association with servers, administrations, and API endpoints, for example, Exchange on-line and O365 email occupants. This really intends that in-item email administrations will quit working assuming clients are on renditions of Sage 100 preceding 2021.4 or for Sage 300 before