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 Installing a Secure Version of the ChangeMan ZMF REST API-Jenkins Integration
2. Define Incoming TLS Policy (pagent) Rule for ZMF REST API HTTPS Connector Port
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 Need to provide AT-TLS connection option in base ZMF Web Services
ChangeMan ZMF 8.1.4
CMS-XML “SSLSocketFactory is null” error received executing “Show Web Services Version...” in TLS secured environment
ChangeMan ZMF Client Pack ZMF 4ECL 8.1.2
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
CMS-XML New Features in ChangeMan ZMF for Eclipse 8.1.1 and 8.1.1.01
ZMF for Eclipse client must also be configured to use TLS. Connection to the server will fail if the TLS setting for ZMF for Eclipse does not match the TLS configuration on the z/OS server.
PDF ChangeMan ZMF for Eclipse 8.1.1 Readme
If TLS is enabled, the z/OS® server must also be configured to use TLS on all ports for the server, as well as all ChangeMan ports under the server. Likewise, if the z/OS server is configured to use TLS, the ChangeMan ZMF for ECL client must also be configured to use TLS. Connection to the server will fail if the TLS setting for ZMF for ECL does not match the TLS configuration on the z/OS server.
PDF Serena ChangeMan ZMF Connector Configuration Guide
<Connector port="8443" SSLEnabled="true" scheme="https" secure="true" sslProtocol=" TLS " sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
PDF Serena Release Control: ChangeMan ZMF Plugin Quick Reference
<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" />
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs