| |
Results |
|
Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/TLS secure channel with authority
|
Composer cannot connect to the Repository - Error: ... Failed to retrieve valid security token ... could not establish trust relationship for the SSL/ TLS secure channel with authority
|
|
|
|
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
|
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
|
|
|
|
Installing a Secure Version of the ChangeMan ZMF REST API-Jenkins Integration
|
ZMF REST Services Getting Started Guide, all secure communication functionality (i.e. SSL) associated with this processing on z/OS must be implemented using IBM's Application Transparent Transport Layer Security (AT- TLS ). Some customers may have found and implemented other solutions that address their specific needs (e.g. the implementation of native Apache Tomcat SSL connectors). However, if problems are encountered
|
|
|
|
zMobile logon requests hang in SSL environments
|
Logon operations can hang and provide no response when zMobile is configured to run with SSL connections. This primarily affects customers who have customised their environment to use native Tomcat security (i.e. redefined the connector to use SSL). However, AT- TLS customers could also see the same behaviour if they have not configured their policy rules in the correct manner.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
2009r2.x : How works DM_FILE_ENCRYPTION ?
|
To get a more secure encryption it is possible to configure the system to use the SSDP (Secure Standard Dimensions) protocol. Encryption will then be provided using TLS version 3.1 using the following cipher suite: TLS _DHE_RSA_WITH_3DES_EDE_CBC_SHA
|
|
|
|
How-To Setup CAC / SmartCard in SBM 11.2 and later
|
This document assumes that SSL/ TLS has already been enabled on IIS and the SBM Tomcat. It will also work if you SBM Tomcat is installed on a different server from IIS.
|
|
|
|
Dim9: Compression of password sent from Desktop Client to the Dimensions 9.1.3 Server
|
For higher security environments Dimensions CM can be configured to encrypt all network traffic using SSL (see the Secure Sockets Layer Support appendix in the Dimensions CM Administrators Guide). When running over SSL the traffic is encrypted using TLS version 3.1 with the following cipher suite:
|
|
|
|
12.x / Tomcat : what about the Nessus security issues 26928 and 42873
|
ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS _RSA_WITH_AES_128_CBC_SHA, TLS _DHE_RSA_WITH_AES_128_CBC_SHA, TLS _DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3 ...
|
|
|
