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 DA: Importing SSL Certificates on DA Agent
DA: Importing SSL Certificates on DA Agent
PDF How To: Import SSL certificates into the Java keystore used by DA Agent
How To: Import SSL certificates into the Java keystore used by DA Agent Problem Description and Typical Error Message received
CMS-XML Web Browser complains the SSL certificate has expired, even though the expiration date is in the future.
Web Browser complains the SSL certificate has expired, even though the expiration date is in the future.
MS-WORD Integrating SDA with third party tools that use SSL.docx
When integrating with third party tools that have been configured to use SSL /HTTPS, it is imperative that the SDA server can verify the trusted status of the SSL certificate . Examples of such third party tools includes artefact repositories (Nexus/Artefactory), or source control tools. Successful integration can be carried out by putting all certificate authority (CA) public keys in the certificate signing chain in the trusted certificate store.
CMS-XML SSL 3.0 Vulnerability - Poodle
SSL 3.0 Vulnerability - Poodle
CMS-XML SDA: Integrating SDA with third party tools that use SSL/HTTPS
SDA: Integrating SDA with third party tools that use SSL /HTTPS
MS-WORD Mitigating POODLE in Serena Deployment Automation.doc
A new security vulnerability called POODLE (Padding Oracle On Downgraded Legacy Encryption) is currently in the news. This is the result of a flaw in the SSL 3.0 protocol and the specific attack and may allow a man-in-the-middle to intercept parts of SSL encrypted communications. This has the potential to affect any SSL encrypted communications and thus requests to communicate with Serena Deployment Automation (SDA) are affected.
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 TLS1.2,TLS1.1, or TLS1.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 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 SDA: Configuring Unauthenticated Mode for HTTP Communications
Deployment Automation automatically uses this mode for JMS-based server/agent communication (you cannot turn this off). SSL unauthenticated mode can also be used for HTTP communication. You can implement this mode for HTTP communication during server/agent/agent relay installation, or activate it afterward.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs