You can configure the Web Server or Application Server on which Communications Express is deployed in the SSL mode.
For information about how to configure the Web Server on which Communications Express is deployed in the SSL mode, refer to Sun Java System Web Server 7.0 Administrator’s Configuration File Reference guide.
For information about how to configure the Application Server on which Communications Express is deployed in the SSL mode, refer to Sun Java System Application Server Administration Guide.
Set the following configuration parameters in the uwc-deployed-path /WEB-INF/config/uwcauth.properties file:
uwcauth.ssl.enabled=true. If set to true, the entire authentication process and access of the application is done in SSL mode.
uwcauth.https.port=SSL-port-number-of -the webcontainer-in which-uwc-is-deployed
webmail.ssl.port=SSL port for the Messaging Server
Set the local.webmail.sso.uwcsslport Messenger Express parameter value to the SSL port-number of the Web Server in which Communications Express is deployed.
This parameter is required to instruct Messenger Server to get Communications Express integration services. For example, if this parameter is set, then time out event of webmail will take the user to Communications Express' login page.
For example, local.webmail.sso.uwcsslport=SSL port-number of the webserver in which communications express is deployed
Set the webmail.ssl.port parameter for Messaging Server.
Set the parameter to the SSL port that Messaging Server listens to.
Communications Express can be configured for SSL authentication only, which implies that authentication can be performed over SSL, but access of the application thereafter is over non-SSL mode.
Set uwcauth.ssl.enabled to false in the uwcauth.properties file.
Set uwcauth.https.port to the SSL port number of the Web Server in which Communications Express is deployed.
Set uwcauth.ssl.authonly to true.
The two parameters, uwcauth.ssl.authonly and uwcauth.ssl.enabled in the uwcauth.properties file are mutually exclusive .