| |
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.
|
|
|
|
Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority
|
If you are not using SSL then in Configurator deselecct the SSL configuration for Tomcat . Untick "Use HTTPS on Port" and Apply.
|
|
|
|
OE database fails to upgrade: Tomcat server startup timed out
|
Tomcat server startup timed out. ---> ConfigurationUtility.Core.Network.HttpException: URL: https://sbmp02/, Method: GET, Error message: The request was aborted: Could not create SSL/ TLS secure channel.
|
|
|
|
DimCM: Tomcat: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
|
This might be because the site uses outdated or unsafe TLS security settings. If this keeps happening, try contacting the website's owner.
|
|
|
|
ALF Events from Dimensions CM are not Received when SBM Tomcat Requires HTTPS (SBM 11.0 or Higher)
|
For example: <!-- SSL/ TLS Connector for 1-way SSL authentication--> <!-- In Configurator "Tomcat Server / HTTPS Connector port" -->
|
|
|
|
How to configure the Cipher Strength for SBM Tomcat
|
ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS _DHE_
|
|
|
|
How-To Setup SBM (10.1.3 - 11.7.0) on a TLS hardened server / Disable SSL
|
Secure SSL and TLS in SBM 11.x common_config.bat located in [SBM INSTALL DIR]\SBM\Common\ Tomcat 7.0\bin Locate the section starting with this line:
|
|
|
|
KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
|
port="8443" scheme="https" secure="true" sslProtocol=" TLS " strategy="ms" truststoreFile="C:\Temp\.keystore" truststorePass="serena"/>
|
|
|
|
How to configure the Cipher Strength of the Tomcat engine used by the Serena VM Web Application Server and Serena Common Tomcat?
|
truststorePass="serena" clientAuth="false" sslProtocol=" TLS "/> <Connector port="8444" minSpareThreads="5" maxSpareThreads="75"
|
|
|
|
Deploy stays in waiting when TLS 1.0 is removed from server.xml - Invoking import callback failed: Error observed by underlying SSL/TLS BIO: No such file or directory
|
As of SBM 11.3, it doesn't look possible to remove TLS 1.0 from both the Server.xml ( Tomcat ) and the SChannel Registry key ( IIS ) and have deploys reach the "Completed" status. The deploy itself will succeed and your changes will get deployed. It is just the callback from the Application Engine to the Repository telling the system the deploy completed that fails so the status stays in "Waiting" forever.
|
|
|
