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 Dim CM 14.2.x: Setting up Secure SDP via SSL for Dimensions 14.2.x installations
1. Make sure the Dimensions listener and Tomcat are shutdown. 2. As user dmsys, or whoever your Dimensions admin user is, enter the following commands: cd $DM_ROOT/prog
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 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 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 How to configure the Cipher Strength for SBM Tomcat
SBM has an IIS/Windows component and a Tomcat component that can be secured with SSL . IIS/Windows is often setup by group policy to disable the use of weak SSL ciphers. However, the Tomcat component is not affected by group policy. Furthermore, the default setup of Tomcat is to allow the use of weak SSL ciphers.
CMS-XML SSL 3.0 Vulnerability - Poodle - SDA
This is the result of a flaw in the SSL 3.0 protocol and the specific attack and may allow a man-in-the-middle to intercept parts of SSL encrypted communications. This has the potential to affect any SSL encrypted communications and thus requests to communicate with Serena Deployment Automation (SDA) are affected. For customers to make sure their installations are secure there are mitigation steps they can take to secure the SDA Server and Serena Common Tomcat .
CMS-XML Tips for Securing SBM Server
Use SSL: Make sure to use well-known SSL certificates in IIS and Tomcat (if you have HTTP ports active). Vulnerable TLS:
PDF How To: Import SSL certificates into the Java keystore used by DA Agent
Import the missing Certificates The next steps describe the how to import the certificate(s) into the Java certificate trust store (cacerts) file so Serena Common Tomcat can communicate via SSL / HTTPS to secure sites and URL's. To determine the location of the Java Runtime Environment (JRE) and the Keystore that is used by the Agent, use these steps:
CMS-XML How to configure the Cipher Strength for SBM JBOSS
SBM has an IIS/Windows component and a JBOSS/ Tomcat component that can be secured with SSL . IIS/Windows is often setup by group policy to disable the use of weak SSL ciphers. However, the JBOSS/Tomcat component is not affected by group policy. Furthermore, the default setup of Tomcat is to all the use of weak SSL ciphers.
MS-WORD Mitigating POODLE in Dimensions CM.DOCX
For customers to make sure their installations are secure there are mitigation steps they can take to secure the Dimensions CM Server and Serena Common Tomcat . Vulnerability Description
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs