Sage issues Important Alert to Sage 100 Users About OAuth and TLS
With the useful assistance of the Sage 100 software, businesses have been able to perform their accounting activities more efficiently these days. In this blog, we are going to discuss two important matters related to the Sage 100 application- the OAuth and TLS.
Using OAuth with Sage 100
This feature has been made available in Sage 100 2021 and later versions for paperless Office Email.
Important alert for Sage 100 Users-
The Sage Customer Support is unable to assist the Sage 100 customers while setting up the OAuth Authentication and connecting to different SMTP Mail Servers. However, they may provide information to the customers or Business Partners already familiar with the SMTP (Mail) Server in use.
Sage cannot offer guidance for all SMTP Server configurations. However, here is an example that can serve as guidance on how to connect Sage 100 to Gmail through OAuth 2.0
What are the Steps to Connect Sage 100 to Gmail using OAuth 2.0?
Here are the steps to follow-
- Click to open the Company Maintenance window
- Choose Company Code
- Set the SMTP (Mail) Server – Authentication Method as OAuth
- Set the address as smtp.gmail.com
- Set the port as Port = 587
- Specify the SMTP Encryption as TLS
- In the User ID field, enter the User’s Gmail id
- In the field named Client ID, enter the Client ID obtained from the Google Cloud Platform
- In the Client Secret field, enter the Client Secret code obtained from the Google Cloud Platform
- Specify http://account.google.com.com/o/oauth2/auth?gp=1&js=1&uuid=1685535476.0035596260&other_args=eyJ1cmkiOiAiL28vb2F1dGgyL2F1dGgiLCAiYXJncyI6ICIiLCAicmVmZXJlciI6ICIiLCAiYWNjZXB0IjogInRleHQvaHRtbCxhcHBsaWNhdGlvbi94aHRtbCt4bWwsYXBwbGljYXRpb24veG1sO3E9MC45LGltYWdlL2F2aWYsaW1hZ2Uvd2VicCxpbWFnZS9hcG5nLCovKjtxPTAuOCxhcHBsaWNhdGlvbi9zaWduZWQtZXhjaGFuZ2U7dj1iMztxPTAuNyJ9 as the Auth End Point
- Specify Token End Point
- Set the Scope as https://www.google.com/gmail/about/
- Specify the Redirect URI as http://localhost
- Set the Redirect Port as 3017
- Set the Code Challenge Method as None
if you need the 128-bit encryption while sending password-protected documents over emails, click on 128-bit Encryption for Password Protected Documents
Using TLS with Sage 100
TLS stands for Transport Layer Security. it ensures the much-needed privacy between the users and the communicating applications on the internet.
Important alert for Sage 100 Users-
In 2015, the PCI Security Standards Council came up with a mandate that merchants must discard the use of TLS 1.0 before June 2018. With effect from May 2, 2018, users of Sage 100 versions 4.5 and below (named MAS90 and MAS200 before) ceased to be TLS 1.2-compliant. Users of these versions can upgrade to a newer Sage 100 version to maintain TLS 1.2 compliance. Then only they will be able to continue processing credit cards. This became necessary as TLS 1.0 and 1.1 protocols failed to meet the minimum security requirements owing to inherent vulnerabilities observed. Thus, both these protocols TLS 1.0 and 1.1 are deemed to have a significant risk of data breaches.
In this blog, we have discussed what OAuth and TLS are and some important alerts related to these or Sage 100 users. If you have any more queries, you may speak to some authorized 1800 964 3096 Sage professionals.
Accounting Professionals & Specialized Experts
Want quick help from accounting software experts? Get in touch with our team members who can install, configure and configure your software for you. Proficient in fixing technical issues, they can help you quickly get back to work whenever you encounter an error in Sage software. Our team is available 24/7 365 days to assist you. To get in touch.
Why am I getting the ‘Failed to establish TLS Connection’ Error Message while attempting a Test E-mail?
You may receive this error message due to any of the reasons mentioned below-
🔹 The SMTP server may be accepting only some specific cipher suites/versions of TLS encryption and these are not offered currently by your version of Sage 100
For Example, the Sage 100 2018 worked on the previous protocol of TSL 1.0 or 1.1. Sage 100 2019 and higher versions are using the current standard of TLS 1.2.
🔹 Due to interference resulting from firewall restrictions, antivirus and security software.
🔹 Any data corruption related to the operating system or network.
What causes the Sage 100 Unable to Process the Lock File issue?
Two of the prominent causes are listed below-
🔹 Issues with Windows Security Settings
🔹 Issues caused by a new Windows 10 Feature Update
What are the causes of the Sage 100 Integration PVX Errors?
Some prominent causes of this error are listed below-
🔹 Certain information is missing in the SData definition file.
🔹 InstallShield is unable to complete its process due to incorrect registry files in use.
🔹 Multiple installations of the same Sage version
🔹 Network file locking issues
🔹 Time-out occurred on a device.
🔹 Cannot open a file that is locked by another user.
🔹 An invalid IP or DNS address
Please follow the steps mentioned below-
🔹 Right-click on the Home object under the Object window and then choose
🔹 Import Reporter under the Toolbar Menu. then, click on Tools and then select Import Report
🔹 Choose the Report To Be Imported (along with the .al_extension) and click on Open
🔹 Under the Import Report window, Choose the Target Connection (that is, The Connector)
🔹 Choose the Report Destination (that is, the folder) under the drop-down list
🔹 Click on the Import option
🔹 After that, click on OK
🔹 On the Toolbar, click on Action and then select the Refresh option