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  
  Results
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 “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 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
CMS-XML 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.
CMS-XML New Features in ChangeMan ZDD 8.2 Patch 2
on the system, and it causes significant performance degradation in the server. TLS Client Certificate Support When a server is configured
CMS-XML Event Response Code: 500 following the implementation of ChangeMan ZMF 8.2 Patch 3 - REST API (Revision-1)
After the customer disabled their AT- TLS rule, the problem was eliminated. They had the AT-TLS rule encrypting all ports AND they had configured Tomcat to secure ports (HTTPS), so it appears that their issue was caused by double encryption.
CMS-XML How to configure one-way and two-way SSL for Release Control and ZMF Connector
<Connector port="8443" SSLEnabled="true" scheme="https" secure="true" sslProtocol=" TLS " sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
CMS-XML How to install setup the ZMF Connector to communicate with SBM using SSL (SBM and ZMF Connector on same server)
screen. On the HTTPS/ TLS tab, click on Export Existing Certificate When prompted, chose the option for "Export certificate and all certificates in the certificate path
PDF RLM HTTP Server Overview:
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol=" TLS " keystoreFile="/u/tomcat/TomcatCertificate.cer" keystorePass="TomcatPassword" />

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs