Since TLS is triggered by the client software, there is not much you need to do to setup in offering TLS.  Wildcat! supports TLS (where it applies) and if the client supports TLS, then the user can choose to use TLS.

On the other hand, SSL requires that you setup Wildcat! properly for SSL operations.   More specifically, SSL requires that you have a trusted security certificate from a CA vendor.   Certificates are used by the client and server to determine valid end-points. Wildcat! provides a new configuration tool called wcSSLConfig to help you setup Wildcat! for SSL operations and to create and manage your certificates.

Installation and Setup:

WcSSL is a stock installation item. It is included in Wildcat! package. WcSSL uses the OPENSSL open source technology to implement SSL in Wildcat!.

Run the Wildcat! SSL Configuration manager (wcSSLConfig).  You can start the wcSSLConfig directly or by using  wcConfig | SSL Options (which runs wcSSLConfig).

wcSSLConfig is used to setup Wildcat! for SSL operations.  It will automatically check for the SSL\ sub-folder and if not available, it will automatically create the folder and all necessary files.

The only thing remaining is to install a trusted SSL certificate which you must purchase from a CA vendor.   You will use the Wildcat! SSL Certificate Wizard,  to help you with this process.  You can use the wizard to create self-signed certificates.   This means the certificate will not be trusted.  By trust, it is meant that the end-user software (i.e., web browser) will see your self-signed certificate as being not signed by a trusted CA vendor.   However, end-user software will still offer the user the option to continue with the secured connection using the untrusted self-signed certificate.  At some point, you will want to get a trusted certificate signed by one of the trusted CA vendors.