Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML 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.
CMS-XML 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.
CMS-XML 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" -->
CMS-XML 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"/>
CMS-XML 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"
CMS-XML 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.
CMS-XML How-To Setup CAC / SmartCard in SBM 11.2 and later
This document assumes that SSL/ TLS has already been enabled on IIS and the SBM Tomcat . It will also work if you SBM Tomcat is installed on a different server from IIS.
CMS-XML Things to Consider when disabling TLSv1.0 and TLSv1.1 for SBM 11.7.1+
for Client TLS in IIS and Tomcat , you may prevent SBM from talking to other servers / programs. for Server TLS in IIS and Tomcat, you may prevent other programs from talking to SBM. Here is how we should proceed to verify on the test server.
HTML Solutions Business Manager 11.7 Security Bulletin
Summary You can now select the Java TLS provider of your choice, including the OpenJSSE Provider , which enables you to select TLS 1.3 with Tomcat . TLS configuration improvements (ENH326186)
CMS-XML Disable weak ciphers for the SBM Tomcat
Disable weak ciphers for the SBM Tomcat
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs