Follow

Disabling SSL access to the Web Application

  • Create a copy of TRAVERSE_HOME/apps/tomcat/conf/server.xml and place outside of the Traverse installation folder.  This will allow for the quick restoration of the original copy, if required.  Note:  TRAVERSE_HOME should be replaced by the actual installation folder.
  • To disable SSL access to the Web Application, find the following section within TRAVERSE_HOME/apps/tomcat/conf/server.xml:
<!-- define ssl-enabled (https) request handler -->
<Connector port="443"
minProcessors="20" maxProcessors="80"
enableLookups="false" allowChunking="false"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" protocols="TLSv1,TLSv1.1,TLSv1.2"
keystorePass="changeit" keystoreFile="../../plugin/web/webapp.keystore"
compression="off" debug="0"
URIEncoding="UTF-8" />
  • Enclose the 'Connector' XML element between '<!--' and '-->' to remove this configuration. For example:
<!-- define ssl-enabled (https) request handler -->
<!-- disabled
<Connector port="443"
minProcessors="20" maxProcessors="80"
enableLookups="false" allowChunking="false"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" protocols="TLSv1,TLSv1.1,TLSv1.2"
keystorePass="changeit" keystoreFile="../../plugin/web/webapp.keystore"
compression="off" debug="0"
URIEncoding="UTF-8" />
-->
  • Then restart the Web Application to reload the modified configuration
  • Should the Web Application fail to start, review the changes made to the file for any typographical errors.  And if all else fails,  you may revert to the original copy of the file.
  • Please note that any changes to this file are not retained after an upgrade, and so may need to be re-applied after completion of upgrades.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.