Configure a secure Suitelink communication as a standard user
- Last UpdatedJul 16, 2024
- 2 minute read
A secure Suitelink connection, enabled with TLS 1.2 protocol, encrypts the communication channel between client and server. If you are using the encrypted Suitelink, to access remote date, you must configure the System Management Server (SMS) from the Configurator. The encryption is achieved through the certificates provided by SMS. For the SuiteLink server and client to use encrypted communication, the ASB Runtime Components feature must be selected in the SuiteLink 3.0 installation.
Since the introduction of secure SuiteLink (V3), SuiteLink has been providing the fallback so that a SuiteLink server can accept incoming connections in a secure (V3, encrypted) or an unsecure (V2, unencrypted) mode together. From the System Platform 2023 release, by default, the fallback mode to accept V2 connection is disabled. If you want to enable the fallback mode to accept the unsecure connection, you have to make the configuration changes in the System Management Server. You can verify the mode of SuiteLink connection, whether secure or unsecure, by checking the WWSLS component in the Log Viewer.
Note: As of System Platform 2023, the SuiteLink connection is by default set to secure with TLS encryption. If unsecure fallback mode is not enabled and secure connection requirements are not met, then SuiteLink connection will fail. For more information, see Configure the System Management Server in the Configurator.
Enable or disable the fallback (unsecure) Suitelink connection using the Registry Editor
-
Open the Registry Editor.
-
Navigate to the path: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ArchestrA\WebApplications\Default\SuiteLink]
-
Locate the entries:
"V2Server"=dword:00000001
"V3Server"=dword:00000001
-
To enable the fallback mode, set the value of V2Server to 1.
-
To disable the fallback mode, set the value of V2Server to 0.
-
Restart the computer.