| |
Results |
|
Meritage -Meritage fails when Tomcat is configured to accept SSL connections only.
|
The underlying connection was closed: Could not establish trust relationship for the SSL /TLS secure channel. Additionally, in .\Documents and Settings\<User_ID>\Application Data\Serena\Meritage\meritage.log the following will be found: 2005-07-12 11:54:18,777 [3908] INFO Merant.DocShare.UI.Forms.ServerSetupForm - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
|
|
|
|
KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
|
The section in the Administration guide on how to setup Tomcat to use SSL simply points to the online Tomcat documentation. Here is a quick guide on how to generate a self-signed certificate and how to setup Tomcat to use it.
|
|
|
|
How to install an SSL certificate into the RLC 5.x/RLM 4.x/ALM 3.x JRE keystore for Serena Common Tomcat
|
When Tomcat needs to communicate with other systems via SSL, the JRE used by the Serena Common Tomcat will need to have the root certificate installed. If you do not know which JRE is being used by Serena Common Tomcat , you can follow these steps:
|
|
|
|
How to configure the Cipher Strength of the Tomcat engine used by the Serena VM Web Application Server and Serena Common Tomcat?
|
To prohibit the use of weak ciphers, it is necessary to manually modify the Tomcat SSL connector definitions and assign them an explicit list of acceptable ciphers. This will also solve the Firefox error: Secure Connection Failed
|
|
|
|
VM 8.6.1: VM I-Net Web Client Agent cannot connect to server if IIS or Tomcat requires an SSL Client certificate
|
With VM 8.6.0 and older, the Java plug-in would use the network connection that was already established by the browser. If the server was configured to require an SSL Client certificate, but the browser had this certificate, the Java applet would therefore transparently be allowed access.
|
|
|
|
How to configure the Cipher Strength for SBM Tomcat
|
The SBM Tomcat server can be setup to prohibit the use of weak ciphers. To do this, it is necessary to manually modify the JBOSS/ Tomcat SSL connectors with a list of acceptable use ciphers. SBM Tomcat is capable of using any ciphers allowed by version of Tomcat in used.
|
|
|
|
How to configure one-way and two-way SSL for Release Control and ZMF Connector
|
2. Configure the Tomcat server that serves ZMF Connector to use one-way SSL. In the Tomcat conf directory (..\common\ tomcat \8.0\conf), edit server.xml
|
|
|
|
VM: How to use an SSL certificate from IIS with Tomcat in the PVCS Version Manager Web Application Server
|
://server:8443 (using Admin | File Server ), see Configuring VM File Server access from Version Manager Desktop Client installations on other machines
|
|
|
|
VM 8.6+: Using certtool to generate a unique SSL certificate for the PVCS VM Web Application Server (Tomcat)
|
To have other browsers trust the CA, import the file into each browser using its certificate import procedure. Configuring VM File Server access from Version Manager Desktop Client installations on other machines If there are PVCS VM Desktop Client installations on other machines that have to access the VM File Server via HTTPS, execute the following command on each of these machines:
|
|
|
|
VM 8.6+: Using certtool to generate an SSL certificate for the PVCS VM Web Application Server (Tomcat) that is signed by your Certificate Authority
|
This step is only required for VM File Server clients running VM 8.6.1 or newer: Configuring VM File Server access from Version Manager Desktop Client installations on other machines When PVCS VM Desktop Client installations on other machines are going to access the VM File Server one this machine via HTTPS, execute the following command on each of these machines:
|
|
|
