Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML 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.
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
When using self-signed certificates, or when the JRE does not know the Certificate Authority that was used to sign the certificate, attempts to associate an issue (module association) from VM I-Net during checkout or checkin will yield errors similar to the following in the Tomcat logs (std*.log on Windows, catalina.out on UNIX):
CMS-XML VM 8.6+: Using certtool to generate a unique SSL certificate for the PVCS VM Web Application Server (Tomcat)
The sample certificate that is installed with Version Manager is intended to quickly validate SSL access is working via the HTTPS port (8443). However, it should not
CMS-XML VM: How to use a pre-generated SSL certificate that includes the private key with Tomcat in the PVCS Version Manager Web Application Server
The typical process to obtain an SSL certificate consists of generating a private key on the server, sending a signing request to a Certificate Authority, and apply its signature to the certificate (see KB S143068 ). However, if you are provided with a keystore containing a pre-generated SSL certificate that includes the private key , use the instructions below to import that into PVCS Version Manager's Tomcat instance.
CMS-XML VM: How to use an SSL certificate from IIS with Tomcat in the PVCS Version Manager Web Application Server
If Microsoft Internet Information Services (IIS) has a valid SSL certificate, it is possible to use this certificate with the Tomcat instance of PVCS Version Manager running on the same machine. That way VM clients can reach the VM File Server via Tomcat's port 8443, as accessing it via IIS (e.g port 443) is technically possible but not recommended due limitations imposed by IIS.
CMS-XML Serena VM Web Application Server (Tomcat) SSL Sample Certificate Chain Contains RSA Keys Less Than 2048 bits
The sample certificate that is installed with Version Manager is intended to quickly validate SSL access is working via the HTTPS port (8443). However, it should not
CMS-XML 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
can be used to generate a Certificate Signing Request (CSR) for your Certificate Authority (CA), and how it can subsequently import the signed request into Tomcat used by the PVCS VM Server. If you integrated the PVCS VM server with Internet Information Services (IIS) on your Windows machine, use KB doc S143162 to copy the SSL certificate from IIS into Tomcat.
CMS-XML 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.
CMS-XML Using Version Manager with a custom SSL certificate - How to change the SSL certificate used to access Tomcat via HTTPS
All of the following commands are executed from the directory VM_Install_Dir \vm\common\ tomcat \conf (e.g. C:\Program Files (x86)\Serena\vm\common\tomcat\conf
CMS-XML 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
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs