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 Configurator requires TLS 1.0 Client to be enabled for SSO URL Overrides to Test Connect
Configurator requires TLS 1.0 Client to be enabled for SSO URL Overrides to Test Connect
CMS-XML Static Diagnostics Notification Server and Mail client database connection fails if TLS 1.0 is disabled
Static Diagnostics Notification Server and Mail client database connection fails if TLS 1.0 is disabled
CMS-XML Configurator requires TLS 1.0 to be enabled in order to do static diag tests to its own web services.
Configurator requires TLS 1.0 to be enabled in order to do static diag tests to its own web services.
CMS-XML This page can’t be displayed. Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://servername again.
This page can’t be displayed. Turn on TLS 1.0 , TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://servername again.
CMS-XML How-To Setup SBM on a TLS hardened server / Disable SSL
Secure SSL and TLS in SBM 11.x SBM 11.x will communicate with an external web service using TLSv1.2 unless the web service endpoint requests a lower protocol. However, the JRE used by SBM 11.x enables TLS v1.0 and later by default. Below are instructions to disable TLSv 1.0 in SBM 11.x.
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
04/06/2018 11:47:59: Invoking import callback: uuid=b9d721eb-61ec-4de0-b4f2-7fce77fa0a85, endpoint=https://sbm/mashupmgr/services/sbmimportcallback72, result=30 04/06/2018 11:47:59: Invoking import callback failed: Error observed by underlying SSL/ TLS BIO: No such file or directory: SSL_connect error in tcp_connect()
CMS-XML Agents don't appear online after a server upgrade to Deployment Automation version 6.1.1 or higher
6.1.1, Serena Deployment Automation (SDA) has enhanced security to connect through TLS 1.2, TLS 1.1, or TLS 1.0 protocols supported by Java 6 and above, and rejects connection through earlier SSL protocols such as SSLv3 and SSLv2Hello. If you have agents that have been connecting using one of the rejected protocols, your agents may try to connect through the unsupported protocol and the connection will be rejected.
CMS-XML Get "Internet Explorer cannot display the webpage" error using Mariner on Demand or Agile on Demand.
Serena Mariner on Demand and Agile on Demand require SSL 3.0 or TSL 1.0 in order to access the website. By default Internet Explorer 6 and 7 have these encryption algorithms enabled. If SSL 3.0 and TLS 1.0 are disabled you will see a message that says "Internet Explorer cannot display the webpage" instead of the login page.
CMS-XML CM 14.1.0.4 web client with SSO gets applet errors
The terms SSL and TLS are often used interchangeably or in conjunction with each other ( TLS /SSL), but one is in fact the predecessor of the other — SSL 3.0 served as the basis for TLS 1.0 which, as a result, is sometimes referred to as SSL 3.1. Subsequent versions of TLS — v1.1 and v1.2 are significantly more secure and fix many vulnerabilities present in SSL v3.0 and TLS v1.0.
CMS-XML PVCS Version Manager - How to disable SSLv3 and optionally also TLSv1.0 and TLSv1.1, or how to exclusively use TLSv1.2
BEAST (Browser Exploit Against SSL/ TLS )
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs