Is it possible to add Encrypt=yes; to LiteSpeed Connection String? (4297770)

Is it possible to allow LiteSpeed to connect using Encryption?

Customer uses SSL Certificates on their SQL Server instances to encrypt traffic when connecting to SQL. They do not have the Force flag enabled yet but would like to enable it. In most cases, the applications that use SQL they are able to find the connection string that is being used to connect and manually add Encrypt=Yes; to the string. In addition, they are able to change the Server name to the Fully Qualified Domain Name (FQDN) so it matches the Common Name (CN) on the certificate.

Newer and more rigid security requirements in SQL environments.

The LiteSpeed connection string is hard coded and can’t be directly edited by a customer. 

Enhancement Request CR114407 added to StarTeam to address this in a future release of LiteSpeed.