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 VM 8.6.1: VM I-Net Web Client Agent cannot connect to server if IIS or Tomcat requires an SSL Client certificate
VM 8.6.1: VM I-Net Web Client Agent cannot connect to server if IIS or Tomcat requires an SSL Client certificate
CMS-XML How to acquire the SSL certificates for your mail server when setting up the Mail Client ( EOF on Socket ) error in ns.log
The attached video shows how to get a copy of the SSL certificates being used by your mail server in order for them to be imported into the JBoss/ Tomcat keystore.
CMS-XML How to setup jboss web server to use the same SSL key pair as IIS -- 2009R3 and later
When SBM is configured with the Application Engine and JBOSS servers on the same server , it is possible to setup the JBOSS Tomcat web server to use the same SSL key pair used to secure IIS. This article assumes that IIS has already been configured to use SSL. This how to is for SBM 10.1 and higher.
CMS-XML KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
Create a new keystore containing a single self-signed Certificate by running the keytool program from <common tools directory>\jre\bin from the command line on the server : Windows: keytool -genkey -alias tomcat -keyalg RSA -keystore \path\to\my\keystore
CMS-XML DimCM: SSL: How to enable SSL for Dimensions CM Server with your own CA Certificate
This keystore contains a certificate which has a CN of ‘localhost’ with the Root of Serena Sample CA-2. This file is located in the $ Tomcat \conf directory.
CMS-XML DimCM: SSL: How to enable SSL for Dimensions CM with SBM SSO Server with your own CA Certificate
keystore file. This keystore contains a certificate which has a CN of ‘localhost’ with the Root of Serena Sample CA-2. This file is located in the $ Tomcat \conf directory.
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 8.6+: Using certtool to generate a unique SSL certificate for the PVCS VM Web Application Server (Tomcat)
be used in a production environment as the identical sample certificate is installed on all Version Manager installation, allowing anyone with access to that certificate to decipher the traffic. To avoid this, every VM installation should generate a unique certificate. This also avoids problems caused by the default certificate only being valid for a server named "localhost".
CMS-XML 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.
CMS-XML Serena VM Web Application Server (Tomcat) SSL Sample Certificate Chain Contains RSA Keys Less Than 2048 bits
be used in a production environment as the identical sample certificate is installed on all Version Manager installation, allowing anyone with access to that certificate to decipher the traffic. To avoid this, every VM installation should generate a unique certificate. This also avoids problems caused by the default certificate only being valid for a server named "localhost".
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs