Typically, SystemWeaver installations are run within a closed network at an organization. As such, the use of encryption for the connection between the SystemWeaver Server and Database and the SystemWeaver clients is not necessary from a security standpoint. However, if used outside a closed network, an option is available to use  encryption*. 

To enable encryption, open the swServer.ini configuration file in a text editor and set the UseSSL entry to "True". 

To use encryption you must have a certificate. Many organizations already have a process for this and guidelines as to what type of certificate to use. The certificate needs to be in the .pfx format and must be called CARoot.pfx. It must be placed in the Server installation directory. If the certificate file has a password, the CertPassword entry in swServer.ini must also be set. 

For testing purposes SystemWeaver is distributed with a dummy certificate, with the dummy password "aaaa". But this should not be used in production to ensure security.

Save your changes. The changes will take affect the next time the server is restarted. 

Note: Within a closed network, 'False' or a null value could be used to improve robustness for network disturbances.

Command Line Option

The following command line option is available for the swServer. It is the same function as the UseSSL entry described above.

Ssl [true/false]    

* The availability of the encryption option is restricted due to EU regulations. Please contact us at support@systemweaver.com for more information.