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 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 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 limit access to the PVCS Version Manager Web Application Server to HTTPS (SSL) only
How to limit access to the PVCS Version Manager Web Application Server to HTTPS (SSL) only
CMS-XML Using Version Manager with a custom SSL certificate - How to change the SSL certificate used to access Tomcat via HTTPS
Using Version Manager with a custom SSL certificate - How to change the SSL certificate used to access Tomcat via HTTPS
CMS-XML How to make cookies like JSESSIONID secure if HTTPS encryption/decryption is handled by an external device, like an F5 load balancer
How to make cookies like JSESSIONID secure if HTTPS encryption/decryption is handled by an external device, like an F5 load balancer
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
CMS-XML After installing Microsoft Windows patch KB3172605 on a client PC, Internet Explorer can no longer access Tomcat-based servers via HTTPS (ports 8443/8444)
After installing Microsoft Windows patch KB3172605 on a client PC, Internet Explorer can no longer access Tomcat-based servers via HTTPS (ports 8443/8444)
CMS-XML VM I-Net Web Client using HTTPS doesn't work in Internet Explorer without compatibility mode
VM I-Net Web Client using HTTPS doesn't work in Internet Explorer without compatibility mode
CMS-XML Problems using HTTPS / SSL with Java plug-in 1.6.0 Update 19 (or 1.5.0 Update 23) and later
Problems using HTTPS / SSL with Java plug-in 1.6.0 Update 19 (or 1.5.0 Update 23) and later
CMS-XML VM 8.6.1: When using HTTPS, the VM I-Net Web Client can get stuck processing Agent-based operations and ultimately fail with Transfer process has unknown timeout exception
VM 8.6.1: When using HTTPS , the VM I-Net Web Client can get stuck processing Agent-based operations and ultimately fail with Transfer process has unknown timeout exception
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs