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 VM 8.6.1+: VM I-Net Web Client going through Apache HTTPD on Linux/UNIX fails to find /vminet.html when using HTTPS
"IncludeOptional /usr/serena/vm/vm/inet/install/httpd2_pvcs.conf" Performing this step will make PVCS VM available for the non-SSL portion of the server (HTTP). When SSL is enabled (by installing mod_ssl), this usually adds the file / etc /httpd/ conf.d /ssl.conf
CMS-XML Login and any operation taking a very long time after switching to https only on SBM
The issue has been seen when IIS is configured to accept client certificates for all or some SBM virtual directories ( gsoap, tmtrack, workcenter, etc . ). The SBM configuration reports shows the virtual directory/application as "SSL Negotiate Certificate".
CMS-XML MCLG: How to setup Collage to run using SSL (https) instead of http?
These instructions show how to setup a "Self Signed" certificate and customize the Collage startup files to be able to use ssl and allow users to login via https. If you need instructions on how to install a certificate from a Certificate Authority such as Verisign, Thawte etc . see the following link for details. After installing the certificate the same customizations from a Collage standpoint illustrated in this document will pertain.
CMS-XML After upgrading to VM 8.6.1 or newer, HTTPS connections to the File Server may fail with SSL routines:ssl3_get_server_certificate:certificate verify failed
Have a Common Name (CN) or alternate DNS name matching the URL being used to access the server Be signed by a Certificate Authority (CA) known to the Java Runtime Engine (JRE) contained within VM (e.g VeriSign, DigiCert, GeoTrust, thawte, etc .) Not be expired
CMS-XML How to test whether JBoss or Tomcat is able to communicate with a https (secure) website.
The attached Java application TestHTTPS can be used to verify that the JRE keystore is able to accept the HTTPS-based URL you're trying to use. This url can be used for a variety of activities in SBM including connecting to orchestration endpoints, rest grid endpoints, secure mail server connections, secure ldap connections etc . Basically anytime the JBoss/Tomcat engine will connect to a secure url.
CMS-XML HTTPS hostname wrong: should be ...
This means that the locally known host name resolved to the correct IP address but SSL required the hostname the SSL certificate was issued to, not the IP address. The solution to this problem is to add to the JBoss Hosts file (C:\Windows\System32\drivers\ etc \hosts), a line with the NAT IP address of the Endpoint and its actual hostname ( i.e. not the local one).
CMS-XML DimCM: AdminConsole: 400 errors are occurring when attempting to edit lifecycles, assign users to group, etc.
relaxedQueryChars="[,]" scheme=" https " secure="true"
CMS-XML Https and file attachments
Https and file attachments
MS-WORD Excel link not working with https protocol and IE
Excel link not working with https protocol and IE Description: By clicking on the Excel link using Teamtrack in a secure environment, you may receive the following error message.
CMS-XML HTTPS error when connecting in Composer or Connection attempt failed.
HTTPS error when connecting in Composer or Connection attempt failed.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs