Find Answers

Filter Search Results
All Products:
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 Need to provide AT-TLS connection option in base ZMF Web Services
Need to provide AT- TLS connection option in base ZMF Web Services
CMS-XML Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/TLS secure channel"
Trying to connect Composer using Secure SSL Connection get error "The request was aborted: Could not create SSL/ TLS secure channel"
CMS-XML “SSLSocketFactory is null” error received executing “Show Web Services Version...” in TLS secured environment
“SSLSocketFactory is null” error received executing “Show Web Services Version...” in TLS secured environment
CMS-XML SDA: There is no configuration that can be utilized to mitigate the risk of BEAST vulnerability on Agent Relay
A security vulnerability called BEAST (Browser Exploit Against SSL/ TLS ) is currently in the news. This leverages weaknesses in cipher block chaining to exploit the SSL protocol. This has the potential to affect any SSL encrypted communications and thus requests to communicate with Serena Deployment Automation (SDA) are affected.
CMS-XML Inserting BLOBs in Oracle database may exceed established limit in 50k bytes for db parameter
- enable centralized database in Configurator - generate SSL/ TLS certificates - enable SSL Client Certificate Authentication and generate client certificates
CMS-XML Problems using HTTPS / SSL with Java plug-in 1.6.0 Update 19 (or 1.5.0 Update 23) and later
This problem is caused by a configuration change in the new Java plug-in that attempts to protect against a Man-In-The-Middle attach, which all previous JRE versions were prone to when using TLS encryption (which includes SSL v3). Details on the problem can be found here: http://java.sun.com/javase/javaseforbusiness/docs/TLSReadme.html
CMS-XML Upgrading 2008 R2 to 2009 R1 and the Keystores are lost during upgrade
The following lines were modified: <!-- SSL/ TLS Connector configuration using the admin devl guide keystore -->
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs