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
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.
PDF RLM HTTP Server Overview:
2) Tomcat SSL is configured at the port level. A SSL connector port is defined in the Tomcat server.xml file and specifies the SSLEnabled=”true” attribute.
CMS-XML How to install the SBM certificate into the ZMF Connector (ALM Connector) java keystore
This article goes through the steps to import a certificate into the Java Keystore ( cacerts ) file so JBoss can communicate via SSL / HTTPS to secure sites and URL's. ... Restart Micro Focus Common Tomcat
CMS-XML “SSLSocketFactory is null” error received executing “Show Web Services Version...” in TLS secured environment
[1/10/17 14:12:51:416 CET] 00000012 SystemErr R javax.net. ssl .SSLException: SSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set.
CMS-XML Need to provide AT-TLS connection option in base ZMF Web Services
However, several customers also host their own homegrown, ZMF web services(ZMFWS)-based applications. Looking at the web services there is no ‘ secure logon’/TLS/ SSL option available. This functionality needs to be added so that custom applications can also exploit the benefits of AT-TLS security.
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 SSL 3.0 Vulnerability - Poodle - Serena Mainframe Products
SSL 3.0 Vulnerability - Poodle - Serena Mainframe Products
CMS-XML REST API Tomcat Server : Message: Property Name ZMFRESTCONTEXT Not recognized.
REST API Tomcat Server : Message: Property Name ZMFRESTCONTEXT Not recognized.
CMS-XML ZMF Plugin: Tomcat localhost.log gives error "java.net.UnknownHostException: ?xxxxx"
ZMF Plugin: Tomcat localhost.log gives error "java.net.UnknownHostException: ?xxxxx"
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs